CRM migration

    CRM migration with every record counted before and after.

    We move your data into Pipedrive, HubSpot or Zoho: first we map, then we test in staging, then we count. What stays behind, you agree to before we start.

    • Pipedrive Platinum Partner, top 8 worldwide
    • More than 150 CRM implementations
    Lead time
    Usually 2 to 4 weekslonger with large datasets
    Price
    After the inventorydepends on records, objects and integrations
    Counted
    Before and after every runper object, signed off by you
    Platforms
    Pipedrive, HubSpot, Zoho

    Where CRM migrations usually go wrong

    • Duplicates move along.

      Whatever was messy in the old CRM is just as messy in the new one, only now with a fresh import date on it.

    • Fields land in the wrong place.

      A dropdown becomes free text, a date becomes a string, and nobody notices until a report shows nonsense.

    • Automations stop without anyone noticing.

      Workflows and Make or Zapier scenarios still point at the old CRM, so follow-ups silently stop going out.

    • The team keeps two systems open.

      Without a clear cutover date reps keep working in the old CRM, and new data ends up in both.

    How we migrate

    This is the method behind Surge Shift, and the same one our team uses when we do the work for you.

    • Inventory

      Every object, field, pipeline, automation and integration in the old CRM on one list, with owner and record count.

    • Mapping

      Each old field gets a place in the new structure, or a documented reason why it stays behind.

    • Staging

      The data goes into a test environment first. That is where we clean, deduplicate and fix field types.

    • Dry run

      A full test migration on a copy, so the first real run is not also the first time anything is tried.

    • Counts before and after

      After every run we put the numbers from source and target side by side. The counting protocol is further down this page.

    • Rebuilding what does not transfer

      Automations, integrations, reports and permissions are rebuilt in the new CRM and tested on real deals.

    From old CRM to new CRM

    What we do in each phase, and what we need from you. How long the whole thing takes is in the table further down.

    1. Phase 1

      Inventory and mapping

      We list what is in the old CRM. From you: a decision per object on what moves, and who owns which accounts.

    2. Phase 2

      Trial run

      We load the data into staging and run the dry run. From you: a check on a handful of deals you know well, and a yes to the first count.

    3. Phase 3

      Migration and rebuild

      The real run, in batches. From you: who relies on which Make or Zapier scenario, so we reconnect them in the right order.

    4. Phase 4

      Cutover and handover

      Freeze moment, final delta run, training on your own data. From you: a switch date, and from that day on the team works in the new CRM only.

    From practice

    Very good service

    “The Sales Surge Team set up our Pipedrive. They promptly took all the information we gave them and did an excellent job in setting up our sales team in Pipedrive.”

    Christopher Jakoby

    Pipedrive Marketplace, Jun 2026

    Read the review on the Pipedrive Marketplace
    Pipedrive Platinum Partner

    Pipedrive Platinum Partner

    View partner profile

    What it costs

    What does a CRM migration cost?

    Price
    Price after the inventory
    Lead time
    Usually 2 to 4 weeks

    The price depends on the number of records, objects, pipelines and integrations. We name it once we know what is in your CRM. We invoice per phase, always before that phase starts.

    Honestly

    When we would not migrate

    When the old CRM is mostly clutter. Then a clean rebuild with a selective import is often cheaper than moving every problem along. We say so after the inventory, before you pay for a migration.

    What moves in a CRM migration, and what does not?

    People, organisations, deals and notes move. Activities, email, attachments and custom fields move with limits. Automations, integrations, reports and permissions are rebuilt. That split holds between Pipedrive, HubSpot, Zoho and Salesforce, although the details differ per platform.

    The table below is how we discuss it in the first week. Per object you decide with us what goes, and we write down what stays behind and why. That list is part of the plan you sign off.

    ObjectStatusWhat to know
    People and contactsMovesIncluding owner, labels and the link to their organisation.
    Organisations and companiesMovesHubSpot allows a contact on several companies. Pipedrive links a person to one organisation, so we pick the primary one with you.
    DealsMovesOld stages are mapped to the new pipeline. The full stage history usually does not move as history.
    NotesMovesAs text on the right record. Formatting can differ.
    ActivitiesMoves with limitsOpen and recent activities move. Very old completed ones we often leave behind, by agreement.
    EmailMoves with limitsThreads tied to the old inbox do not transfer one to one. Often you reconnect the mailbox in the new CRM instead.
    AttachmentsMoves with limitsPossible per file, but slow and bound by platform limits. We agree which files matter.
    Custom fieldsMoves after mappingField types must match. Dropdown options are created in the new CRM first.
    Automations and workflowsRebuiltThey never transfer. We rebuild and test them.
    Integrations (Make, Zapier)RebuiltEach scenario still points at the old CRM. We list them and reconnect them.
    Reports and dashboardsRebuiltBuilt again on the new data model.
    Users and permissionsRebuiltVisibility and roles work differently per CRM.

    How do you prevent data loss in a CRM migration?

    By counting, and by agreeing upfront what gets counted. A promise of zero loss says nothing if nobody counts. This is the counting protocol we follow on every migration:

    • What we count. Records per object, deals per stage and activities per owner. Three numbers per object, so a gap in one place cannot hide behind a total that happens to add up.
    • When we count. In the old CRM during the inventory, after the dry run, after every batch of the real run and after the final delta run.
    • Who signs off. You do. You get the counts per object side by side and you check a few deals you know well. We only switch over after your yes.
    • What happens with a difference. Every difference gets a written explanation: a record left behind on purpose, a duplicate merged in staging, or a mistake. A mistake we fix in a new run before we carry on.

    What we deliberately leave behind is written down before we start. Think of completed activities from five years ago, or a field nobody has filled in since 2021. You say yes or no to each item. That way nothing disappears by accident, and nothing comes along that you did not want.

    How long does a CRM migration take?

    Most migrations take two to four weeks. The duration depends less on the number of records than on the number of objects, pipelines and integrations. Three scenarios we see often:

    ScenarioWhat it looks likeLead time
    SmallOne pipeline, a few thousand records, hardly any automationsAbout 2 weeks
    MediumSeveral pipelines, custom fields, a handful of Make or Zapier scenarios3 to 4 weeks
    LargeTens of thousands of records, custom objects, a data warehouse or ERP alongsideLonger, planned after the inventory

    The slowest part is rarely the import. It is the decisions: which pipeline structure, which fields stay, who owns which accounts. Teams that make those choices in week one finish fastest.

    From HubSpot, Salesforce or Zoho to Pipedrive: where does it go wrong?

    Each source has its own traps. These are the two we run into most often per platform.

    HubSpot to Pipedrive. First, associations: in HubSpot a contact can belong to several companies, in Pipedrive a person has one organisation. Decide which link becomes primary before you import. Second, lifecycle stages and lists have no direct counterpart. Some become a lead, some a deal, some a label. For this route we also have a dedicated HubSpot to Pipedrive migration and a checklist.

    Salesforce to Pipedrive. Custom objects and record types do not exist one to one in Pipedrive. You flatten them into fields or into separate pipelines. And the logic in flows and validation rules has to be rebuilt as Pipedrive automations, so list it before the move.

    Zoho to Pipedrive. Zoho keeps leads in a separate module that converts into contacts and deals. Decide whether unconverted leads go to the Pipedrive leads inbox or stay behind. Deluge functions and blueprints do not transfer, so those processes are rebuilt.

    Should you deduplicate before a CRM migration?

    Yes. Every duplicate you migrate costs time twice: once in the import and again in the clean-up afterwards. We deduplicate in staging, before the data reaches the new CRM.

    Once you are in Pipedrive, Surge Dedupe keeps it clean. It finds duplicate people and organisations on email, phone and name, and you review every proposal before anything merges. It works in Pipedrive only, so for the clean-up inside the old CRM we use the staging step.

    Do it yourself with Surge Shift, or hand it to us?

    Both work, and the choice mostly depends on where you are going. Surge Shift is our product for a move into Pipedrive, with mapping, staging and a dry run. If you would rather hire a migration agency that counts every record, that is our team, and it also handles a move to HubSpot or Zoho.

    Surge ShiftOur team
    DestinationPipedrive onlyPipedrive, HubSpot or Zoho
    Who does the workYou, with the toolWe do, you decide
    Fits whenOne source, simple structure, someone in house who knows the dataSeveral sources, many automations, a warehouse or ERP, or no time in house
    Automations and integrationsNot included, you rebuild themRebuilt and tested by us
    TrainingNot includedOn your own data, at handover

    Not sure which fits? The Pipedrive implementation page shows what the full setup around a migration looks like, and our guide to CRM data migration walks you through doing it yourself.

    In short

    What does a CRM migration involve?

    A CRM migration moves your people, organisations, deals, notes and recent activities to a new CRM. Automations, integrations, reports and permissions are rebuilt, because they never transfer as they are. Email history and attachments depend on the platform. A typical migration takes two to four weeks, longer with large datasets. You get a price after the inventory, not before.

    Source: Sales Surge, migration method November 2026

    Frequently asked questions about CRM migration

    Which CRMs can you migrate from and to?

    We migrate between Pipedrive, HubSpot and Zoho, and from Salesforce, Monday Sales CRM and most other modern CRMs into one of those three. Pipedrive is where we are strongest: we are a Pipedrive Platinum Partner and, since July 2026, one of the top 8 Pipedrive partners worldwide. For Zoho we are a fully certified partner.

    Can I move HubSpot to Pipedrive with email history?

    Partly. Contacts, companies, deals and notes move. Email threads tied to the HubSpot inbox do not transfer one to one, so you usually reconnect the mailbox in Pipedrive, which brings back mail within the limits of your Pipedrive plan. Older threads that really matter can come along as notes on the right record. We agree upfront which ones.

    What does a CRM migration cost?

    That depends on the number of records, objects, pipelines and integrations, so we name the price after the inventory and not before. You get a fixed price per phase, and we invoice each phase before it starts. Want a first look for free? The Quick Scan shows within 48 hours what is in your CRM and where the work is.

    What if the counts do not match after go-live?

    Then we trace the difference per object, starting from the count of the last run. Often it is a record that was still edited in the old CRM after the freeze moment, or a filter in an export. If something is really missing, we bring it across in a separate run. That is why it helps to keep the old CRM available read-only for the first weeks after go-live, if your subscription allows it.

    Can we keep working during the migration?

    Yes. Your team keeps working in the old CRM while we build and test in staging. Just before the switch we agree on a freeze moment, run a final delta migration for everything that changed since the dry run, and then switch over. We only do that once the counts match.

    What happens to our Make or Zapier integrations?

    They still point at the old CRM, so they have to be reconnected or rebuilt. In the inventory we list every scenario with what it does and who relies on it. Then we rebuild them against the new CRM and test them on real deals before go-live. We are a Make Certified Partner, so most of those scenarios we rebuild ourselves.

    Do you also migrate from Pipedrive to Zoho?

    Yes. Our team does that, because Surge Shift only moves data into Pipedrive. The method is the same: inventory, mapping, staging, a dry run and counts before and after. Zoho does work differently, with separate modules for leads and contacts, so the mapping takes more decisions than a move between two similar CRMs.

    Who on our side needs time during a migration?

    Three people, roughly. Someone who decides on the pipeline structure and which fields stay, because those choices set the pace. Someone who knows the data well enough to check the dry run on deals they know by heart. And whoever owns your Make or Zapier scenarios, so we know who relies on what. How many hours that takes depends on the size of the migration, and we tell you after the inventory.

    Know what your migration involves before you start.

    The free Quick Scan shows within 48 hours what is in your CRM and what a migration would take.

    Or call directly:+31 6 5350 9843