A CentrixOne to Zoho One migration is only finished once it has been verified. This is the checklist Nuagix applies at the end of every migration, published as is so any business owner can check their own data, whoever performed the transfer.
- Compare record counts, type by type, between CentrixOne and Zoho.
- Check relationships: every contact under the right account, every deal and activity on the right record.
- Check a sample field by field, including the original owner.
- Count and open documents and attachments.
- Validate each automation before turning it on.
- Shut down old integrations, replace website forms and authenticate the sending domain.
- Run the delta load before CentrixOne closes, then require a written comparison report.
1. Compare counts, type by type
The first check is arithmetic. For each data type, record the count in CentrixOne before cutover, then the count in Zoho after loading. In Zoho CRM, the list view shows the module's total record count; use an unfiltered "All" view.
| Data type | Where to count in Zoho | Watch for |
|---|---|---|
| Accounts (companies) | Accounts module, "All Accounts" view | Merged duplicates explain a lower count: it must be documented. |
| Contacts | Contacts module | A unique email field can silently skip records during import. |
| Deals | Deals module, by pipeline | Also compare total amounts by stage. |
| Activities and notes | Related tasks, meetings, calls and notes | Dates must be the original ones. |
| Lists and segments | Views, tags or Zoho Campaigns lists | Dynamic lists are rebuilt, not migrated. |
| Custom fields | Settings → Modules and Fields | Every picklist value must match character for character. |
| Users and roles | Settings → Users, Roles, Profiles | An inactive user can still own records. |
| Documents and attachments | Record attachments and Zoho WorkDrive | Count and size, not just count. |
| Emails and templates | Email templates | Subjects and merge fields are reviewed one by one. |
| Automations | Workflow rules | They are rebuilt, not migrated. |
| Web forms | Zoho Forms | The website code must be replaced, or requests still go to CentrixOne. |
| Reports and dashboards | Zoho CRM or Zoho Analytics | Rebuilt according to the decisions actually made with them. |
| Sales stages | Pipeline settings | The old stage → new stage mapping must be written down. |
2. Check relationships, not just records
Matching counts do not prove that links are correct. A successful migration keeps the data, its ID, its parent and its relationships.
- Every contact is attached to the right account.
- Every deal is linked to the right account and contact.
- Activities, notes and emails appear on the right record, on the right date.
- The original CentrixOne ID is kept in a dedicated field: it is used for the delta load and any later fix.
- Every record keeps its original owner, not the account of the person who ran the import.
3. Check a sample field by field
Pick about twenty representative records — old and recent, simple and busy — and compare them screen by screen with CentrixOne: every field, date and picklist value. Typical errors are altered accents and apostrophes, swapped day-month dates, picklist values spelled differently and truncated phone numbers. An error found in the sample exists across the whole volume: fix it before going further.
4. Count and open documents
Documents are the most often incomplete part of a migration, because they are spread between the library and record attachments.
- Compare file count and size, record by record, against the starting inventory.
- Open a sample of each file type (PDF, images, Office documents): a file of the right size can still be unreadable.
- Check files with identical titles: they are matched by title and date, never by title alone.
- Confirm where large files are stored (WorkDrive) and the link from the record.
5. Validate each automation before turning it on
Automations should be rebuilt inactive, then turned on one at a time after validation. Turning rebuilt rules on all at once risks emailing your whole database on cutover day.
- Review each rule: trigger, conditions, actions.
- Check the recipients and text of every automatic email.
- Account for delays imposed by Zoho, which are not always those of CentrixOne.
- Turn on one rule at a time and watch its first real run.
6. Shut down the old system
Cutover is only complete when nothing feeds CentrixOne anymore.
- Replace website form code with Zoho Forms, then test them.
- Shut down integrations and Zaps that still write to CentrixOne.
- Authenticate the sending domain (SPF, DKIM) before the first bulk send from Zoho.
- Check that consents (CASL, Law 25) followed the contacts.
- Send user invitations and plan training.
7. Run the delta load, then require a written report
Between extraction and cutover, the team keeps working in CentrixOne. The delta load picks up those additions and changes using the original ID. It is impossible after CentrixOne closes: it is the one step that cannot be made up later.
The migration ends with a comparison report: one line per data type, the count in CentrixOne, the count in Zoho, and a one-sentence explanation of each gap. The report separates what migrated in full from what shows a gap, and states plainly what did not migrate.
An unexplained gap becomes a complaint. A gap explained in one sentence becomes a decision.
Frequently asked questions
How long does it take to verify a CentrixOne to Zoho migration?
For an SMB, counts and the sample take a few hours. Validating automations and documents takes longer, depending on how many there are. The delta load must be scheduled before CentrixOne's closing date.
Are CentrixOne automations migrated automatically?
No. Automations, templates, views, reports and forms are rebuilt in Zoho. They should be created inactive, then validated and turned on one by one.
What if the counts don't match?
Every gap must be explained: merged duplicates, records deliberately excluded, records skipped by the import. A gap with no explanation signals a problem to fix before CentrixOne closes.
Can Nuagix verify a migration done by someone else?
Yes. Nuagix applies the same checklist to an existing migration and delivers a written comparison report, with the corrections to make.
Need an independent check of your migration?
Nuagix is a Quebec-based company founded in 2011 and a Zoho Premium Partner since 2019, with more than 350 implementations and more than 250 optimizations of existing clients. Nuagix received the Sales Achievement award at the Zoho Partner Awards 2024.
Book a Zoom meeting