6sense Sales Intelligence migration checklist: moving your sales team without losing data

6sense sells Sales Intelligence alongside its Revenue Marketing product. In May 2026 6sense announced that its RevvyAI assistant was generally available for Sales Intelligence customers at no additional cost, working inside Sales Intelligence and through the 6sense Chrome extension on LinkedIn profiles, Sales Navigator, Salesforce, Salesloft and Outreach, with HubSpot support described as coming soon. The same announcement added custom roles, SSO role and group mapping with SCIM, and audit log exports.

Those details matter for a migration. They tell you where reps will meet the tool, which integrations to test first and which security settings your IT team will ask about. Confirm the current list of integrations and what your contract includes with 6sense directly before you plan, because packaging changes.

• List every field the current sales intelligence tool writes on Lead, Contact and Account, with fill rates.
• Note which fields drive routing, scoring, territories or reports. Those cannot change silently.
• Export the current users, their roles and how often each one logs in.
• List the sequences, plays and saved searches reps rely on, and which tool feeds them.
• Record contract end dates, export rights and how long data can be kept after cancellation.
• Pick 200 to 500 target accounts as a comparison set for data quality checks.

In 6sense deployments the platform typically writes its own fields to Account, Contact and Lead in Salesforce and reads CRM activity back into its models. GitLab's public handbook, for example, describes a bidirectional 6sense and Salesforce integration with 6sense fields on all three objects, segment names synced to Salesforce through an orchestration, and sales users reviewing profile fit, account reach and buying stage in Salesforce. Your setup will differ, but the principle holds: decide what each field is for before data starts flowing.

Write the rules in a one-page mapping document that RevOps owns. It becomes the reference when a rep asks why a phone number changed.

1. Set up roles that match job functions (SDR, AE, manager, admin), using custom roles where available.
2. Connect SSO and, if your IT team uses it, group mapping so access follows the directory.
3. Install the Chrome extension for a pilot team and test it in LinkedIn, Sales Navigator and your CRM.
4. Rebuild the five saved searches and two sequences the pilot team uses most.
5. Run the pilot for two to four weeks and compare contact match and accuracy on the comparison set.
6. Collect three things from reps: what they used daily, what they could not find, and what they stopped doing.

• Switch routing, scoring and territory rules to the new fields in one planned change, not field by field.
• Update dashboards so managers see 6sense data in the views they already use.
• Retire old saved searches and sequences, and archive legacy fields after the comparison window.
• Track weekly active users, contacts added and sequences enrolled per rep for the first 60 days.
• Hold a 30-minute review with sales managers at weeks two, four and eight.
• Cancel or downgrade the old tool only after reports and sequences run cleanly on the new data.

The expensive mistakes are rarely technical. Teams connect the integration before writing overwrite rules, and a week later reps find their edited titles and numbers replaced. Or they roll out to every rep at once without rebuilding the saved searches people actually use, so adoption collapses and managers conclude the data is worse. Or they cancel the old contract before comparing data on the same accounts, and lose the ability to prove anything either way.

If the migration is part of a wider 6sense rollout, our 6sense implementation checklist covers segments, intent keywords, buying stages and orchestrations. If you are still choosing a platform, our Demandbase vs 6sense comparison sets out where each fits.

We have implemented 6sense for more than five large enterprises, and we know where rollouts lose data and adoption.

We are also an official Demandbase partner, so we work on both sides of the ABM platform decision. For a Sales Intelligence migration we own the field mapping, the CRM changes and the adoption reporting, and work with your 6sense team on configuration.

Book a free 30-minute pipeline plan if you want a second pair of eyes on the cutover plan.