Migrate from Prospects CRM to Twenty CRM

Prospects CRM Contact maps directly to Twenty's People object. Standard fields (firstname, lastname, email, phone, jobtitle) migrate to Twenty's name, email, phone, and jobTitle fields. The companyId relation requires the Company record to exist first — FlitStack sequences companies before people during migration so foreign-key links resolve correctly.

Prospects CRM custom fields on Contact (beyond standard fields) map to custom fields on Twenty's People object. Before migration, FlitStack generates a custom-field creation plan for Twenty's Data Model → Fields UI. Fields like custom pick-lists, date fields, and numeric fields are created as matching types in Twenty. Notes fields become Twenty Note records linked to the People record.

Prospects CRM Company maps to Twenty's Company object with direct field mapping for name, domain/website, industry, numberofemployees, and annualrevenue. Multi-level company hierarchies (parent/child) in Prospects CRM map to the Parent CompanyId field in Twenty's Companies object. Industry pick-list values require value-by-value mapping when Prospects uses a controlled vocabulary.

Prospects CRM's stock-aware Company fields that link to inventory platforms (Unleashed, Katana, Cin7, Xero, Sage 50) have no direct Twenty CRM equivalent since Twenty has no native inventory model. FlitStack preserves these as custom text fields on the Company record for reference — teams using inventory platforms must rebuild those integrations via Twenty's REST API or a middleware layer post-migration.

Prospects CRM Deal maps to Twenty's Opportunity object. Direct field mappings include dealname → name, amount → amount, closedate → closeDate, and owner → workspaceMember (resolved by email match). Deal stage (dealstage) maps to Twenty's stage field via value mapping where Prospects stage names are translated to the target stage pick-list values defined in the Twenty workspace.

Prospects CRM pipeline stages (dealstage pick-list values) map to Twenty's Opportunity stage field value-by-value. FlitStack extracts the full stage vocabulary from Prospects CRM and generates a stage-mapping table that the Twenty workspace admin pre-loads into Settings → Data Model → Opportunities → Stage before the migration runs. Stage-entered timestamps from Prospects are stored as custom datetime fields for reporting continuity.

Prospects CRM custom fields on Deals (probability overrides, deal source, decision-maker type, custom amounts) migrate to Twenty custom fields on the Opportunity object. FlitStack documents each custom field's type (pick-list, number, text, date) and the matching Twenty field type to create before migration day. Custom pick-list fields require the options to be pre-created in Twenty's Data Model.

Prospects CRM activity records (calls, emails, meetings, notes) map to Twenty's Task, Event, and Note objects. Call activities become Tasks with Type='Call'; email records become Tasks with Type='Email'; meetings become Events with original start/end times and attendees preserved. Notes migrate as Twenty Note records and are linked to the parent record (People, Company, or Opportunity) by ID. Original timestamps and owner assignments are preserved.

Prospects CRM owner IDs are resolved by email match against Twenty Workspace Members. FlitStack generates a pre-migration user map: any Prospects owner with a matching email in Twenty becomes that WorkspaceMember's Opportunities and People records. Owners without a Twenty account are flagged before migration — teams either invite them to the Twenty workspace first or assign records to a fallback WorkspaceMember. This step must complete before Opportunity migration because OwnerId is required on Opportunity records.

Prospects CRM custom objects (available on higher tiers) map 1:1 to Twenty's custom objects. Custom object definitions (name, fields, types) are extracted from Prospects CRM's schema export and recreated in Twenty via Settings → Data Model → Objects. Custom-object associations that use a many-to-many model in Prospects require a junction object in Twenty — FlitStack surfaces this in the migration plan before the run commits.

Prospects CRM file attachments on records (documents, images, PDFs) have no native file storage in Twenty CRM. FlitStack downloads attachments from Prospects, re-uploads them to a destination storage location (S3-compatible bucket or Twenty's file attachments feature if available), and stores the file URL as a custom field on the linked record. Teams using Prospects' native file viewer will need to access files via the stored URL after migration.

Prospects CRM workflows and automation rules are not migratable to Twenty CRM. These must be rebuilt manually in Twenty's workflow builder. FlitStack exports Prospects workflow definitions as a structured reference document listing each rule's trigger, conditions, and actions — this document is delivered alongside the migration and serves as the rebuild brief for the Twenty admin. Views and permissions are similarly not migratable and must be reconfigured in Twenty's workspace settings.