Migration scope is agreed with you in writing before any data is touched, covering what is extracted, who handles it, and how long it is held. Data is mapped, migrated into a test environment first, and validated by your team before anything reaches production. Cirro does not retain your business data beyond what the engagement requires.
The sequence
- Scope agreed in writing. Which records, from which source, and what happens to the extract afterwards. Cirro's privacy policy states that we do not collect or store client business data unless explicitly required and consented to in writing for a specific project. Migration is one of those cases, and it is documented.
- Assessment on a sample. A sample tells us about volume, duplicates, missing fields, and inconsistent formatting. Data quality problems are almost always worse than expected, and finding that early is better than finding it at cut-over.
- Mapping, reviewed by you. You see how each source field lands in Zoho before the migration runs. This is where you catch the field that means something different in your business than the name suggests.
- Test migration. The migration runs into a non-production environment first. Your team checks a defined set of records against the source.
- Production cut-over. Only after you have signed off the test run.
Cross-border and retention
Cirro does not transfer personal data outside India by default. Where a project requires it, that happens only with your explicit consent and in line with applicable law. Working extracts are disposed of once the migration is complete and validated. The full position is in the Cirro privacy policy.
What this means for you
Ask for the migration scope in writing before signing, and ask specifically what happens to extracts after cut-over. Any partner should be able to answer both without hesitation.
Next step
If you are moving from an existing CRM, read We are on Salesforce or HubSpot. Is moving to Zoho worth it?
Related articles