Migrate from SuperOffice CRM to Zoho CRM

SuperOffice Company records map directly to Zoho CRM Accounts. The Company record is imported first because Contact records carry a Company link via the associate table, and Zoho CRM enforces the Account lookup at import time. We use the SuperOffice company name as the Account Name dedupe key and preserve the SuperOffice country and business ID fields as custom Account fields.

SuperOffice Contacts with no associated Company or with a Person-type designation map to Zoho Lead. Contacts with an associated Company map to Zoho Contact tied to the corresponding Account. This differs from the pure Contact-only model in SuperOffice; we apply the split during the transform phase using the contact's company link and country properties, and we preserve the original SuperOffice contact ID in a custom field for reconciliation.

SuperOffice Sales map to Zoho CRM Deals. The sale stage maps to Zoho Deal Stage, and the pipeline assignment maps to a Zoho CRM pipeline that we configure before migration. Closed-Lost and Closed-Won reasons from SuperOffice custom properties become Zoho Loss Reason and Won Reason fields. The SuperOffice Sale type list table defines which Zoho pipeline and stages apply per record.

SuperOffice pipeline stages tied to SaleType link tables map to Zoho CRM pipeline stages. We export the stage order, name, and probability percentage from SuperOffice and configure matching Zoho pipeline stages before Deal import. Stage probability percentages round to Zoho's allowed integer format.

SuperOffice Projects with type and status link tables have no native equivalent in standard Zoho CRM tiers. We create a Zoho Custom Module named Projects with fields mapped from SuperOffice ProjectName, ProjType, ProjStatus, start date, and end date. Project-type-status links are stored as custom picklist fields in the custom module. If the customer also licenses Zoho Projects separately, we plan a Zoho-to-Zoho integration post-migration rather than migrating project members and time tracking through the CRM.

SuperOffice Quote → QuoteAlternative → line items structure maps to Zoho CRM Quotes. The primary QuoteAlternative becomes the Zoho Quote. Secondary QuoteAlternative versions are serialized as a JSON object in a custom Notes field on the Zoho Quote with a label Alternatives_Stored, so the information is preserved and visible to the admin during review. Line items map directly to Zoho Quote Line Items with product, quantity, and unit price.

SuperOffice Activities linked to Contact or Company records migrate to Zoho CRM Tasks. Calls map to Tasks with Task Type set to Call and Call Duration preserved in a custom field. Appointments migrate to Zoho Events with Start DateTime, End DateTime, and Location preserved. Activity associations to other objects (Sale, Project) are preserved by setting the WhatId equivalent on the Zoho Task or Event during import.

SuperOffice Selections (dynamic named lists of Contacts, Companies, or Sales) have no native equivalent in Zoho CRM. We export the Selection membership as tagged records, applying the Selection name as a Zoho Tag to each member record. The customer receives a written Selection inventory document listing each SuperOffice Selection, its record type, and its member count for manual recreation as Zoho Custom Views or CRM Workflows if dynamic filtering is required.

Documents stored in SuperOffice's document archive are exported as binary files with metadata (document name, type, date, linked record). We attach each file to the corresponding Zoho Account, Contact, Deal, or custom Projects record using Zoho's attachment API. Document-link relationships to multiple records are preserved by attaching to the primary parent and documenting secondary associations in the post-migration handoff report.

SuperOffice custom fields on Contacts, Companies, Sales, and Projects defined in the userDefined table map to Zoho CRM custom fields. We create the Zoho custom fields during schema setup, matching the SuperOffice field type (text, number, date, dropdown) to the nearest Zoho field type. Dropdown lists must be pre-created in Zoho with matching values before import to avoid rejection on insert.

SuperOffice Users with an email address map to Zoho CRM Users. We resolve owners by email match against the Zoho destination User table. Any SuperOffice Owner without a matching Zoho User goes to a reconciliation queue for the customer's admin to provision before record import resumes, since OwnerId is required on most Zoho CRM standard objects.

Tags applied across SuperOffice Contact, Company, Sale, and Project objects are exported and applied as Zoho CRM Tags to the corresponding records. Tags migrate as a flat string per record; if a tag is used for categorization rather than segmentation, the customer receives a tag audit document to determine whether Tags or Custom Views are the better Zoho equivalent.