Migrate from Spiro to Pipedrive

Spiro Companies map to Pipedrive Organizations. We handle name normalization, deduplication (merging records representing the same legal entity), and address field consolidation during the extract phase. The Organization record must exist before any linked People or Deals import, so we migrate Organizations first. Address, domain, and industry fields map to Pipedrive's standard Organization fields. Any custom fields on Spiro Companies are pre-created in Pipedrive before Organization import begins.

Spiro Contacts map directly to Pipedrive People. Standard fields (name, email, phone, title) migrate cleanly. We resolve the Organization link by matching the Contact's associated Company against the migrated Organization records using the organization name or domain as the dedupe key. If a Contact has no associated Company in Spiro, we flag it for the customer's admin to either create a placeholder Organization or link it manually post-migration. Custom Contact fields are pre-created in Pipedrive as custom fields on People before import.

Spiro Opportunities map to Pipedrive Deals. Stage name, value, and close date migrate directly. Pipedrive requires every Deal to link to an Organization; we resolve this by looking up the Opportunity's associated Company in the migrated Organization table and setting the Organization ID. Deals with no Company association in Spiro require a reconciliation decision (create placeholder Organization or exclude) before migration begins. We preserve the Opportunity's Spiro-specific fields (if any custom fields exist on Opportunities) as custom Deal fields.

Spiro Opportunity stages map to Pipedrive Pipeline stages. We configure Pipedrive Pipelines and Stages during the schema phase before any Deal records import. Stage names from Spiro are used as stage labels in Pipedrive, and probability percentages are mapped to Pipedrive's stage probability field. If Spiro uses multiple pipelines, we create a corresponding number of Pipedrive Pipelines with separate stage sequences. Pipedrive's visual Kanban pipeline view is available from the Lite tier.

Spiro custom fields on Companies are extracted with CSM assistance (Spiro does not expose the custom field schema via self-service API) and pre-created in Pipedrive as Organization custom fields before Organization import. Field type mapping follows Pipedrive's supported types: text, number, date, checkbox, dropdown, and currency are all supported. Picklist values are preserved as Pipedrive dropdown options.

Spiro custom fields on Contacts map to Pipedrive People custom fields. We extract the field definitions from Spiro's UI or via CSM export and recreate them in Pipedrive before People import. Multi-select checkbox fields in Spiro map to Pipedrive's multi-select picklist. Fields are created with the same label and API-safe name format that Pipedrive requires.

Spiro custom fields on Opportunities migrate to Pipedrive Deals custom fields. Pipedrive supports custom fields on Deals from the Lite tier onward. We create all Deal custom fields before Deal import begins so that field mapping is available during the CSV or API load phase. Custom field values are included in the Deal import payload.

Spiro call activities map to Pipedrive Activities with type set to Call. Call duration, disposition, and outcome from Spiro migrate to corresponding custom Activity fields in Pipedrive. Owner assignment resolves via email match to Pipedrive Users. Activities are linked to the relevant Person or Deal record using Pipedrive's sub-resources API after the parent record is confirmed to exist in the destination.

Spiro email engagement records map to Pipedrive Activities with type set to Email. Email subject and body content migrate to Pipedrive's Activity fields. Note: any emails not logged during Spiro's email disconnection windows are not recoverable; we flag this during discovery and recommend the customer verify email sync status and export activity logs before the migration window. We cannot backfill activity data that was never recorded in Spiro.

Spiro meeting activities map to Pipedrive Activities with type set to Meeting. Meeting title, date, duration, and location migrate. Attendees are mapped to linked Person records where the email matches an existing Pipedrive Person. Recurring meetings are imported as individual Activity records per occurrence.

Spiro notes (internal freeform annotations on Companies, Contacts, or Opportunities) map to Pipedrive Notes. Notes are linked to the parent record (Organization, Person, or Deal) via Pipedrive's Note API. Timestamp and author ownership are preserved. Notes are imported after parent records exist in the destination.

Spiro Users map to Pipedrive Users. We match by email address as the dedupe key. Pipedrive requires users to exist (or be provisioned) before any records can be assigned to them. We run a user reconciliation step: all Spiro Owners are listed, matched against Pipedrive's existing User table, and any unmatched Owners are flagged for the customer's admin to provision before Deal and Activity import begins. Inactive or departed Spiro users are mapped to inactive Pipedrive users to preserve activity attribution.