Migrate from Spiro to Zoho CRM

Spiro Company records map to Zoho CRM Accounts. We normalize company name and merge duplicate Spiro Company records that share the same legal entity before inserting. The Zoho Account Name field is the primary insert key. Address fields (street, city, state, zip, country) map directly; any Spiro custom fields on Company are pre-created in Zoho as custom Account fields before import begins.

Spiro Contacts migrate to Zoho Contacts with standard fields (full name, email, phone, title) mapping directly to Zoho Contact fields. We resolve the parent Account reference by matching Spiro Company name to Zoho Account Name at migration time. Custom Contact fields from Spiro are pre-created in Zoho Contacts module before import. If a Spiro Contact has no associated Company, we create a standalone Zoho Contact and flag it for the customer's admin to attach to an Account.

Spiro Opportunities map to Zoho CRM Deals. The Spiro Opportunity stage (e.g., Prospecting, Qualification, Demo, Proposal, Negotiation, Closed Won, Closed Lost) maps to a Zoho Deal Stage that we configure in Zoho before migration. Spiro deal amount maps to Deal Amount, close date maps to Closing Date, and owner email matches to the Zoho User record by email. We flag any Spiro Opportunities with unrecognized stage values during scoping for manual mapping.

Spiro custom fields on Companies, Contacts, and Opportunities require pre-creation in Zoho before any data import. We extract the full field inventory from Spiro's UI with customer confirmation, then create the equivalent custom fields in Zoho using the Setup menu or API. Zoho Free edition does not support custom fields; we confirm the destination Zoho edition (Standard, Professional, Enterprise, Ultimate) during scoping and factor any edition upgrade into the migration scope. Zoho also limits each module to 300 fields with a maximum of 5 Lookup fields per module; we flag conflicts during mapping.

Spiro activity records (calls, emails, meetings) linked to Contacts and Companies migrate to Zoho Tasks and Events. Call activities map to Zoho Tasks with Task Type set to Call; emails map to Tasks with type Email; meetings map to Zoho Events with start time, end time, and location preserved. Owner assignment migrates by matching Spiro owner email to Zoho User. If Spiro's email integration had disconnected silently during the source period, some activity records will not exist in Spiro; we verify email sync status during scoping and export any activity logs the customer wants to preserve before the cutover window.

Spiro user records map to Zoho CRM Users. We match by email address. Any Spiro Owner with no matching Zoho User record is placed in a reconciliation queue for the customer's admin to provision the Zoho user before record import resumes. Inactive Spiro users are migrated as inactive Zoho users so that historical activity attribution is preserved without granting active login access.

Spiro uses Opportunities to represent pipeline entries. We reconstruct pipeline structure by mapping Spiro stage values to Zoho CRM pipeline stage definitions. Zoho supports multiple pipelines with custom stage layouts; we configure the target pipeline in Zoho during the schema setup phase and map Spiro stage names to the corresponding Zoho stage during data transformation.

Spiro stores attachments as linked file URLs. We resolve each attachment URL during migration, download the file if reachable, and upload it to Zoho CRM's WorkDrive-based document storage. The migrated attachment is then linked to the corresponding Zoho Account, Contact, or Deal record. If the Spiro workspace access is revoked before migration completes, attachment URLs become orphaned; we flag this risk during discovery and recommend downloading critical files before the migration window. Zoho's 5 GB per-file import limit and 25 GB total import cap apply to bulk attachment migration.

Spiro notes linked to Companies, Contacts, or Opportunities migrate to Zoho Notes. We preserve note content, creation timestamp, and owner attribution. Notes without a resolvable parent record are attached to the nearest related object (Contact or Account) and flagged for the customer's admin to review and re-associate.

Spiro's Data Collector configuration (Dropbox folder path, import schedule, CSM-enabled settings) is a Spiro-specific feature with no equivalent in Zoho CRM. We document the Data Collector settings as part of the migration inventory so the customer's admin understands what automated import workflows existed in Spiro and can reconfigure equivalent data feeds in Zoho using Zoho Flow, Zoho Analytics, or a scheduled CSV import.