Migrate from Spin CRM to Twenty CRM

Spin CRM Companies map directly to Twenty Companies. We export via the settings-based CSV, capture company name, address, industry, and any custom properties, then import into Twenty as Company records. Spin CRM's Companies serve as the primary relationship anchor for People records, so we export and import Companies first to establish the lookup keys before any People import. Domain-based dedupe is used where company website is populated.

Spin CRM People records (the platform's unified contact and lead entry object) map to Twenty's People object. We resolve the company association by matching Spin CRM's company link against the imported Company record names. Email address is the primary dedupe key. Any Spin CRM Person records without an email are flagged for manual review before import.

Spin CRM Deals map to Twenty Opportunities. The Spin CRM deal stage maps to a Twenty pipeline stage value that we configure before migration. Deal value, expected close date, owner, and associated company and person links transfer directly. Closed-Lost and Closed-Won statuses from Spin CRM map to matching Twenty stage values.

Spin CRM's customizable pipeline stages are captured during scoping and replicated in Twenty's pipeline configuration. Each Spin CRM stage becomes a named stage in a Twenty pipeline with the same order and any available probability or description values. Stages are configured before Opportunities are imported so that the stage field is validated during data load.

Spin CRM's separate Lead object (accessible via the Lead window settings export) maps to Twenty People. Spin CRM uses Leads and People/Contacts as distinct entry points; Twenty consolidates both into the People object. We import both Spin CRM object types as Twenty People records and flag any duplicate email addresses to prevent record collision during load.

Spin CRM task and reminder records map to Twenty Tasks. Task title, due date, status, assigned owner, and linked company or person transfer as-is. We resolve Spin CRM owner email references against the Twenty User records provisioned before import. Tasks without a resolvable owner are imported with no assignment and flagged for the admin to assign post-import.

Spin CRM notes and internal comments map to Twenty Notes attached to the relevant People, Company, or Opportunity record. Note body text, author, and timestamp transfer directly. Notes without a clear parent record are attached to the most recently accessed related People or Company record based on Spin CRM's activity ordering.

Spin CRM calendar events and meeting records map to Twenty Tasks with a type indicator distinguishing them from standard to-do tasks. Meeting title, date, and attendees transfer. If the Spin CRM export exposes attendee information, we store it in a custom field on the Twenty Task record; otherwise, the calendar nature of the activity is indicated in the task title for the admin to reconcile in Twenty's calendar view post-migration.

Spin CRM owner references on Companies, People, Deals, and Activities map to Twenty User records. We resolve by email match where a Twenty User exists with the same email address. Owners without a matching Twenty User enter a reconciliation queue, and the customer's admin provisions the User before the relevant records are imported. Owner resolution is validated before each object import phase begins.

Spin CRM custom fields on People (Contacts and Leads) require pre-creation in Twenty's Settings Data Model before any People import. We audit the Spin CRM CSV column headers against the customer's reported custom field list during scoping, request a re-export if columns are missing, create each custom field in Twenty with the appropriate type (text, number, date, select), and then import the values during the standard People load phase.

Spin CRM custom fields on Companies require pre-creation in Twenty before the Company import. Custom field values stored as picklist options in Spin CRM map to Twenty select field options. Boolean fields map to Twenty checkbox fields. Any custom field not visible in the Spin CRM CSV export is flagged and the customer is consulted before the import proceeds.

Spin CRM custom fields on Deals are captured from the Deal CSV export and pre-created in Twenty as custom fields on the Opportunity object. Deal-specific custom properties such as deal source, contract type, or renewal date map to equivalently named or typed Twenty custom fields. We validate that all Spin CRM custom Deal fields appear in the exported CSV before schema creation begins.

Spin CRM supports custom field creation but custom object availability is limited and not prominently documented. If the customer has custom object data in Spin CRM (tracked via separate linked records or export tabs), we create matching Custom Objects in Twenty via the Settings Data Model, define the custom fields and any lookup relationships to standard objects, and import the records via the Twenty REST or GraphQL API. This phase runs last in the migration sequence to allow all standard object dependencies to resolve first.

Spin CRM document storage is not migratable via the documented CSV export mechanism. File blobs and attachments stored within Spin CRM cannot be extracted without a confirmed export path from the Spin CRM interface. We flag document storage access with the customer during scoping. If a supported export method is identified, we include document migration as an optional add-on scope. By default, document migration is excluded from the standard migration package.