Migrate from OneSuite to Zoho CRM

OneSuite Clients map to Zoho Accounts for company records and Zoho Contacts for person records, determined by the presence of a companyName field. OneSuite contact-level fields (email, phone, social links) map to Zoho Contact fields; company-level fields (ICP status, revenue) map to Zoho Account fields. We pre-create the Zoho Account before inserting dependent Contacts to satisfy the Account Name lookup requirement.

OneSuite Leads map directly to Zoho Leads. Pipeline stage names from OneSuite migrate as Zoho Lead Status picklist values, and source attribution data migrates to the Lead Source field. Lead scoring values from OneSuite's scoring system transfer to a custom numeric field on Zoho Lead. Any OneSuite Leads with stage names not yet configured in Zoho are flagged during discovery for picklist value addition before migration.

OneSuite Projects do not have a direct standard equivalent in Zoho CRM. We map Projects as a custom Projects module in Zoho CRM (or as a set of related Tasks with a Project identifier field) depending on the customer's use case. The Client-to-Project relationship is preserved as a lookup from the custom Projects module to the Zoho Account. Milestones and task assignments migrate as Task records linked to the Projects module or parent Account.

OneSuite Invoices map to Zoho Quotes in the standard CRM module, with line items preserved as Quote Item rows. Tax rates, currency, and payment status transfer to Quote fields. If the customer licenses Zoho Books, we flag Invoices for migration through the Zoho Books API instead of the CRM, since Books handles multi-currency and tax configuration more robustly. Complex multi-currency invoices or custom tax configurations are flagged for manual reconciliation.

OneSuite Documents associated with Clients migrate as file attachments on the corresponding Zoho Account or Contact record. We transfer document metadata (name, type, URL, upload date) but do not migrate binary file content if the total file volume exceeds the customer's Zoho storage allocation. File URLs are preserved as text fields so that linked external storage (e.g., OneSuite's document URLs) remains accessible post-migration.

OneSuite Files attached to Projects, Tasks, or Invoices migrate as Zoho Attachments on the corresponding record. We pre-scan total file volume against Zoho's storage limits for the customer's plan tier. Files exceeding the tier cap are migrated as URL references rather than binary attachments, with a flag in the migration report for post-migration storage planning.

OneSuite Members (team users) map to Zoho Users. We match Members by email address to Zoho User records in the destination tenant. Any Member without a matching Zoho User is placed in a reconciliation queue for the customer's admin to provision before the migration continues, since Owner lookups on Accounts, Contacts, and Deals require a valid User reference.

OneSuite Pipeline Stages are user-defined picklist values on the Lead entity. We extract the full stage list during discovery and add any missing values to the Zoho Lead Status picklist before Lead migration begins. Custom automation or scoring rules attached to specific stages are documented in the migration inventory for manual reconfiguration in Zoho Blueprint or Workflow Rules.

OneSuite Project and Document templates contain metadata and field structure that we capture in the migration inventory. Template automation logic (workflow triggers, auto-assignment rules) cannot be replicated automatically and is excluded from migration. We deliver a written template inventory with the recommended Zoho equivalent (Zoho Writer for document templates, Blueprint for project workflows) and the customer's admin rebuilds the logic post-migration.

OneSuite custom fields appear flattened on entities with their original slug as the property key (e.g., clientTier instead of a nested customFields object). We parse each slug, determine the target Zoho module, create the equivalent custom field in Zoho with the appropriate field type, and map the slug value during import. If a target custom field does not exist in Zoho at migration time, we create it first or flag it for pre-migration creation to prevent value drops.