So You’re Moving 10,000 Contacts from Salesforce to Zoho. Here’s What Actually Happens.

On paper, moving contacts from one CRM to another sounds like exporting a spreadsheet and importing it into another CRM. Anyone who’s done it at any real scale knows that’s roughly true for about the first hour, and considerably more complicated for every hour after that.

Here’s what a migration like this genuinely involves at a scale where shortcuts start to matter.

The export is never as clean as it looks

By the time a business decides to move off Salesforce, the data’s usually accumulated years of mess. Custom fields get added and abandoned, duplicates creep in through years of manual entry and old imports, and information sometimes ends up in fields it was never really intended for. A phone number in a notes field, a job title where an address should be, that sort of thing.

None of it looks like much of a problem until you’re staring at an export file with 10,000 rows and realising that the column headings don’t necessarily tell you what’s in each column. Sorting that out before anything gets migrated is a big part of the work. There’s little point in moving years of messy data into a brand-new CRM and then having to clean it up there.

Where does all that data actually go?

Salesforce and Zoho don’t structure everything in the same way, so very little maps across perfectly without someone making a decision. A custom Salesforce field might not have an equivalent in Zoho, which means deciding whether to recreate it, combine it with something else or leave it behind. Relationships among records, record types, and validation rules require the same treatment.

The important thing is that the data still works when it arrives. A migration isn’t successful just because all 10,000 contacts appear in Zoho. They need to be in the right places, connected properly and usable by the people who rely on them.

What happens to all the workflows?

The data is only part of what you’re moving. Salesforce may have lead scoring, assignment rules, email alerts, approval processes, and other automations running behind the scenes, and none of those is automatically reflected in the contact records.

They need to be rebuilt in Zoho and tested there. It’s also a good opportunity to look at what you’ve got running. Some workflows will still be useful, some may need changing, and there will probably be a few that nobody quite remembers setting up in the first place.

Why test before moving everything?

Before the full migration happens, it’s worth running the process on a smaller batch of records. A few hundred contacts is enough to check that fields have landed where they should, relationships are intact, and the important automations are doing what they’re supposed to.

Finding a mapping error in a test batch of 300 takes an afternoon to fix. Finding the same error after 10,000 contacts have already moved is a much longer conversation.

What happens when you switch over?

By the time the live migration happens, most of the difficult work should already be behind you. The data has been checked, the mappings have been tested and the workflows are ready to go.

There is still the people side to deal with. The team needs to know where things have moved, what’s changed and how they’re expected to use the new system. Even a technically successful migration can be frustrating if everyone arrives in Zoho and has to work out the new setup for themselves.

So, what does a migration like this involve?

It’s careful, fairly unglamorous work. You need to understand what the existing data contains, decide what is worth taking across, map it properly into the new system, rebuild the processes around it and test everything before making the switch.

That’s also why a CRM migration is rarely something worth rushing. Done properly, your team should arrive in Zoho with clean data, working processes and a system they can rely on, rather than spending the next six months discovering what didn’t make the journey.

If you’re planning a move from Salesforce to Zoho, speak to the Caldere team. We’re happy to talk through what’s involved before you start moving anything.