How to export your data from Zoho CRM before you leave
Zoho CRM data leaves through an administrator-requested backup, which arrives as CSV files and record attachments in a single ZIP archive, and for scripted pulls through the Bulk Read API. Start by confirming who holds an administrator profile, because only administrators can request a backup. Backups cover module records and attachments, including file and image upload field data, but they exclude email content, documents and data from integrations. Those three categories need a separate extraction plan before you cancel anything.
Backups can be run immediately or scheduled weekly, twice a month or monthly, and the download link stays active for 7 days. Missing that window means requesting another backup, so set a calendar reminder for the day the archive is ready and store the file in your own storage at once. Check how many backups your edition includes before you plan the timeline. Confirm the current allowance with Zoho, since the free backups per edition are set by Zoho and can change. The Zoho CRM help article on requesting a data backup explains the request steps and the download window.
Before you rely on the archive, open the CRM Data folder and sample the CSV files for each module. Compare record counts with the live views, check that lookup fields, custom fields and multi-select values survive intact, and confirm that the CRM Attachments folder matches the files attached to your records. Then pull email, documents and integration data separately, using the mailbox provider, document store or the Bulk Read API for records that the backup skips. Treat these checks as the acceptance test for your receiving system, and document the results so your migration team can trace every record back to its source.
Which Zoho CRM data you can export and how
This table compares the Zoho CRM export routes by what each one includes, how often you can run it and how long you have to download it. Read it first by data type, then by how often you need a copy, since the free backup allowance differs by edition.
| Export route | What it contains | Frequency and limits | Notes for a migration |
|---|---|---|---|
| Module records via backup | CSV files for each module in a CRM Data folder, inside one ZIP archive | Only administrator profiles can request it; two free a year in Standard, Professional and Enterprise, four in Ultimate | Use as the base extract for mapping modules and custom fields to the target CRM |
| Attachments via backup | A CRM Attachments folder with record files and file or image upload field data | Same request and download rules as module records | Confirm attachment file names and links map to the right records before import |
| Backup scheduling | The same CSV and attachment archive produced on each run | Run immediately, or schedule weekly, twice a month or monthly | Schedule a final backup close to cutover so the newest records are included |
| Free edition backups | Same archive format as paid editions | Free edition requires purchasing backup add-ons | Budget for add-ons in the migration plan if you only hold the Free edition |
| Download window | The archive download link | Stays active for 7 days at most | Download and store the archive in your own storage as soon as it completes |
| Email, documents and integrations | Not included in backups | Not available through the backup archive | Plan separate extracts or API calls for these data types |
| Bulk Read API | Module records retrieved by scripted calls for larger or repeated exports | Subject to Zoho API credit limits for your edition, confirm in Zoho's API documentation | Suited to automated, repeatable extracts that the backup archive cannot schedule |
What Zoho CRM backups leave out and how to recover it
A Zoho CRM backup covers module records and attachments, but it does not cover email content, documents or data from integrations. Each gap needs its own source and its own check before you plan an export or a migration.
Email content
Zoho CRM backups exclude email content, so messages linked to contacts, deals or accounts will not appear in the CSV or ZIP archive. Pull them from the mailbox where they were sent or received, or from your mail provider's archive or journaling service. Decide which messages matter for the new system, export them in a standard mail format, and link them to the matching records by email address and date. Confirm with Zoho whether any email content can be reached through the Bulk Read API in your edition.
Documents stored outside record attachments
Files saved in Zoho CRM's document area are not part of the backup, which covers only record attachments and file or image upload fields. Locate these files in Zoho's document section, or in the shared drive or cloud storage your team used alongside it. Build an inventory that lists each file, its parent record and its owner, so you can match files to records after the import. Confirm with Zoho how documents can be retrieved in your edition, because the Bulk Read API may not return them.
Data from integrations
Records that arrived through connected apps, such as marketing tools, telephony, accounting or helpdesk integrations, are excluded from the backup. The source of truth for these records often sits in the connected app itself. Export them from that app's own tools, keep the external IDs, and map them to the matching Zoho CRM records so the new CRM does not create duplicates. Ask each integration vendor which export formats and history limits apply.
Checking the Bulk Read API limits
The Bulk Read API covers scripted exports of module data, but it is not a full substitute for the backup. Before you plan the migration, confirm with Zoho which modules, fields and file types your edition can read through it, and whether any of the three exclusions above can be reached this way. Test a sample export on a non-production org and compare record counts with the backup. Record the answers in your migration plan so the gaps have named owners.
Retention of the backup download link
The download link for a Zoho CRM backup stays active for at most 7 days. If an excluded source is still being pulled when that window closes, you will need to request a new backup, which counts against your edition's allowance. Store the archive in your own controlled location as soon as it is ready, and record the checksum and date. Plan the order of exports so that email, documents and integration data are collected while the backup is still available.
Export sequence and verification for a complete Zoho CRM export
This sequence produces a complete, encrypted copy of your Zoho CRM module records and attachments, plus a documented check that the copy matches the live CRM before anyone relies on it. It separates what the native backup covers from what needs a scripted pull, so gaps are found while Zoho still holds the data.
Confirm an administrator profile is available
Only administrator profiles can request a Zoho CRM data backup, so the first task is to confirm which named users hold that profile and can act during the export window. The export owner should check this inside Zoho CRM's administration settings and record the names in the export log. The step is complete when at least one administrator has confirmed access and a second has been named as backup in case the first is unavailable. Ask your Zoho administrator to confirm this rather than assuming it.
Request the backup or schedule it
The administrator either runs an immediate data backup or schedules one on a weekly, twice-monthly or monthly cycle, depending on the edition and the number of backups still available. Backups in Ultimate edition include four free backups a year, while Standard, Professional and Enterprise include two, and the Free edition needs paid add-ons. Record the request time, the requesting user and the edition in the export log. The step is complete when Zoho confirms the backup is queued and you have the backup date recorded.
Download the archive within the window
Once the backup is ready, download the ZIP archive before the download link expires. Zoho CRM states the link stays active for at most 7 days, so the download should be scheduled as soon as the notification arrives, not left until the end of the week. Confirm the archive opens and that it contains a CRM Data folder and a CRM Attachments folder. The step is complete when the file's checksum is recorded and both folders are present.
Store the archive encrypted
Move the archive into your controlled storage and encrypt it at rest, using an encrypted volume or an archive tool that applies strong encryption with a key held by your security team. Restrict access to named roles and log every copy. The archive contains customer personal data and attachments, so treat it under the same classification as the live CRM. The step is complete when the encrypted copy is verified by decrypting it to a test location and confirming the file count matches the original.
Run Bulk Read scripts for gaps and repeat pulls
The backup does not include email content, documents or data from integrations, and it is a point-in-time file set. For those gaps, and for repeated or larger pulls, use the Zoho CRM Bulk Read API with a script that your developers have written and tested against a sandbox or low-volume module first. Keep the script, its authorization scope and its output in version control. The step is complete when each in-scope module has a script output file with a timestamp, and any API limits or errors are logged for follow-up. Confirm the current API limits with Zoho before scheduling large runs.
Compare record and attachment counts per module
For each module, compare the record count in the archive with the count shown in the live CRM on the same export date, and compare attachment counts for modules that hold files. Note any difference and whether it stems from records created or deleted after the backup, from excluded data or from a failed script run. The step is complete when every module has a recorded count, a variance and a reason for any non-zero variance. Record the results in a reconciliation sheet and keep it with the archive.
Spot-check sample records and files
Select a sample of records from each module, including accounts with multiple related contacts, deals at different stages and records with custom fields, and open each one in the archive and in the live CRM. Open a set of attachments to confirm they are readable and linked to the correct record. Document any mismatch in field values, dates or file links. The step is complete when the sample has been reviewed by someone other than the person who ran the export, with signed notes stored alongside the reconciliation sheet.
How to verify an export is complete before you cancel
Do not cancel the Zoho CRM subscription until the export has passed reconciliation. Reconciliation means comparing what Zoho CRM holds with what your target system and archive contain, module by module. Start with record counts for each module in the CRM Data folder of the backup ZIP, and compare them with counts taken from Zoho CRM itself under the same module. Record the date and time of each count, because records created or changed after the backup will show as differences that are expected, not losses. Check that the number of files, the row totals and the header row of every CSV match what the backup contains, and keep a signed log of the results.
Next, match attachments. Every file and image upload field should have a corresponding file in the CRM Attachments folder, linked to the right parent record through its record ID. Pick a sample of parent records with several attachments, open them in Zoho CRM, and confirm that each file exists in the archive with the same name and a plausible size. Then run field-level spot checks on records with lookups (for example, a contact linked to an account or a deal linked to a contact), multi-select values, currency fields and date fields with time zones. Lookups and multi-select values are where imports most often break silently, so check at least a sample of records from each module by hand.
Finally, write down what the export leaves out and get that list approved. Zoho CRM backups exclude email content, documents and data from integrations, so those categories need a named owner, a retention decision and a plan for recovery. Ask the business owner to sign off on the exclusion list before cancellation, and keep the source account active until every check passes and the sign-off is on file. Confirm current backup and download terms directly with Zoho CRM, using its requesting data backup article, since the 7-day download window means a missed link must be regenerated from a new backup.
What to plan before the Zoho CRM contract ends
Exporting from Zoho CRM is a project with a calendar, not a single button press. The cards below cover the decisions and checks that set the timeline: when notice is due, which backup allowance you have, how long exports take to verify, and what you must confirm in writing before your data is deleted.
Notice period and renewal date
Find the notice deadline and renewal date in your Zoho order form or admin billing view, not in your memory of the sales call. Work backward from the renewal date to set the export, verification and cutover dates. Confirm with Zoho whether the subscription ends at renewal or at the end of a paid term, since that changes when your last usable backup must exist.
Edition and backup allowance
Your edition sets how many backups you can request without buying add-ons. Zoho includes four free backups a year in Ultimate and two a year in Standard, Professional and Enterprise, while the Free edition must buy backup add-ons. Count the backups you have left before you start, and schedule the final full export so it runs well before the contract ends.
Time to run and verify exports
Budget time for three steps: running the backup, downloading the ZIP archive before the link expires, and checking the CSV files against live record counts. Verification often takes longer than the export itself, especially for modules with many attachments. Plan a dry run on a sample module first so surprises show up while Zoho is still your system of record.
Retention rules for the archive
Decide how long the ZIP archive must be kept, who may access it and where it is stored, based on your own legal, tax and records policies. Store it in encrypted storage you control, with a copy in a second location. Record the backup date and edition in the archive metadata so auditors can tie the files back to a specific point in time.
Gaps in the backup
Zoho backups exclude email content, documents and data from integrations, so they are not a complete copy of your CRM activity. List every integration, mailbox sync and document store that feeds Zoho, and decide how each gap will be recovered. Without this inventory, the archive looks complete but leaves out the communication history sales teams rely on.
Access revocation and written deletion terms
Only administrator profiles can request backups, so limit that role during the wind-down and remove access for users, API clients and connected apps once the final export is verified. Ask Zoho in writing how and when your data is deleted after termination, which copies are kept, and how deletion is confirmed. Keep that answer with the contract file.
Questions buyers ask before exporting Zoho CRM data
Can an administrator export Zoho CRM data alone?
Yes, for a standard backup. Only administrator profiles can request a Zoho CRM data backup, so the admin who runs it must hold that profile. The output is a single ZIP archive with CSV files for module records in a CRM Data folder and attachments in a CRM Attachments folder. The effort that grows is not the click but the checking afterward: confirming record counts per module, linking attachments back to their parent records, and deciding what to do about data the backup leaves out. Email content, documents and integration data are excluded, so those need a separate extraction path, usually through the Zoho CRM API. Ask whether your admin has time for that verification work, not only the export itself.
What drives the effort of a Zoho CRM export?
Four factors set most of the effort: data volume, custom modules, attachments and integrations. Large record counts make files harder to open and check in spreadsheets. Custom modules and custom fields need a mapping decision in the target system before any import. Attachments are stored in their own folder and must be matched to records. Integrated data from connected apps is not in the backup, so each integration needs its own plan. Each factor adds work in a different role, so estimate them separately rather than as one number.
How long does a Zoho CRM backup take to download?
The timing depends on the schedule and the download window, not on a fixed duration Zoho publishes for this step. A backup can run immediately or on a weekly, twice-monthly or monthly schedule. The download link stays active for 7 days, so the file must be fetched and stored within that window or the request must be repeated. Plan the schedule around your migration calendar and confirm the current run time for your data volume in your own tenant before you commit a project date.
Do we need a migration services partner for a Zoho CRM export?
Not always. A small CRM with few custom modules and no integrations can often be exported and imported by an internal team using the target system's import tools. A partner becomes more useful when you need mapping of custom modules, rebuilt workflows, extraction of email and integration data, or a staged test before cutover. Use the backup for the bulk of records, and treat the Zoho CRM API as the path for anything the backup omits. Decide this from your inventory of modules, integrations and compliance obligations, not from the export alone.
What does a Zoho CRM data export actually cost?
The cost comes from the components you pay for, not from a single export fee. Zoho's backup count depends on edition: Ultimate includes four free backups a year, Standard, Professional and Enterprise include two, and the Free edition must buy backup add-ons. Other cost components are:
- Internal administrator time for requesting, downloading and checking files
- Scripting time if you use the Bulk Read API or the CRM API for excluded data
- Storage for the archive, attachments and retention copies
- Verification and reconciliation work before the source is retired
- Any integration or email extraction work outside the backup
Ask for each component separately in any quote, and confirm which costs recur, such as storage, and which are one-time.
What does a written fixed-scope quote for a Zoho CRM export include?
A fixed-scope quote should name the work in writing before it starts. Ask the consultant to state the modules and record types in scope, how attachments will be linked to records, how email content and integration data will be handled, the target system and environment, the verification method and sign-off criteria, and the deliverables such as the export files, mapping documentation and reconciliation report. Ask who performs each task, what the client must provide, how changes to scope are priced, and what support follows the cutover. DeployOpen plans and implements fixed-scope engagements, with scope, deliverables and timelines agreed in writing before work begins, and it does not publish a price list, so the quote follows from that written scope.
What should we check in the Zoho backup before deleting the source?
Check that every module in scope has files, that record counts match what Zoho CRM reports, and that attachments in the CRM Attachments folder link to their parent records. Confirm that a sample of records opens correctly with the right field values and relationships. Document what the backup excludes, including email content, documents and integrated data, and make sure each excluded item has a stored copy or a sign-off that it is no longer needed. Keep the archive under your retention policy, and do not retire the Zoho subscription until these checks are signed off by the people who own the data.
How DeployOpen scopes an exit export
An exit export is scoped in writing before any data leaves Zoho CRM. DeployOpen agrees the scope, deliverables and timeline with the client first, and the work does not start until that document is signed off. For a Zoho CRM export, the written scope should name which modules are in, which custom fields and layouts must be documented, whether attachments are included, and which Zoho administrator profile will request the backup. It should also state where the archive will be hosted, because the backup file is a ZIP with a CRM Data folder and a CRM Attachments folder that must be stored in the client's own infrastructure.
The deliverables are typically an export runbook, a verification report and the archived copy hosted in the client's environment. The runbook records each step in order: the backup request, the schedule options Zoho offers (run now, weekly, twice a month or monthly), the download window, and how the files are checked against record counts in Zoho. The verification report compares the exported CSV files with the live CRM and lists what the backup does not cover, such as email content, documents and integrated data, so those gaps are owned by a named person before the Zoho subscription ends. Confirm with DeployOpen in writing whether the report is a count-based check, a sample-based check or both.
Clients should ask for the fixed-scope proposal to separate one-time export work from recurring items. Retention of the archive, periodic re-exports, and any Bulk Read API scripts for larger extracts are different cost lines, and each depends on data volume, number of modules and how many integrations sit outside the backup. Ask DeployOpen to state which items are included in the fixed fee, which are optional, and who on the client side must approve the Zoho backup request and retrieve the download before the 7-day link expires.
How DeployOpen scopes, delivers and supports Zoho CRM exit work
DeployOpen plans and runs Zoho CRM export work inside your own infrastructure, from the first backup request through to a documented, tested archive that your team can keep. Each engagement starts with a written scope so that the export method, the target environment and the handover deliverables are agreed before any data moves.
How we scope
- Confirm which Zoho CRM edition and backup allowance you hold, and who holds administrator rights to request backups.
- Inventory modules, custom fields, attachments and any data outside the backup, such as email content and integrations.
- Agree in writing whether the export uses scheduled backups, Bulk Read API scripts or both, with deliverables listed.
How we build
- Set up the export pipeline in your own cloud account, data center or air-gapped network, with access limited to named staff.
- Script retrieval and checksum verification so each CSV file and attachment folder in the ZIP archive is accounted for.
- Test the archive on a staging copy and record gaps, such as data excluded from Zoho backups, before any cutover.
How we hand over
- Deliver the verified archive, export scripts, field mapping notes and a record of every export run and its outcome.
- Document where the 7-day download window applies and the retention steps your team must follow after each download.
- Walk your administrators through the runbook so the archive and the target environment can be operated without DeployOpen.
How we support
- Engagements are fixed-scope, and any follow-up work is quoted against a new written scope.
- Ongoing support, upgrades and continuous testing of the target environment are available as a retainer.
- Ask your DeployOpen contact to confirm support hours, response terms and escalation paths in the written scope before work starts.
