Migrate from Optimiser CRM to Twenty CRM

Optimiser CRM Contact records map to Twenty CRM Person. Standard fields (name, email, phone, address) map to their Twenty equivalents; Optimiser's custom contact properties map to Twenty custom fields that we pre-create during schema design. Email address serves as the dedupe key during import. Owner assignment maps from Optimiser's contact owner to the matching Twenty User by email address.

Optimiser Company records map to Twenty Organization. Company name becomes the Organization name; external ID or domain maps to the Website field where available. Organization is imported before Person records so that the Person-Organization lookup relationship is satisfied at the moment of Person insert, preventing orphaned Person records.

Optimiser Deal records map to Twenty Opportunity. Deal stage maps to Twenty pipeline stage via a stage-mapping table defined during scoping; deal value and expected close date map directly. Optimiser's custom deal properties map to Twenty custom Opportunity fields. Owner assignment resolves via email match to Twenty User.

Optimiser Lead records map to Twenty Opportunity when the migration scope calls for a unified pipeline. Lead status, lead source, and any scoring values migrate as custom Opportunity fields (lead_status__c, lead_source__c). Note that Twenty's GitHub roadmap (issue #10422) identifies a native lead-to-custom-object convert action as a planned feature; we currently handle the lead record as a static Opportunity with a custom type field distinguishing it from converted deal Opportunities.

Optimiser Activities (calls, emails, meetings, notes) logged against Contacts, Companies, or Deals export as activity records. We import these as Twenty Activities in chronological order using the original timestamp for ordering, and associate them to the correct parent record (Person or Organization) via lookup resolution. Activity type determines which Twenty Activity sub-fields populate (call duration, email subject, meeting location, note body).

Optimiser document attachments referenced by URL or stored in the platform's file store are downloaded locally during the migration window, re-uploaded to Twenty, and linked to the correct parent Person or Organization record. If attachments are embedded inside Optimiser's note content rather than stored as separate files, the note body migrates as-is with the attachment reference preserved as a URL string pending the customer's file migration decision.

Optimiser User records (name, email, role) map to Twenty User by email address. Owner assignment on Deals, Contacts, and Activities resolves via the User mapping. Any Optimiser user without a matching Twenty User goes to a reconciliation queue for the customer's admin to provision the account before record import resumes.

Optimiser's configurable pipeline stages per deal type map to Twenty's pipeline stage configuration. We extract the full stage list from the source during scoping, map each stage name to a corresponding Twenty stage, and configure the pipeline in Twenty before Deal import begins. Stages with zero records are excluded from the stage list to avoid creating inactive pipeline columns in Twenty.

Tags applied to Optimiser Contacts or Deals export as label values. We migrate tags as-is and create matching tag sets in Twenty where the platform supports them. Tags with no records are excluded from the migration to avoid creating empty label sets in the destination.

Optimiser custom fields on Contacts, Companies, and Deals are enumerated per-instance during scoping. We create matching custom fields in Twenty on the equivalent object (Person, Organization, Opportunity), apply the appropriate field type (text, number, date, picklist), and map values during the respective object import phase. Fields with zero data across all records are excluded from the migration to avoid creating dead columns in Twenty.

Optimiser's custom properties on standard objects are treated as Custom Fields. If the customer's Optimiser instance uses a separate custom object module, that maps to a Twenty Custom Object of the matching name. We pre-create the destination custom object schema in Twenty, including all custom properties, lookup relationships, and any type constraints, before importing any data. Custom object import runs last because it may have lookups to standard objects (Person, Organization) that must already exist.

Optimiser Project module records migrate to a Twenty Custom Object named Project when the customer includes Projects in migration scope. Project-Company and Project-Contact associations migrate as lookup relationships in Twenty. Most CRM-to-CRM migrations treat Projects as a secondary pass after the primary Contact-Company-Deal migration; we scope it explicitly during discovery to avoid unplanned complexity.