Leaving Zoho CRM without losing your records
Kazee team · · 6 min read
Moving away from any CRM makes people nervous, and with good reason. Years of customers, deals and notes sit in there. When a move goes wrong, it is rarely dramatic. A note goes missing here, a deal loses its link to its customer there, and nobody finds out until a customer calls.
Zoho CRM gives you real ways to get your data out, and this guide uses Zoho's own documentation to explain them. It works whichever system you are moving to. Zoho can change its limits, so check the linked pages before you start.
First, check that leaving will fix the problem
A new CRM will not fix unclear sales stages, or a team that does not update records. Those problems will follow you. Before you plan a move, write down exactly what is not working, and check whether a change inside Zoho would solve it. Zoho CRM is a broad, established product, and leaving is a lot of work if a settings change would do.
List what you have
Open your Zoho CRM and write down everything in it. A spreadsheet with one row per item is enough.
- Core records: leads, contacts, accounts and deals, with a count for each.
- Linked work: tasks, meetings, calls and notes.
- Files and email: attachments, documents and emails linked to records.
- Custom work: custom modules, custom fields and picklist values.
- People: active and inactive users, and who owns what.
- How it runs: workflows, reports, views, templates, web forms and integrations.
Mark each row as move, archive or leave behind. You probably do not need ten-year-old lost leads in your new system, but you may want them in an archive.
Take a full copy before you touch anything
This is your safety net. Zoho documents two main ways to take a copy, and many teams will want to use both.
- Module export. Zoho's export page says users with the Export (Module) permission can export a module as CSV or XLSX. The maximum is 200,000 records from a single module in one go in CSV, and 50,000 in XLSX. For larger modules, Zoho suggests splitting exports using Created Time criteria. The number of exports a day varies by edition, and the download link lasts seven days.
- Data backup. Zoho's backup page says users with an administrative profile can request a backup of the whole account, as CSV files in a ZIP archive, with attachments in their own download. How many backups you get depends on your edition, so check before you plan around one. The link stays active for up to seven days, so download it promptly.
Read the backup page's list of exclusions closely. It says email content and attachments, documents, and data obtained through integrations are not part of the backup, and that backing up emails with IMAP configuration is not supported. If your team relies on any of those, work out separately how you will keep them, and ask Zoho support if you are unsure.
If a developer is helping, Zoho also has a Bulk Read API. Its limitations page says it does not support Notes, Attachments, Emails, or related and cross modules, so those need their own plan.
Keep the copy unchanged, in a secure place, and work only on a duplicate. Zoho's backup page also advises against changing the unique IDs in the backup files, because that will impede restoration.
Clean up while you are still in Zoho
It is easier to fix records in the system you know than after the move.
- Merge duplicates. Do this for contacts and accounts first, so deals stay with the right customer.
- Sort out record owners. Records owned by people who have left need a new owner. Zoho's page on deactivating users talks about transferring ownership of records before you deactivate someone, so do this in the right order.
- Standardise the fields that matter. Phone numbers in one format, one spelling for each county or branch, and clear stage names.
- Delete with care. Zoho says you can restore records from the recycle bin within 60 days, after which they are permanently deleted. Your full copy protects you beyond that.
Map the fields, then test with a small sample
Write out how each field in Zoho maps to a field in the new system. Decide what happens to fields with no match: create them, combine them or archive them. Do the same for users, so records arrive with the right owners.
Then move a small sample before anything else.
- Import a sample. Pick records that test the edges: an old account, a big deal, a contact with attachments and a record with odd characters in the name.
- Check by hand. Open each one in both systems. Does the contact still belong to the right account? Does the deal still belong to the contact? Are dates and amounts right?
- Run the full import. Then compare the count for each module against the counts on your list.
- Check the totals. Compare open deals by stage and by owner in both systems. A mismatch here finds problems a record count will miss.
- Let the sales team check. Ask each person to open their five most important customers.
Plan the switch
Set a date, and choose one source of truth at every stage. While both systems are running, people should know which one they update. Editing the same record in two places is how changes get lost.
Then rebuild what is not a record. Workflows, reports, views, templates and web forms generally do not travel with a record import, so use your list and rebuild only what people really use. Check everything that feeds Zoho today, especially the forms on your website, so that new enquiries do not keep arriving in a system nobody is watching.
Close the old account last
Do not close your Zoho account on the day you switch. Keep it for at least one full sales cycle, in case someone finds a gap.
When you are ready, take one final backup. Zoho's page on deleting a CRM account sets out the conditions, including deactivating other users and ending your subscription, and notes that you can download a backup of your data and attachments first. The Zoho privacy FAQ explains what follows: data from a closed account is deleted from the active database at the next clean-up, which happens once in six months, and from backups three months after that.
Your own copies need attention too. They hold personal data, and a summary of Kenyan data protection law notes that data should not be kept in a form that identifies people for longer than necessary. Decide how long you will keep the archive, who can open it and when you will delete it.
Where Kazee fits
If you are thinking of moving to Kazee CRM, it has a Zoho CRM import wizard in Settings › Integrations. It connects to your Zoho account, maps Leads, Contacts, Accounts and Deals with their fields and users, and shows a preview before you import. Afterwards it can refresh records every hour, every 6 or 12 hours, daily or weekly, or only when you press Sync now, so both can run side by side while your team switches.
Those four are the modules we name on our site, so ask us about anything else on your list, such as notes, attachments or emails, before you set a date. Keep your full Zoho copy either way, and rebuild your automations in the new system.
Wherever you are heading, the order stays the same: list, copy, clean, test, switch, and close last. If you would like to walk through your own list with us, book a demo and we will show you how the import looks.
Sources
- Zoho CRM help: Export CRM Data
- Zoho CRM help: Requesting Data Backup
- Zoho CRM API v8 documentation: Bulk Read API limitations
- Zoho CRM help: Activate and deactivate users
- Zoho CRM help: Recycle bin
- Zoho CRM help: Delete Zoho CRM Account
- Zoho: Frequently Asked Questions on Privacy (updated 12 January 2025)
- DLA Piper, Data protection laws of the world: Kenya (last modified 23 March 2026): section 25 principles