Back to blog
Engineering•March 15, 2024•4 min read

Moving 20 years of CRM data without stopping the business

At Taycor I led the migration of a CRM system that had been in place for two decades onto Salesforce. Twenty years is a long time for a system to accumulate habits. There were processes nobody had written down, fields that meant something different than their label, and a team that relied on all of it every single day.

The thing I learned is that moving the data is the easy part. The hard part is that the business cannot pause while you do it.

Map the processes before you touch the data

Before any migration I spent the time mapping how the company actually worked, not how the org chart said it worked. Where a record came from, who touched it, what happened next. A lot of that lived only in people's heads. If you skip this step you will faithfully migrate a broken process into a shiny new system, and now it is harder to fix.

A migration is a chance to understand the business, not just copy its database.

Bring the people, or the system fails quietly

You can get every integration right and still have the project fail if the team does not trust the new tool. So training was not an afterthought, it was half the project. I walked the whole team through the new system, mapped old habits to new ones, and made sure the people doing the work every day felt like the change was done with them, not to them.

How I would frame a migration like this:

  • Map the real processes first. The undocumented ones are the ones that bite you.
  • Phase it. Move in pieces you can verify, not one big risky cutover.
  • Treat integrations as the plumbing that has to keep the business running mid-move.
  • Budget as much for training as for the technical work. Adoption is the deliverable.

When it was done, the data was cleaner and the processes were clearer, but the part I am most glad about is that nobody's Monday broke while we did it.