Want to work smarter with AI? See how Agentforce fits your business.
Integrations and automations keep working through a CRM switch when they are treated as part of the migration, not an afterthought. Start by listing every connected system and every workflow, decide which to rebuild, replace or retire, then re-point integrations to Salesforce and rebuild automations in Salesforce Flow. The integration cutover is sequenced with the data cutover, and regression tests confirm each connection works before the team goes live.
Step 1: Build an Integration and Automation Inventory
- Integrations: ERP, accounting, marketing, support, telephony, ecommerce and data warehouse connections.
- Automations: assignment rules, workflows, email alerts, approvals, scheduled jobs and scripts.
- Details to capture: data direction, frequency, owner, fields used and what breaks if it stops.
Step 2: Rebuild, Replace or Retire
Some integrations have ready-made Salesforce connectors and can be replaced. Custom ones are rebuilt against Salesforce APIs, ideally through middleware so future changes are easier. Automations are redesigned in Salesforce Flow rather than copied line for line, which is a good moment to retire workflows nobody needs.
Step 3: Sequence the Cutover
| Stage | Data | Integrations and Automations |
|---|---|---|
| Build | Trial loads in a sandbox | Rebuilt and connected to test endpoints |
| Test | Validated sample data | End-to-end tests with connected systems |
| Freeze | Old CRM set to read-only | Old integrations paused to stop new writes |
| Cutover | Final delta load into production | Integrations switched to Salesforce production |
| Stabilize | Reconciliation and fixes | Monitoring, error queues and replays |
Pausing old integrations before the final load prevents records being written to the old CRM after it has been copied.
Step 4: Regression Testing
Test every connection end to end: an order created in the ERP should appear in Salesforce, a won deal should reach finance, and a web form should create a lead with the right owner. Automations are tested with real scenarios, including edge cases such as missing fields and reassigned owners.
Switching Mid-Year
A mid-year move also needs continuity for reporting. Migrate year-to-date pipeline, closed deals and targets so dashboards and commission figures stay accurate, and agree which system is the record for each period.
Who Should You Hire?
Choose a partner that handles both data and integrations so the two cutovers are planned together. Folio3 provides Salesforce integration services for re-pointing and rebuilding connected systems.
For workflows and approvals, Salesforce automation services rebuild your processes in Flow.
The data side is covered by Folio3 Salesforce migration services, so one team owns the whole cutover.
People Also Ask
- How do you migrate workflows and automations to Salesforce?
- How do you sequence integration cutover with data migration?
- What regression testing is needed after a CRM switch?
- How do you re-point integrations to a new CRM?
- We’re switching CRMs mid-year and worried about keeping our integrations and automations working after the move. How is that handled during a migration?
Switching CRMs with integrations and automations in place?
Talk to Folio3 about a cutover plan that keeps connected systems running.
Plan your integration cutover with Folio3 →