Migrate from The Case File to Twenty CRM

Activity history requires record-type disaggregation

The Case File logs calls, emails, and meetings as engagement records that attach directly to a contact or company. Twenty collapses all activity types into a single Tasks and Notes model. When migrating activity history, FlitStack disaggregates each engagement type: call records become Tasks with Type='Call', email records become Tasks with Type='Email' and the body preserved in the task body field, and meeting records become Tasks with the original start/end time stored in custom datetime fields. Meeting body content is stored as a note attachment linked to the task. This transformation preserves the original timestamp and owner of every engagement but changes how activity history appears in the Twenty UI compared to The Case File.

File attachments do not transfer via CSV import

The Case File file attachments stored in its document layer have no equivalent in Twenty's CSV import mechanism. The Twenty CSV import does not ingest binary file attachments. FlitStack generates a full attachment manifest listing each file's name, source record ID, file type, and storage location. Your team can re-upload attachments manually after the migration, or FlitStack can upload files via the Twenty GraphQL API with the correct record relationship for an additional scope fee. File attachments that are critical to deal context should be identified during the audit phase so the re-upload plan is scoped before cutover.

20,000-record export limit requires chunked extraction

Twenty's CSV export is capped at 20,000 records per file. The Case File workspaces with more than 20,000 total records require FlitStack to extract in multiple passes — either by object type (Companies, then People, then Opportunities), by date range, or by record ID offset. The chunked extraction is then re-assembled in the correct dependency order before loading into Twenty. Chunking adds processing time and requires careful sequencing so that the Companies-pass completes before the People-pass, and the People-pass completes before Opportunities load so foreign keys resolve correctly.

Import order constraint forces staged migration sequencing

Twenty's CSV import enforces a dependency order: Companies must be imported before People, and People must be imported before Opportunities. Custom objects import last after all standard objects are loaded. This constraint means the migration cannot be a single parallel load — it must run in sequence. FlitStack manages this sequencing automatically and uses the delta-pickup window to reconcile any records modified in The Case File during the Companies and People migration passes before Opportunities load. If your The Case File data uses non-standard import ordering from a previous migration, FlitStack re-normalizes the record sequence before loading into Twenty.

Workspace members must accept invitations before owner resolution

Twenty requires workspace members to exist and accept their invitations before owner or assignee references can resolve during import. If a The Case File owner record references an email address for which no Twenty workspace member exists, FlitStack flags that owner as unresolved and assigns the record to a designated fallback workspace member. Your team must pre-invite all intended Twenty users and confirm they have accepted their invitations before the migration runs. FlitStack provides an owner-resolution report in the audit phase listing all The Case File owners, their email addresses, and whether a matching Twenty workspace member exists so you can resolve gaps before data moves.