CRM migration

CRM migration consultancy: moving platform without losing the pipeline

Independent CRM migration and CRM data migration consultancy for moves between Salesforce, HubSpot, Dynamics 365 and other platforms: scoping the data objects, mapping and deduplicating, rebuilding integrations and automations, running in parallel and cutting over with the sales team still selling.

19 yrssenior systems delivery
7finance platforms delivered
39 daysearly on an Oracle to Dynamics migration
22m+assets in the National Grid separation

Delivered for and alongside

ShellBPCapitaBaringaOfgemSmart DCCInsightsFlui TechnologiesExxonMobilVodafoneConstellation SoftwareDeloittePwCEYNational GridElexon

Salesforce to HubSpot, HubSpot to Salesforce, Dynamics to Salesforce: what changes with the direction

CRM migrations run in every direction, and the reasons are usually commercial before they are technical. A Salesforce to HubSpot migration tends to follow a renewal quote that no longer matches how many people use the system. A HubSpot to Salesforce migration follows growth: a second business unit, a partner channel, a product catalogue that needs quoting rules, or an ERP interface that the current setup cannot carry. A Dynamics to Salesforce migration, or the reverse, usually follows a group decision about which vendor the wider estate will standardise on.

The direction decides what you lose. Salesforce record types have no direct equivalent in HubSpot and must be mapped to properties or pipelines, and custom objects in HubSpot need an Enterprise subscription. HubSpot workflows and sequences have to be rebuilt as Salesforce flows, because no tool carries logic across. Dynamics 365 solutions, plug ins and Power Automate flows stay behind entirely, and a Dataverse export arrives as tables that need reassembling into the target's object model.

The vendors have made the data part easier. HubSpot's Smart Transfer pulls contacts, companies, deals, pipelines and stages, products, users and activities from Salesforce, Dynamics 365, Pipedrive, Zoho and others in a one time move, with attachments handled as a separate transfer and the exact scope varying by source, and HubSpot says most businesses leaving Salesforce complete the migration within about three months. Salesforce's Data Loader takes CSV files of up to 150,000,000 records and Bulk API 2.0 accepts 150 million records in a rolling 24 hours. None of that tells you what the data should look like when it lands, which is where an independent adviser earns the fee. For the choice of destination, start with our HubSpot versus Salesforce comparison.

The direction, and the usual reason

SalesforceHubSpotA renewal quote that no longer matches usageHubSpotSalesforceGrowth: a new unit, a partner channel, quoting rules, an ERP interfaceDynamicsSalesforceA group decision on which vendor to standardise on The reasons are usually commercial first. The direction then decides what you lose.
Salesforce to HubSpot

A renewal quote that no longer matches usage

HubSpot to Salesforce

Growth: a new unit, a partner channel, quoting rules, an ERP interface

Dynamics to Salesforce

A group decision on which vendor to standardise on

The reasons are usually commercial first. The direction then decides what you lose

The data objects, field mapping and deduplication

Every CRM migration moves the same family of objects, whatever the vendors call them: accounts or companies, contacts, leads where the source has them, opportunities or deals with their stages and pipelines, activities (calls, emails, meetings, notes and tasks), attachments, products and price books, users and any custom objects. We scope each one with three questions: does it move at all, how far back, and who signs off that it landed correctly.

Field mapping is the slow, decisive work. Picklist values rarely match, so a twelve stage Salesforce pipeline becomes a seven stage HubSpot one with a written rule for every conversion. Owners must map to active users in the target or records arrive orphaned. Currencies, record types and lookup relationships need a decision before the first test load, not after. HubSpot's import tool takes files up to 512 MB and 1,048,576 rows, and paid portals can import ten million rows a day; the constraint is the mapping document, not the pipe. Dynamics 365's import wizard caps files at 8 MB, or 32 MB zipped, and Microsoft recommends 20,000 rows or fewer per file, pointing larger loads to the API.

