Migrate from FastTrack to Twenty CRM

FastTrack's person records map directly to Twenty's People object. Every field on the person (name, email, phone, job title, address) maps to the matching Twenty field. The source system ID is preserved as a custom field for traceability. Owner assignment resolves by email match against Twenty workspace members — users must be invited to Twenty before migration runs.

FastTrack company records map to Twenty Companies. Company name, domain/website, industry, employee count, and annual revenue translate field-by-field. Parent-child company hierarchies in FastTrack map to the Parent Company field in Twenty's Companies object. Multi-company affiliations on a single person collapse to the primary companyId plus a note on additional relationships.

FastTrack deal records map to Twenty Opportunities. Deal name, amount, stage, expected close date, and owner all have direct equivalents. FastTrack pipeline-stage values require a value-mapping step to align with Twenty's Opportunities stage pick-list. Probability and forecast-category fields map as custom numeric fields if they exist in FastTrack.

FastTrack custom objects migrate 1:1 to Twenty custom objects on paid tiers. Each custom object in FastTrack requires a corresponding custom object to be created in Twenty Settings → Data Model before migration. Custom object relationships that are N:N in FastTrack map to junction objects in Twenty, which your admin configures post-migration.

FastTrack engagement records (calls, emails, meetings) map to Twenty Tasks and Events. Call and email activities become Tasks with Type set to 'Call' or 'Email'; meeting records become Events with start/end times preserved. Original timestamps, owners, and the linked person/company ID are all preserved on the Twenty records.

FastTrack notes attach to the relevant person, company, or deal record and map to Twenty Notes. File attachments in FastTrack are re-uploaded to Twenty's file storage and linked to the parent record. File size limits apply — FastTrack files over Twenty's storage threshold are flagged for manual handling.

FastTrack owner IDs resolve to Twenty workspace members by email match. All FastTrack users who own records must have Twenty accounts created before migration. Unmatched owners are flagged and assigned to a fallback owner — no record lands without a valid Twenty user.

FastTrack custom properties do not auto-create fields in Twenty. Each custom property requires manual field creation in Twenty Settings → Data Model before migration runs. Field types (text, number, date, select, multi-select, relation) must match the source property type. FlitStack delivers a field-creation checklist as part of the migration plan.

FastTrack workflows, sequences, triggers, and custom scripts do not migrate to Twenty. They must be rebuilt in Twenty's workflow builder using Twenty's trigger types (record creation, field change, scheduled) and action constructs. FlitStack exports FastTrack workflow definitions as JSON and delivers a rebuild reference document for your Twenty admin to reconstruct the logic.

FastTrack reports and dashboards do not migrate — the underlying data moves but the visualization layer must be recreated in Twenty. Twenty's Views and Charts provide reporting capability with different configuration semantics than FastTrack, requiring manual rebuild by your admin.

FastTrack third-party integrations (connected apps, webhooks, external data sources) must be rebuilt against Twenty's API or reconfigured in the integrations marketplace. FlitStack documents the full integration stack including API endpoints, authentication methods, and webhook URLs for reference during reconnection.

FastTrack association labels that describe a person's role on a deal (Decision Maker, Champion, Influencer) have no native equivalent in Twenty. These migrate as custom pick-list fields on the People object or as notes on the Opportunity, depending on your reporting needs.