HubSpot migration services, without losing your history.

I move sales, service and marketing teams onto HubSpot from Salesforce, other CRMs, help desks and spreadsheets. Your history comes with you, the team keeps working while it moves, and on day one they're in HubSpot with what they need.

A HubSpot migration moves your records, history and processes from another system into HubSpot. I count what you have, agree with you where it goes, test the move, then switch over at an agreed time, usually with no downtime, and support the team through the first week. Most migrations take from 1 month. Bigger moves, with years of history or several teams, take longer.

How it works, in detail

What makes a HubSpot migration work?

Getting the data into HubSpot is usually the easy bit. What matters is where it lands. If every field from the old system simply becomes a HubSpot field, the old system's quirks come across too, and the reports don't add up.

So before any data goes in, I agree with you what the new portal should look like, and use the move to put the data in the right shape. Everything after that is easier, including HubSpot's own AI, which can only work with what you give it.

How I run a migration

The same six steps whatever you're moving from. The detail changes by source.

  1. Count what you have. I pull a full extract and count everything myself, because every estimate and price depends on that number. I also find out what's actually used, so fields and pipelines nobody opens can stay behind.
  2. Agree where it goes. Which records are companies, which are contacts, which need their own object, and how they link. This is where most of the thinking goes, and you sign it off before anything moves.
  3. Map every field. A sheet with a row per field, saying where it goes and who signed it off. Plenty of fields get dropped here, which leaves fewer for your team to fill in.
  4. Test it first. I load a small batch, check it, remove it, then run and time the full move in a test portal, so there are no surprises on the day.
  5. Switch over. A written plan with a tick box per step: freeze the old system, final load, switch mailboxes and integrations, turn on HubSpot automation, and send a test record through end to end.
  6. Support the team. I stay close for the first week, with short written reports on day one and day five saying what's live, what's fixed and who owns what's left.
Your team keeps working. Most of the history goes into HubSpot while the team carries on in the old system. The last changes come across on switch-over day.

Which systems do you migrate from?

Salesforce, Pipedrive and Zendesk are the moves I'm asked about most.

  • Salesforce to HubSpot. Accounts, contacts, opportunities, cases and custom objects, with the automation rebuilt the HubSpot way. I led this move for a publicly traded global technology company, onto HubSpot Sales, Service and Marketing Hub.
  • Zendesk to HubSpot Service Hub. Tickets, conversations, attachments, organisations, users and groups, plus the macros, triggers and views that need rebuilding.
  • Pipedrive to HubSpot. Deals, pipelines, activities, emails, products and custom fields, plus the Pipedrive habits your sales team will want back.

I also move teams off spreadsheets, booking platforms, home-built databases and other CRMs. For Zing365, booking data from a platform that had been in service for over a decade went into HubSpot, cleaned up on the way. The Zing365 case study has the detail.

Not every migration comes from another system. For a manufacturer, I moved over 80,000 product tests into a proper structure in HubSpot, with a forward schedule across more than 2,300 customer accounts. See how that worked.

What should you decide before a migration starts?

  • What history is worth moving. Ten years of closed deals may be useful. Ten years of automated monitoring alerts usually isn't.
  • Who owns each decision. One named person each for the records, the set-up and the go or no-go call. A migration that stalls is more often waiting on a decision than on a technical problem.
  • The switch-over date. Work back from it. Seat approvals, mailbox changes and training sessions all have lead times.
  • What the old system still does. Web forms and integrations that post into it will carry on doing so unless someone repoints them.

Why one person runs it end to end

I count, design, run the move, train the team and support them afterwards myself, so the decisions made in week one are still understood at go-live.

Client data stays in client systems while I work on it. I'm a HubSpot Gold Solutions Partner.

Peter led our migration away from Salesforce to HubSpot Sales, Service and Marketing Hub. My experience with Peter was exceptional.
John RankinChief Operating Officer, Beonic, ASX-listed global technology business

Questions people ask

Do you migrate from Salesforce?

Yes. Salesforce moves need the most design up front, because years of custom objects, fields and automation rarely map one to one, so I agree what each one becomes in HubSpot before anything moves.

What can you migrate into HubSpot?

It depends on the system you're moving from, but usually most of it. Records like contacts, companies, deals and tickets, their properties and the links between them, plus activity such as meetings, emails, notes, tasks and calls. I check what your system lets out before quoting, so there are no surprises. Pipelines, automation and reports are rebuilt in HubSpot rather than copied, so they work the HubSpot way.

Will we have downtime?

Usually not. On a recent Zendesk move, the team stopped using one system at an agreed time and started in HubSpot, with no downtime. Where a short pause can't be avoided, I keep it as small as possible, tell everyone well in advance and put a plan in place to cover that window.

Can you migrate history, not just records?

Usually, yes. It depends on the system, but most let emails, notes, calls, meetings, tasks and ticket conversations come out with their dates, so they land as activity on the right record in HubSpot. I agree with you what's worth moving, because some of it, like automated alerts, is better left behind.

How long does a migration to HubSpot take?

From 1 month, audit to go-live. A single pipeline with clean data is the quicker end. A help desk with years of tickets and several teams takes longer, mostly because of the testing and the transfer time. What usually adds time is deciding what to bring, what to leave and how things should work in HubSpot, and those decisions need your team.

Do we need a HubSpot sandbox?

It helps. Enterprise portals include one, and it's where I test the whole move and time it. Without one I test a small batch in your live portal and remove it before the full run.

What happens to our old system afterwards?

Keep it read-only for a set period as a fallback, export any reports you want to keep, then switch it off. I write the date into the plan so it actually happens and you stop paying for two systems.

Where to next

Planning a move to HubSpot?

Book a short call. Tell me what you're on now, roughly how much data there is and when the renewal lands. I'll tell you how I'd run it and what to sort out first.

Book a call