Deduplication has to happen before the load, because the target will not do it the way you expect. HubSpot matches contacts on email and companies on domain, and an import file with two rows sharing an email rejects those rows rather than merging them. Salesforce relies on matching rules and duplicate rules, which can block or warn but cannot merge a lead into a contact. We profile duplicates in the source, agree survivorship rules with sales operations, merge in the source where history matters and in the staging file where it does not, and keep a cross reference of old and new identifiers so the integrations can be rewired. The same discipline sits behind our data migration consultancy for ERP programmes, and the lessons in ERP data migration: what goes wrong apply to CRM data too.

Field mapping, stage by stage

SOURCE: 12 STAGESTARGET: 7 STAGES Stage 1Stage 2Stage 3Stage 4Stage 5Stage 6Stage 7Stage 8Stage 9Stage 10Stage 11Stage 12 Stage 1Stage 2Stage 3Stage 4Stage 5Stage 6Stage 7 Decide before load one A written rule per stageOwners mapped to active usersCurrencies and record typesLookup relationships Illustrative. The constraint is the mapping document, not the pipe.

Import limits by platform

HubSpot import512 MB, 1,048,576 rows a file; 10m rows a day on paid portalsDynamics 365 wizard8 MB, or 32 MB zipped; 20,000 rows a file recommendedSalesforce Data LoaderUp to 150,000,000 recordsSalesforce Bulk API 2.0150 million records in a rolling 24 hours

Integrations, automations and reports are rebuilt, not migrated

Data is the part everyone budgets for. The work that overruns is everything attached to it. Automations do not travel: Salesforce flows, and any Workflow Rules and Process Builder processes still running after their end of support in December 2025, must be rebuilt as HubSpot workflows or Dynamics flows, and HubSpot sequences must be rebuilt in Salesforce. The right move is to inventory every automation, retire the ones nobody can explain, and rebuild the rest from a written description of what they do rather than a copy of how they do it.

Integrations are next. The ERP interface, the marketing platform, the website forms, the telephony, the finance system that posts invoices back to the account, the data warehouse feed: each one has a source system identifier buried in it that changes on migration day. The HubSpot to Salesforce connector is built for ongoing two way sync rather than a one time move, can use up to four API calls per contact each sync, and HubSpot warns that running it alongside a Smart Transfer creates duplicates, so the two cannot both be live at cutover. Our CRM integration page covers the rebuild patterns.

Reports and dashboards are rebuilt from the questions they answer, not from their field lists, and this is the chance to retire the ones nobody opens. Email and calendar sync, mobile apps, document templates and e signature links are reinstalled per user and need a setup guide and a support rota for the first fortnight. Training is designed around the moments that changed: how to log a call, how to move a deal, how to find the account history that used to live in the old system. Where Salesforce is the destination, our Salesforce implementation consultancy covers the build; where HubSpot is, see HubSpot consultancy.

Rebuilt, not migrated

Source identifierschange on migration day ERP interfaceMarketing platformWebsite formsTelephonyFinance invoicesData warehouse feed Automations, reports, email sync and templates are rebuilt too. Keep a cross reference of old and new IDs.
Integrations rebuilt

ERP interface, marketing platform, website forms, telephony, finance invoices, data warehouse feed

Source identifiers change on migration day

Keep a cross reference of old and new IDs

Also rebuilt

Automations, reports, email sync and templates

Parallel running, cutover and adoption

A CRM cannot be frozen for a month, so the migration plan has to let people keep selling. We run at least two full trial loads into the target, reconciling record counts, pipeline value by stage and activity counts by owner against the source, and we hand the comparison to sales operations rather than marking our own homework. The final load is a delta: everything created or changed since the last trial, loaded over a weekend with a short freeze on edits in the source.

Parallel running is tempting and usually wrong. Two live CRMs mean double entry, two versions of the pipeline and a sales team waiting to see which one management reads. We prefer a short overlap with the old system read only, a named owner for every integration on cutover day, and a hypercare period with a visible fix list. Adoption is measured from day one in the target's own usage reporting. The old system is switched off on a date agreed before the migration begins. Salesforce subscriptions renew automatically for a year unless notice is given at least 30 days before the term ends, so the cutover date and the renewal date have to be planned together.

