Migrate from Exsalerate to Twenty CRM

Exsalerate Accounts map directly to Twenty CRM Company records. The Account name becomes the Company name, and contact details, owner assignment, and custom properties map field-to-field. Company is the first object imported because it satisfies the lookup dependency for Contacts, Opportunities, and activity records. We use the Company domain or name as the dedupe key during import to prevent duplicate records.

Exsalerate Contacts map to Twenty CRM Person records. The Account-Contact relationship is preserved by linking each Person to the migrated Company record via a lookup field. We run duplicate detection across the contact set before import using email as the primary key. Any contacts without email addresses are flagged for the customer's admin to resolve manually before the migration phase begins.

Exsalerate Opportunities map directly to Twenty CRM Opportunity records. The Opportunity name, value (amount), expected close date, owner, and associated Pipeline Stage migrate field-to-field. The Exsalerate Pipeline Stage becomes the Twenty CRM Stage value. Closed-won and closed-lost reasons from Exsalerate custom properties migrate as text fields on the Opportunity. WorkflowMax quote cross-references embedded as custom attributes on Exsalerate Opportunities are stored in a custom field (workflowmax_quote_ref__c) on the Twenty CRM Opportunity and flagged for manual relinking if the customer needs to restore the project management connection.

Exsalerate Pipelines are top-level named containers for sales activity. Twenty CRM does not have a separate Pipeline object; instead, pipeline groupings are achieved through stage labels and optional workspace view filters. We map each Exsalerate Pipeline name to a set of Opportunity Stage values prefixed with the pipeline name (for example, 'Enterprise: Proposal Sent') to preserve the pipeline context. The customer configures workspace views in Twenty CRM to filter by pipeline prefix after migration.

Exsalerate Pipeline Stages (ordered labels such as Qualified, Proposal Sent, Negotiation) map to Twenty CRM Stage picklist values. Stage order and probability percentages are preserved. The colour metadata attached to stages in Exsalerate (used for visual tile encoding) is stored in a custom field on the Opportunity record for reference. Stage-level automation triggers do not migrate — we document each Exsalerate stage trigger in the automation inventory deliverable.

Exsalerate's colour-coded activity tiles (the to-do model) map to Twenty CRM Task records. Due date, status, owner, and description migrate field-to-field. The tile colour value is stored in a custom Task field (activity_tile_colour__c) to preserve the urgency and context encoding that Exsalerate users relied on. This custom field is created during schema preparation before the task import phase begins.

Exsalerate email history associated to Accounts and Contacts migrates to Twenty CRM Timeline Entries with subject, body (plain text), timestamp, sender, and recipients preserved. Attachments are handled as file migrations outside the record migration scope. Email threading relationships from Exsalerate are not preserved as Twenty CRM does not have a native email threading model; however, the chronological sequence of emails per contact is maintained through the ActivityDate timestamp.

Custom fields on Exsalerate Accounts, Contacts, and Opportunities are migrated with field-type awareness. Picklist values are normalised to the destination picklist format. Date formats are converted to ISO 8601. Numeric precision is preserved. Any Exsalerate custom field that does not have a direct Twenty CRM equivalent is created as a custom field in the Twenty CRM workspace during schema preparation. Fields with no equivalent object in Twenty CRM (for example, Exsalerate-specific accounting references) are stored as text custom fields and flagged for review.

Exsalerate user accounts map to Twenty CRM workspace members. We create a user mapping table during scoping using email as the matching key. Any Exsalerate Owner without a matching Twenty CRM workspace member is held in a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Exsalerate users are assigned to a placeholder owner record in Twenty CRM with a custom field indicating their inactive status.

Where Exsalerate Opportunities were created from WorkflowMax quotes, a cross-reference attribute links the Opportunity to the originating WorkflowMax job. This linkage is not a standard CRM field — it is a custom attribute that we detect during scoping. We store the WorkflowMax job reference identifier in a custom text field (workflowmax_job_ref__c) on the migrated Twenty CRM Opportunity. The customer rebuilds the WorkflowMax connection manually after migration using the stored reference, or excludes this field if the WorkflowMax relationship is being discontinued.