Migrate from Simple Sales Tracking to Twenty CRM

Simple Sales Tracking Lead records map to Twenty CRM Person records. We apply a pre-split rule based on the Lead status property: Leads with a status indicating early-stage qualification map to Person records with a custom stage field capturing the original status. Lead source fields migrate to a custom source field on Person. Custom Lead-level Sales Record fields migrate as custom Person fields after schema inspection from UI metadata.

Opportunities map directly to Twenty Opportunities. The Simple Sales Tracking deal amount, expected close date, and owner assignment transfer to the corresponding Twenty Opportunity fields. Pipeline stage names from Simple Sales Tracking are mapped to Twenty stage values that we configure before migration; the stage sequence order is preserved as the Stage display order in Twenty.

Simple Sales Tracking Accounts map to Twenty CRM Companies. Account names, addresses, industry tags, and associated Contact links transfer to the Company object. The Company record is created before any Person import so that the Person-to-Company relationship is satisfied at the moment of Person insert. Account domain or website fields map to the Company URL field.

Contacts map to Twenty CRM Person records using the same mapping as Leads. Where a Contact is linked to an Account, the Person-Company relationship is resolved during import by matching the associated Account name to the pre-created Company record. Email, phone, and address fields transfer to Person's standard contact fields; custom Contact-level fields migrate as custom Person fields.

Notes are free-text records attached to Contacts, Opportunities, or Accounts in Simple Sales Tracking. We preserve note content and creation timestamp. Note formatting and embedded file links do not carry over; if a note contains an attachment reference, we export the linked file separately and note the association for re-attachment in Twenty.

Tasks migrate with due date, assignee, and completion status preserved. Open and completed tasks transfer. Simple Sales Tracking task histories do not include a full activity log of status changes, so we migrate the final state rather than an audit trail. Task assignment resolves by matching the Simple Sales Tracking owner email to a Twenty User.

Appointments include date, time, duration, title, and linked Contact. We migrate appointment records as Task records in Twenty with the original timestamp preserved and a custom field capturing the duration. The linked Contact resolves to the corresponding Person record via email match. Calendar re-booking in Twenty is a manual step for the end user post-migration.

Files attached to Contacts, Opportunities, and Notes are exported as individual downloads from Simple Sales Tracking's 1 GB storage pool. We re-attach each file to the corresponding migrated record in Twenty using the Person, Opportunity, or Note API. File metadata (original filename, upload date, file size) is preserved. The 1 GB total storage ceiling means we flag any account approaching capacity during discovery so the customer can archive old files before migration.

Custom fields on Sales Records require UI-metadata extraction because Simple Sales Tracking does not expose a schema endpoint. We ask the customer for a screen capture of their custom field configuration page during discovery and cross-reference it against a sample API response to build the complete field map. Custom fields are created in Twenty as custom Person or custom Opportunity fields before migration, matching the source field type (text, number, date, picklist).

Simple Sales Tracking allows custom named stages with drag-and-drop ordering per pipeline. We capture the full stage sequence during discovery, then configure Twenty's Opportunity stage values to match the source stage names and order before any Opportunity records are imported. Any stage with a probability percentage in Simple Sales Tracking is set as the Stage probability in Twenty.

Simple Sales Tracking user records and role assignments export as a user list. We map role names to the closest applicable Twenty workspace role. Active users receive Twenty User accounts; inactive or archived users are flagged for the customer's admin to handle post-migration. Owner assignment on Opportunities and Tasks resolves via email match against the migrated User list.

Commission percentage or amount fields attached to Opportunities in Simple Sales Tracking are treated as custom Opportunity fields. We create a custom commission field in Twenty's Opportunity object before import and transfer the values directly. If the destination field does not exist, we export the data as a CSV alongside the migration for manual entry or custom field creation post-migration.

Lead sources are a configurable reference taxonomy in Simple Sales Tracking. We migrate source labels as options in a custom picklist or text field on the Person object in Twenty. If Twenty's standard source field exists in the target workspace, we map labels directly; otherwise we use a custom field and note the available values for the admin to configure.

The Activity Feed is a real-time event stream generated within Simple Sales Tracking and is not exposed as a queryable API object. Historical feed entries cannot be retrieved via the API. We explain this limitation during discovery and recommend the customer export any critical feed entries as manual Notes before the migration date. This is not a data loss gap but a product limitation of the source platform.