On the BP Pulse programme, where PEF held the main contract, the Oracle to Microsoft Dynamics migration landed 39 days ahead of forecast and cut billing errors, and the same cutover discipline applies to a CRM. The consultants on our bench have led and analysed the decisions before, during and after CRM platform moves. Since Dynamics 365 is often the source or destination: PEF's basic membership of Microsoft's AI Cloud partner programme carries no Solutions Partner designation and no fees or incentives from Microsoft. Under Part A we assure a migration run by your team or a vendor partner; under Part B our practitioners run it. Our fees are shown plainly on the pricing page; contact us to talk through the move.

Cutover without stopping the sales team

Trial load 1ReconcileTrial load 2ReconcileFinal delta,short freezeOld systemread onlyHypercare Reconcile record counts, pipeline value by stage and activity counts by owner, signed off by sales operations.Two live CRMs mean double entry, so a long parallel run is usually wrong.

What we have delivered

22m+assets, National Grid separation

Ran the procurement of every software provider on the National Grid separation, more than 22 million assets, through to implementation including Oracle to SAP S/4HANA.

£25msaving at BP Pulse, 39 days early

Delivered the Oracle to Microsoft Dynamics migration at BP Pulse 39 days ahead of forecast, with a £25m saving, the largest on a programme where PEF held the main contract.

£9bnEnergy Bills Support Scheme

Delivered the £9bn Energy Bills Support Scheme for Ofgem, BEIS and HMRC.

19 yrsfinance systems delivery

Implemented and delivered most major finance systems over 19 years: Oracle, Microsoft Dynamics, NetSuite, Sage, SAP S/4HANA, Unit4 and Access.

ERP and CRMpre, mid and post migration

A suite of consultants who have led and analysed pre, mid and post migration decisions and implementations across ERP and CRM platforms, independent of every vendor.

Questions we are asked

How long does a CRM migration take?

HubSpot says most businesses moving from Salesforce complete the migration within about three months, and that is a fair planning figure for a single team with one or two integrations. Add an ERP interface, a marketing platform, custom objects and several years of attachments and the realistic range is longer, because the work is in the mapping, the automation rebuild and the trial loads, not the final transfer. We plan from your object counts and integration list.

What data can be migrated from Salesforce to HubSpot?

Accounts become companies, contacts and leads become contacts, opportunities become deals with mapped pipeline stages, and calls, emails, meetings, notes and tasks move as activities. HubSpot's Smart Transfer handles these as a one time move and treats attachments as a separate transfer. Custom objects need a HubSpot Enterprise subscription, record types have to be mapped to properties or pipelines, and automations, reports and integrations are rebuilt rather than migrated.

Should we run the old and new CRM in parallel?

Only briefly, and only with the old system read only. Two editable CRMs produce double entry, two pipelines and a team waiting to see which one leadership reads. A short overlap for reference, a final delta load over a weekend, named owners for every integration on cutover day and a visible hypercare fix list protect the business better than months of parallel running.

Do we lose our email and activity history when we change CRM?

Not if it is scoped in. Calls, emails, meetings, notes and tasks can be imported into HubSpot and loaded into Salesforce, but every activity needs a valid owner and a parent record in the target, and years of history inflate storage and load times. We agree a cut off with the sales leadership, archive what sits beyond it in a searchable form, and reconcile activity counts by owner after each trial load.

What does a CRM data migration cost?

Our fees are shown plainly on the pricing page. The cost drivers are the number of objects and custom fields, the volume and age of activities and attachments, the number of integrations and automations to rebuild, the quality of the source data and how many trial loads are needed before sign off. Vendor tooling such as HubSpot Smart Transfer and Salesforce Data Loader comes with the platforms, so the spend is in people and time.

Changing CRM platform?

Get the data model, the mapping and the cutover plan agreed before the first record moves.

Book a conversation