Understand the process and requirements of customer relationship (CRM) platforms and marketing automation platform (MAP) data source migrations, including the dependencies and the initial information-gathering requirements that must be completed before starting a migration.
For Advanced Package
This CRM and MAP migration information is for customers with the Advanced package. Customers with the Platform-only or the Platform and Essentials package can simply submit a support ticket for migration assistance.
Migrations Overview
After consultation, we provide a scoped statement of work (SOW) to predictive customers for both CRM and MAP migrations.
It will take about three to five weeks to complete a CRM migration.
It will take about two to three weeks to complete an MAP migration.
For either a CRM or an MAP migration, the intent models are rebuilt and refreshed from the new data source. This means that it is expected that the intent models before a migration and after one may change.
For either a CRM or an MAP migration, all data must be migrated to the new CRM or MAP. In addition, the new CRM or MAP must have begun being used before we begin the migration process.
CRM Migrations
CRM migrations are complex and differ from organization to organization. For predictive customers, they commonly involve:
Clearing credentials that are locked in 6sense integrations screens.
Enabling the new credentials to be input.
Following the onboarding steps to make sure new data is being accounted for accurately before retraining the predictive models for predictive customers.
Note: We load CRM data from the new source only, and this new data source should have data finalized before we integrate with the new system. This protocol helps to ensure a clean data sync once the integration is connected. 6sense does not migrate any CRM data from one system to another.
Data Requirements
All CRMs: We require four or more (4+) months of data to be present in a new data source for a CRM so that our platform can show the validity of our intent models.
Salesforce Migrations: Make sure that any Opportunity, Campaign/Campaign Member, Opportunity Contact Role, and Task/Event data has a true historic created date that we can reference. We will need Accounts, Contacts, and Leads associated with the data above to feed into our Profile Fit models to ensure accuracy.
HubSpot CRM Migrations: Make sure that any Deals, Activity (marketing and sales), deal contact relationship, and pipeline data has a true historic created date that we can reference. We will need Companies and Contacts associated with the data above to feed into our Profile Fit models to ensure accuracy
Considerations
After consultation, we provide a scoped SOW to predictive customers for CRM migrations.
If you are planning on migrating your CRM, alert your CSM as soon as possible in advance so you and your CSM can talk and finalize a timeline. When reaching out to your CSM be prepared to answer these six questions:
What is the CRM migration planned to be (what platform to what platform)?
When does the current CRM expire?
When will you start using the new CRM for production activities?
What data are you migrating to the new CRM?
When will data be in a finalized state in the new CRM?
Are there any other migrations happening at the same time (MAP, WEB, and so on)?
Since we will need to rebuild the intent models using the new CRM data source, those intent models will be refreshed toward the end of the migration process. This refresh is likely to cause the buying stages and scores to shift between their current state and the future state after the rebuild.
During a CRM migration, no new scores will be generated. Since no new scores will be generated, score orchestrations will be paused during a CRM migration.
Required Pre-Migration Tasks
Any segments referencing CRM-specific fields or CRM reports will go into error during the migration, so update or delete them before the migration begins.
Delete any score orchestrations that are sent directly to your CRM. These score orchestrations must be remade once the models are rebuilt from the new CRM data source.
Advertising campaigns, score orchestrations, and Enrichment orchestrations should be paused before CRM migrations.
MAP Migrations
Changing your MAP is a straightforward process in 6sense. However, keep in mind that:
While intent models will remain up during the migration and the existing models will remain accurate, they will not be as accurate as they can be because MAP activity and MAP contact data is not flowing into the model during the migration.
Predictive scores will still flow through during the migration if you already have score orchestrations set up to your CRM.
Migrating to a new MAP commonly involves:
Clearing credentials that are locked in 6sense integrations screens.
Enabling the new credentials to be input.
Following the onboarding steps to make sure new data is being accounted for accurately before retraining the predictive models for predictive customers.
Note: We load MAP data from the new source only, and this new data source should have data finalized before we integrate with the new system. This protocol helps to ensure a clean data sync once the integration is connected. 6sense does not migrate any MAP data from one system to another.
Integration and Data Requirements References
Data Requirements
All MAPs: We require one or more (1+) months of data to be present in a new data source to make an MAP migration. We require three or more (3+) months of data to be present in the new MAP (the more months of data the better) to show the validity of our intent models.
All MAPs: Make sure that Contact and Account/Company data is fully migrated to feed into our Profile Fit models to ensure accuracy.
All MAPs: 6sense will not migrate any historical data, so it is important your organization migrates its data and starts using the new MAP before we begin the migration process.
Custom Solutions: For an added fee, we can map old data sources to the new ones, but we need the ID mappings provided by you. Doing this involves creating a custom solution that also adds time to the migration.
Considerations
After consultation, we provide a scoped SOW to predictive customers for MAP migrations.
If you are planning on migrating your MAP, alert your CSM as soon as possible in advance so you and your CSM can talk and finalize a timeline. When reaching out to your CSM be prepared to answer these six questions:
What is the MAP migration planned to be (what platform to what platform)?
When does the current MAP expire?
When will you start using the new MAP for production activities?
What data are you migrating to the new MAP? How much activity data (email sends, email opens, form fills, and so on) are you migrating, if any?
When will data be in a finalized state in the new MAP?
Are there any other migrations happening at the same time (CRM, WEB, and so on)?
Score orchestrations will continue for MAP migrations. If you are doing a simultaneous CRM and MAP migration, score orchestrations will be paused.
Since we will need to rebuild the intent models using the new MAP data source, those intent models will be refreshed toward the end of the migration process. This refresh is likely to cause the buying stages and scores to shift between their current state and the future state after the rebuild.
Required Pre-Migration Tasks
Any segments referencing MAP-specific fields will go into error during the migration, so update or delete them before the migration begins.
CRM or MAP Migration Process
While every migration is unique, the general process for migrations in the 6sense platform is:
You meet with us to scope the project and confirm the timeline to begin the migration.
We clear the integration UI to enable you to input new integration credentials.
Make sure any users that need to work on the integration have the correct read/write permissions to all objects. If restricted access is required, speak to your assigned product consultant. That person can provide guidance on the object-level access requirements.
Set the API limit to 40–60% of your daily unused API volume to ensure a fast sync.
For predictive CRM migrations, the platform is now paused.
We complete synchronization of the new CRM or MAP data.
We standardize the new CRM or MAP data. The process consists of aligning the new fields with the expected standard model fields.
Migrations for predictive customers include these additional steps:
If you are migrating a CRM, you need to meet with us to discuss opportunity/deal processes, to discuss key standardization fields, and to get a better understanding of any custom process flows or custom fields that you use to classify key data points.
We take a first pass at taxonomizing the new CRM or MAP data. This taxonomy provides a mapping from the CRM or MAP activity types to our model activity types.
We meet with you to discuss the taxonomy and receive an approval to send the taxonomy to the Data Science team to rebuild your intent models.
The models are refreshed, and the CRM or MAP score exports are rebuilt (if they were previously present).
Migration is completed.