Migrate from Inception to Twenty CRM

Twenty's import order constraint blocks cross-object references until parent records land

Twenty enforces a strict import sequence: Companies must be created first because People records hold a companyId foreign key, and Opportunities must be created last because they reference both Companies and People. If your Inception export arrives as a flat CSV without respecting this dependency order, the import will fail for any People record that references a companyId not yet present in Twenty. FlitStack AI sequences the migration passes explicitly and re-orders source records so foreign keys resolve on each pass. We also surface any orphaned records — People in Inception with no linked Company — before the migration runs so you can decide whether to create placeholder Company records or exclude those People.

Inception's pharma-specific custom fields require pre-creation in Twenty before import

Inception's data model includes custom fields specific to pharmaceutical sales workflows — therapeutic category, prescribing tier, physician specialty, territory assignment codes. Twenty's CSV import creates records, not fields. Custom fields must be created in Settings → Data Model before the import pass runs, with field types matched to the Inception source type (select → select, number → number, text → text). Twenty's field type cannot be changed after creation, so mismatches must be corrected by deleting the field and recreating it. FlitStack AI audits your Inception custom field inventory before migration and delivers a field-creation checklist mapped to your Inception schema so Twenty is schema-ready before data lands.

Twenty's 20,000-record export ceiling requires chunked processing for large Inception datasets

Twenty's CSV export is capped at 20,000 records per operation. Inception deployments with more than 20,000 People, Companies, or Opportunities records require batched export runs with pagination or date-range filters. If your Inception instance holds 50,000+ records, we coordinate a multi-batch export strategy, validate record counts across batches, and merge them into a unified import pipeline. We also verify that the 20K export ceiling does not silently truncate your largest object before you sign off on the migration scope.

Inception workflows and pharma process automation have no Twenty equivalent and must be rebuilt

Inception CRM includes built-in automation tied to pharma sales processes — visit-cycle scheduling, physician targeting rules, and territory-based task generation. Twenty CRM's workflow builder supports basic triggers (record created, field updated) but does not have a native equivalent to Inception's domain-specific automation logic. Any workflow, sequence, or automated process running in Inception is scoped out of the data migration. We export your Inception workflow definitions as a structured reference document and recommend a rebuild sequence for your Twenty admin. The FlitStack migration deliverable is data and schema only — automation rebuilds are a separate configuration workstream.

Twenty Workspace Members must be invited before owner resolution can run

Inception owner assignments reference user records within the Inception platform. When migrating to Twenty, these owner references must resolve against Twenty Workspace Members. If a member with the matching email does not exist in Twenty at migration time, the owner link is unresolved and the record lands with no assignee. We require that all Inception users with open record assignments be invited to Twenty and accept their invitations before the migration begins. We provide an invitation checklist with email addresses extracted from Inception so your admin can pre-stage the member list without hunting through individual user profiles.