Migrate from Salesmate to Twenty CRM

Salesmate Contact records map to Twenty Person records. The mapping preserves name fields (first_name, last_name), email address, phone number, and any custom fields as Twenty Person custom fields. We set the Person's displayName to the Contact's full name and preserve the Salesmate contact_id in a custom field sm_contact_id__c for reconciliation. If the Contact is linked to a Salesmate Company, we create or match the Company in Twenty first and link the Person to it via the Company foreign key.

Salesmate Company records map directly to Twenty Company records. The domain from Salesmate's website field becomes the Company domain in Twenty. Companies are imported first to satisfy the Person-Company lookup before Person records are inserted. Any custom fields on the Salesmate Company (industry, employee count, revenue tier) map to Twenty Company custom fields created via the /metadata API.

Salesmate Deals map to Twenty Opportunities. The dealstage maps to Twenty Opportunity stage values, which we configure during workspace setup to match the customer's pipeline stages. Closed-won and closed-lost reasons from Salesmate custom properties migrate to Twenty Opportunity custom fields. The deal amount, expected close date, and owner assignment migrate directly with OwnerId resolved via email match to Twenty User records.

Salesmate pipelines become Twenty Opportunity stage configurations within each Workspace. We extract all Salesmate pipeline names, map each pipeline stage to a corresponding Twenty stage value, and configure the stage probability percentages to match the original Salesmate percentages. For multi-pipeline setups, we configure separate Workspaces in Twenty if the customer's business logic warrants it, or separate Record Type fields if all pipelines share a single Workspace.

Salesmate Tasks map directly to Twenty Tasks. Status, Priority, due date, and assignment migrate. The task association (linked to Contact, Company, or Deal) is preserved as a custom field linking the Task to the corresponding Person, Company, or Opportunity in Twenty. Open and completed task status maps directly to Twenty task status values.

Salesmate email history stored under Module ID 3 migrates to Twenty as Task records with an email subtype indicator. Full email body content may require a separate export path from Salesmate depending on the email's storage configuration. We preserve the email thread association as a custom field. Email attachments migrate as file links if they are accessible via the Salesmate API.

Salesmate Products (Module ID 6) migrate to Twenty as a custom object or as line items on the Opportunity object depending on the customer's usage pattern. If the customer uses Products for a price book, we create a custom object with product name, SKU, and pricing fields. Price book associations require configuration in Twenty's Opportunity data model.

Salesmate custom fields on Contacts, Companies, Deals, Tasks, and Products are recreated in Twenty via the /metadata GraphQL API before any data import begins. We create the field definitions first (field name, type, required/optional), then import values during the record migration phase. Picklist values in Salesmate map to Twenty select or multi-select field options. Number, date, and text types map directly.

If Salesmate has any custom objects (via their Customize > Create Form interface), we create matching custom objects in Twenty using the metadata API. This involves creating the DataSource, Object, and Field metadata records, which triggers Twenty's GraphQL schema computation. Custom object records are imported last, after all parent standard objects are in place, because custom objects often have lookup relationships to Person, Company, or Opportunity.

Salesmate user records map to Twenty User records by email address. Owner assignments on Deals and Tasks are resolved by matching the Salesmate owner email to the Twenty User email. Any Salesmate user without a matching Twenty User is held in a reconciliation queue for the customer's admin to provision before record import resumes.

Salesmate Team Inbox conversations do not have a native equivalent in Twenty's activity model. We export the conversation thread metadata (sender, recipient, timestamp, message body, thread ID) and preserve it as a custom multi-line text field on the related Person or Company record. This preserves the conversation history without forcing it into Twenty's Task or Note model where it would lose threading context.

File attachments associated with Contacts, Deals, and Companies are exported from Salesmate via the API and re-uploaded to Twenty. Storage limits in Salesmate vary by tier (1 GB Basic, 5 GB Pro, 10 GB Business, 20 GB Enterprise). We flag files approaching these limits during scoping and advise on a cleanup or selective migration strategy before migration day.