Moving from one CRM to another - or spinning up a new instance of the same CRM - touches marketing lists, forms, funnel reports, and automated programs across your Act-On account. Work through this process in order to keep the migration smooth and avoid broken syncs.
Quick Reference (Advanced Users)
- Prep: clear scheduled syncs and CRM-dependent segments, and update forms/programs before switching.
- Disconnect: Settings > Connectors > CRM > Disconnect, then file a support ticket for next steps.
- Reconnect: follow the full Integration Guide for your new CRM, then run a sync from Settings > Data Management.
- Validate: recheck Automated Programs, Standard Field Names, segments, List Maintenance Programs, and the Sales Prospector list owner fields.
Prepare Your Data
| Data in Act-On | Actions |
|
Marketing Lists |
|
|
Funnel Reports |
Stop and/or Delete any existing funnel reports that reference your CRM lists |
|
Forms |
|
|
Automated Programs |
|
Disconnect Your Old CRM
- Locate the connector for your current CRM in Settings > Connectors > CRM, then click Disconnect
- Create a ticket using the form below:
Act-On Support will follow up with you with the next steps.
Connect Your New CRM
- Follow the Integration Guide for your CRM in its entirety, even if some elements have already been completed
- Run a CRM sync from Settings > Data Management
Completing these steps will ensure that future scheduled syncs execute correctly.
Validate Your Setup
- Check your Automated Programs and reattach new source lists and CRM task steps, if necessary
- Ensure that Standard Field Names are aligned across your systems
- Recreate segments that use CRM data, as necessary
- Verify that List Maintenance Programs are updating the new CRM lead score field in your CRM
- Change the new Sales Prospector list
- Identify the Owner Name and Owner Email in the new lists
- Note that Sugar uses the ‘Assigned To’ Field for Hot Prospects
- Note: It is recommended to halt scheduled Marketing List syncs when transitioning to a new CRM due to the record ID format being different. Even when migrating to a new instance of the same CRM, mismatched IDs can disrupt list data and cause issues.
Related to