CRM migration · on quote

Switch CRMs without losing your history, or your teams.

Your current tool is holding back your growth, and a failed migration can cost more than the status quo. Data arrives incomplete, customer history gets lost, and teams drift back to spreadsheets. We migrate you to Salesforce starting from your actual processes and data, and we only cut over once the migrated data has been verified with you.

01What you are facing

The problems we solve.

Your tool can't keep up with your growth

Every new team and every new offering adds another workaround, another repurposed field or another Excel file. Your decisions rest on numbers nobody can reconcile anymore.

You're afraid of losing your history

Years of customer conversations, tickets, deals and notes live in your current tool. A standard export doesn't always capture everything, and it's often on the first customer call after go-live that you find out what's missing.

Your data is scattered and duplicated

The same customer exists three times, spelled three different ways, across the CRM, the support tool and your sales reps' spreadsheets. Migrating as is means importing the mess into a brand-new tool.

You dread pushback from your teams

A CRM imposed on teams who can't find their bearings in it gets bypassed in the first week. On paper, the project is delivered; in reality, nobody uses it.

02Our approach

Assess, build, make you self-sufficient.

01
Assess

Map what you have and what really matters

We inventory your objects, fields, volumes, attachments and integrations, and we talk with the teams who use the tool every day. Together, we decide what gets migrated, archived or dropped, rather than copying everything over by default.

Design the target model and the field mapping

We define, field by field, how your companies, contacts, deals, tickets and custom objects fit into Salesforce. The rules for deduplication, record ownership and historical data are settled at this stage.

02
Build

Clean up, then run trial migrations

We deduplicate and normalize your data before import, then run one or more trial migrations in a test environment. Each trial is checked with record counts and sample reviews, signed off by your business leads.

Cut over on a controlled plan

Cutover follows a written plan: data entry freeze in the old tool, final migration, checks, then opening to users. The rollback scenario and read-only retention of the old tool are agreed before the cutover date.

03
Own

Support your teams after go-live

We train your users on their own data and stay close during the first few weeks to fix issues fast. Your admins get the documentation they need to run the tool without depending on us.

03What we deliver

Deliverables.

  • Dated inventory of your current setup: objects, fields, volumes, attachments, integrations
  • Field-by-field mapping between the source tool and Salesforce, signed off by your business leads
  • Documented data cleansing and deduplication rules
  • Trial migration reports: record counts, rejects, sample checks
  • Cutover plan and rollback scenario
  • User training and admin documentation
  • End-of-migration report: what was migrated, archived or left behind, and why
04Good to know

What Salesforce provides.

  • The Data Import Wizard, available from Setup, imports up to 50,000 records at a time: accounts, contacts, leads, solutions, person accounts, campaign members and custom objects. Which objects you can import depends on your edition. Source
  • Beyond that, Salesforce points to Data Loader, a client application usable through its interface or the command line, for 50,000 to 150 million records; above 150 million, Salesforce recommends a partner or an AgentExchange solution. Source
  • To keep original dates and authors (CreatedDate, CreatedById, LastModifiedDate...), audit fields can be set on creation for a list of objects including Account, Contact, Lead, Opportunity, Case, CaseComment, Task, Event and custom objects, once the "Set Audit Fields upon Record Creation" permission is enabled. SystemModstamp can never be modified. Source
  • Duplicate management: Salesforce provides three standard matching rules (business accounts, contacts, leads, plus a fourth for person accounts if enabled); a duplicate rule can alert the user or block the duplicate from being created. Source
  • HubSpot: record exports (contacts, companies, deals, tickets, custom objects...) are sent by email through a link valid for 30 days; associations are exported with one column per associated object. Source
  • Zendesk: the CSV export includes neither deleted tickets, comments nor ticket descriptions; data exports are not enabled by default (the account owner enables them through Zendesk support); JSON and XML formats and the REST API are the other options. Source
05Frequently asked questions

Straight answers.

How long does a migration to Salesforce take?
It depends on the number of source tools, data volumes, data quality and the integrations to carry over. In other words, it depends on scope, and we set it during the audit, before committing to any timeline.
Can we keep the history of our customer interactions?
For a documented list of objects (accounts, contacts, leads, opportunities, cases, tasks, events, custom objects...), Salesforce lets you keep the original dates and authors on import. What can actually be recovered also depends on what your current tool lets you export: we check this object by object during the audit.
Which tools do you migrate from?
HubSpot, Zendesk, Pipedrive, Microsoft Dynamics, an in-house CRM or spreadsheets. Export options (files, API) and their limits vary from one tool to another and by subscription plan: we qualify them at kickoff.
Will our teams have to stop working during cutover?
We aim to keep the data entry freeze as short as possible, scheduled with you during a quiet period. Its actual length depends on volumes and the checks we agree on, and it is set in the cutover plan.
How much does a migration cost?
Every migration is quoted individually, after an initial conversation and an audit of your current setup. The free Health Check is a good starting point to define the scope.

See also: Custom Salesforce Implementation · our Fast Start offers · Salesforce clouds explained.

Let's talk about your project.

A 30-minute conversation to understand your context, then a quote after scoping.