Migrate from Spiro to Freshsales

Spiro Contacts map directly to Freshsales Contacts with standard fields (name, email, phone, title) preserved. Custom Contact fields migrate as Freshsales Contact custom fields, which must be pre-created in Admin Settings before migration. If the customer wants prospect records separated from customer records in Freshsales, we can split Spiro Contacts into Freshsales Leads (pre-conversion) and Contacts (post-conversion) using a custom field value as the segmentation key. Note that Freshsales Lead conversion requires explicit field mapping in Admin Settings; without it, custom field data on Leads is lost at conversion time.

Spiro Company records map to Freshsales Account. Address fields (street, city, state, postal code, country) merge into the Freshsales Account address block. If multiple Spiro Companies share the same legal entity name and website, we use the same dedupe logic Spiro applies: name plus website combination is unique. Account is created before Contact import so that the Account Lookup relationship is satisfied at Contact insert time.

Spiro Opportunities map to Freshsales Deals. The Spiro stage property maps to Freshsales Deal stage, and the pipeline assignment maps to a Freshsales pipeline that we configure before migration. Deal amount, close date, probability (if populated in Spiro), and owner migrate directly. Spiro stage names frequently differ from Freshsales default stage labels; we map these explicitly during scoping and flag any Spiro stages with no Freshsales equivalent.

Spiro custom fields on Companies, Contacts, and Opportunities must be extracted from Spiro's UI or confirmed with a CSM since there is no documented public endpoint for schema retrieval. We pre-create the equivalent custom fields in Freshsales Admin Settings before importing data. For Spiro Contacts that will become Freshsales Leads, we configure Lead field mapping to the corresponding Account, Contact, and Deal custom fields so that conversion preserves the data.

Spiro activity records (calls, emails, meetings, tasks) linked to Contacts and Companies migrate to Freshsales Sales Activities attached to the corresponding Contact and Account. Activity timestamps are preserved to maintain the chronological timeline. Note that Spiro email activity logged during periods of known email disconnection will not exist to migrate; we verify email sync status during scoping and advise customers to export any activity logs they want to preserve before cutover.

Spiro stores attachments as linked URLs rather than embedded blobs. We resolve each attachment URL during migration to confirm it is reachable. If the source Spiro workspace access is revoked post-migration, attachment links break. We recommend customers download critical files before the migration window closes and re-upload to Freshsales Document Storage or a linked cloud storage integration.

Spiro user records map to Freshsales User accounts. We resolve owners by email match. Any Spiro Owner without a matching Freshsales User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Active versus inactive status is preserved from Spiro where available.

Spiro pipeline structure is reconstructed in Freshsales by mapping Spiro stage values to Freshsales pipeline stage definitions. Freshsales supports multiple pipelines from the Growth plan onward. We configure the pipeline stages and any custom stage probabilities before Deal migration begins.