Migrate from Spotler CRM to Twenty CRM

Spotler Contact records map directly to Twenty People. Email address serves as the dedupe key during import. We preserve the Spotler contact's linked Company by resolving the company_id foreign key to the matching Twenty Company record at import time. Custom fields on Contact migrate to custom fields on People after the Twenty Data Model is configured in Settings. Standard fields (name, email, phone, address) map 1:1; any free-form Spotler custom fields require explicit mapping against Twenty's field types (text, number, date, select).

Spotler Company records map to Twenty Company. The company domain becomes the Website field and acts as a secondary dedupe key. Company is created before any People import so that the People-to-Company relationship is satisfied at the moment of import. Industry, size, address, and custom properties migrate to matching Twenty Company fields after the Data Model is configured in Settings.

Spotler Opportunities map to Twenty Opportunities. Pipeline stage from Spotler maps to Twenty Opportunity stage values. Deal value, expected close date, and assigned Owner migrate directly. If Spotler uses multiple pipelines, we configure multiple Opportunity record types in Twenty to preserve the pipeline separation. Stage probability percentages transfer as custom fields if the customer requires them in reporting.

Spotler Tasks map to Twenty Task records. We preserve activity date, description, status, priority, and assignment by resolving the Spotler owner email to the matching Twenty user. Task records are linked to the parent People or Company via the relevant Twenty relationship field at import time.

Spotler call Activities map to Twenty Task records with the call type flagged. Duration, disposition, and any call notes migrate to custom Task fields. Activity timeline ordering is preserved by setting the Task due date to the original Spotler timestamp. Call recording URLs stored in Spotler migrate as custom text fields if the customer has access to the recordings.

Spotler meeting Activities map to Twenty Task records with the meeting type flagged. Start time, end time, location, and attendee information migrate to custom Task fields. Attendee emails are linked to matching Twenty People records where they exist. If the attendee is not a Contact in Spotler, the meeting is linked to the primary related record (People or Company).

Spotler Notes migrate to Twenty Note records linked via the Note's related People, Company, or Opportunity field. Note body migrates as rich text. Note authorship and timestamp are preserved from the Spotler record. Note attachments (document metadata) migrate as file references only; the actual files require separate file transfer and re-attachment in Twenty.

Spotler custom fields on Contacts, Companies, and Opportunities require pre-creation in Twenty Settings Data Model before any data import. Dropdown list values from Spotler must be mapped explicitly to Twenty select options because Spotler stores them as separate reference IDs. We export the Spotler field definition table alongside the data export and recreate all custom fields in Twenty during the setup phase. Fields that exist in Spotler but have no matching Twenty field type (e.g., complex Spotler formula fields) are flagged for manual review and either recreated as custom fields or dropped with a written explanation.

Spotler Quotations (Professional and Enterprise only) carry line items, pricing, and status. Twenty does not have a native quotation object. We configure a custom object (e.g., Quotation__c) in Twenty's Data Model before migration, mapping quotation header fields (quote number, date, status, total value) and creating a linked line item custom object with product, quantity, and price fields. If the customer uses Spotler quotation PDFs, we deliver those as file attachments to the custom object records after migration.

Spotler Cases (Professional and Enterprise) with SLA assignment, priority, and status do not have a native Twenty equivalent. We configure a custom object (e.g., Case__c) in Twenty with fields for case number, subject, description, priority, status, and assignee (linked to Twenty user). Case-to-People and Case-to-Company relationships are preserved as lookup fields. SLA fields migrate as custom date and text fields. We document the original SLA configuration for the customer's admin to rebuild the SLA logic manually.