Migrate from Snapforce CRM to Twenty CRM

Snapforce Account records map directly to Twenty Company objects. The account name maps to Twenty's name field, domain to the website field, and billing address fields map to the standard address compound field. We use company name and domain as the dedupe key during import to prevent silent duplication. Snapforce's custom account fields are captured by label during discovery and recreated as custom fields in Twenty before the company import phase runs.

Snapforce Contact records map to Twenty Contact with name, email, phone, and address preserved. The contact-account linkage (which Account the Contact belongs to) maps to Twenty's companyId foreign key. We resolve the companyId reference before inserting Contacts so that the lookup relationship is satisfied at import time. Email, phone, and custom fields transfer directly; any HubSpot-style email tracking embedded in Snapforce's mailbox logs does not migrate as those are session-based, not record-based.

Snapforce Lead records map to Twenty's Person object when the Lead has not been converted to an Account/Contact pair. In Twenty's model, a Person record can exist independently or be linked to a Company as a workspace member. We preserve the original lead status from Snapforce (New, Contacted, Qualified, Unqualified) in a custom field original_lead_status__c for reporting continuity.

Snapforce converts Leads into an Account/Contact pair. At migration time we detect converted Leads by checking for a corresponding Account record with the same name as the Lead and a Contact with the same email. We map these to Twenty Contact linked to the Company record and flag them as converted by setting a custom field conversion_source__c.

Snapforce Opportunity maps directly to Twenty Opportunity. Pipeline stage names, probability percentages, close dates, and amount migrate as Opportunity fields. We create a Twenty Pipeline record to match the Snapforce pipeline structure before Opportunities import so that the pipelineId foreign key is satisfied. Custom opportunity fields migrate by label match.

Snapforce Tasks map to Twenty Task with title, body, due date, status, and priority preserved. Owner assignment migrates by email match to the Twenty user record. Tasks linked to Contacts, Leads, or Opportunities in Snapforce carry their WhatId and WhoId equivalents as custom relation fields in Twenty.

Snapforce VoIP call metadata (call duration, timestamp, disposition, direction) is written to the Contact record and exported as part of the Contact module CSV. We extract these as standalone Task records in Twenty with TaskType = Call, CallDurationInSeconds set from the duration field, and CallDirection from the direction field. Call recording audio files are handled separately as file attachments.

Snapforce voicemails are audio files stored per-user mailbox with a 500-voicemail cap per mailbox. They are not exportable via CSV. We extract voicemail audio files from the Snapforce storage layer, identify the associated Contact by filename pattern or user mailbox owner, and re-associate the audio file as an Attachment on the corresponding Twenty Contact record. This step is manual per-file and must be scoped explicitly during discovery because file extraction and re-upload are not API-driven.

Snapforce Campaigns are a paid add-on at $8/user/month and contain target audiences linked to Leads and Contacts. Twenty does not have a native Campaign object in its base schema. We map Campaign membership to a custom Target object in Twenty (created as part of the migration schema) or to Note records with a tag linking them to the relevant Person or Contact. The customer's admin selects the preferred representation during scoping.

Snapforce Documents are files uploaded to Accounts, Contacts, or Opportunities, with optional Google Drive sync. We export documents to local storage, preserve the parent record linkage (accountId, contactId, or opportunityId), and re-upload them as Attachments in Twenty linked to the corresponding Company, Contact, or Opportunity record.

Snapforce User records carry role assignments and data ownership. We export the full user list and map each Snapforce user to a Twenty WorkspaceMember by email. Any records owned by a Snapforce user with no matching Twenty user go to an orphan queue for the customer's admin to provision before the final import phase runs. Role and permission mapping is documented for the admin to reassign post-migration.

Snapforce custom fields exist per-organization and use internal IDs that cannot be referenced in Twenty. We capture the full custom field schema for each Snapforce module during discovery — field label, data type, and any picklist values — and recreate the field definitions in Twenty by label match before importing any data. Workflow rules referencing these custom fields are documented separately for the admin to rebuild in Twenty's extension model.