Migrate from Spiro to Twenty CRM

Spiro Companies map to Twenty's Organization object. The Spiro company name, address fields (street, city, state, postal code, country), phone, website domain, and industry values migrate directly. We normalize address components if the source Spiro export combines fields. Any Spiro Company records sharing the same legal entity name are flagged as potential duplicates for customer review before final import. Spiro's custom Company fields migrate as Organization custom fields after the customer provisions them in Twenty's workspace settings.

Spiro Contacts map to Twenty's Person object. Name, email, phone, job title, and LinkedIn URL fields migrate directly. The Spiro Contact's linked Company (via Company lookup) migrates as the Person's organization relationship pointing to the target Organization record. Spiro's custom Contact fields migrate as Person custom fields. The email address serves as the primary dedupe key during import.

Spiro Opportunities map to Twenty's Opportunity object with the pipeline and stage reconstructed in Twenty before import. The Opportunity name, amount (value), expected close date, and notes migrate directly. Stage mapping is explicit: each Spiro stage value becomes a custom stage value in Twenty's Opportunity pipeline that we configure during the schema preparation phase. Closed-Lost and Closed-Won statuses from Spiro map to the corresponding stage values in Twenty.

Spiro's single pipeline with stage values migrates to Twenty's customizable pipeline configuration. We create a Pipeline in Twenty's workspace settings and define stage values that correspond to Spiro's stage labels. Stage order and probability percentages (if present in Spiro) are preserved. If Spiro has multiple pipeline views (for different product lines or team structures), we replicate these as separate Pipelines in Twenty.

Spiro does not expose custom field definitions via a self-serve API. We coordinate with Spiro's Customer Success Manager to extract the full custom field inventory, including field name, type (text, number, date, picklist, checkbox), and object assignment. We then pre-create each custom field in Twenty's workspace (Organizations, People, Opportunities) before importing any data. Field type mapping from Spiro to Twenty is straightforward for text, number, date, and checkbox types; picklist values migrate as-is and require manual recreation in Twenty's picklist settings.

Spiro call records migrate as TimelineEvent entries in Twenty. The call title, date, duration (minutes), outcome, and notes migrate as event fields. The linked Contact and Company are resolved to the target Person and Organization records respectively. If Twenty's standard timeline does not support call duration fields natively, we create a custom TimelineEvent type with duration and outcome fields. Owner assignment migrates by matching the Spiro user's email to the target Twenty workspace member.

Spiro email engagement records migrate as TimelineEvent entries in Twenty. The email subject, body (plain text), sent or received direction, and timestamp migrate. Note: if Spiro's email integration was disconnected during the source period, some emails may not have been logged in Spiro at all; we cannot backfill data that was never recorded. We verify email activity records exist in the Spiro export before importing and flag gaps to the customer.

Spiro meeting records migrate as TimelineEvent entries in Twenty with meeting title, date and time, duration, location, and attendees. Attendee emails are resolved to Person records where matches exist in the migrated data; unresolved attendee emails are noted as external participants. The meeting organizer maps to the Twenty workspace member who owns the record.

Spiro tasks migrate as Twenty Tasks. Task title, description, due date, completion status, priority, and assignee (owner) migrate directly. The linked Contact or Company resolves to the target Person or Organization in Twenty. Task status (completed, in progress, not started) maps to Twenty's task status values.

Spiro user records map to Twenty workspace members. We resolve by email address. Any Spiro user without a matching Twenty workspace member is held in a reconciliation queue; the customer provisions the user in Twenty before the import resumes. Owner assignment on Opportunities, Contacts, and Activities resolves at migration time using the email match lookup.

Spiro stores file attachments as URL references rather than embedded blobs. During migration, we verify each attachment URL is reachable at the time of export, download the file content, and re-upload it to Twenty's attachment storage if available. If the source Spiro workspace access is revoked post-migration, the original URL references become orphaned. We recommend downloading critical attachments before the migration window closes and flag any URLs that fail reachability checks during the export phase.