Migrate from FactBox to Twenty CRM

FactBox contacts migrate as Twenty People records. Email, phone, job title, and address fields map directly. Each contact's primary company link resolves to a Twenty Company by domain match; if no match exists, the company link is preserved as a text field for post-migration resolution.

FactBox company records map directly to Twenty Companies. Industry, employee count, annual revenue, and website fields transfer as-is. FactBox parent-child company hierarchies map to Twenty's company relation field — parent must be migrated first to resolve circular references. Company domain serves as the unique identifier for matching and deduplication during the import process.

FactBox cases become Twenty Opportunities. Case status values (Active, Closed, Pending) map to Opportunity Stage pick-list values your admin configures in Twenty. The case name becomes the Opportunity name; case description maps to the opportunity body or a custom text area field.

FactBox facts (individual data points linked to cases) have no Twenty equivalent. We migrate fact text as a custom field (FactBox_Fact__c) on the related Opportunity, or as a Note attached to the case record for freeform retention. Complex fact hierarchies may require a custom object.

FactBox evidence records combine document reference, exhibit number, and legal status. The document link migrates as a Note on the related Opportunity; exhibit metadata migrates as custom fields (Evidence_Exhibit__c, Evidence_Type__c). Teams needing full evidence chain tracking should create a custom Evidence object in Twenty.

FactBox witness records include contact info plus witness-specific data (deposition date, testimony summary). Contact fields migrate to a Twenty People record; witness-specific attributes (Witness_Status__c, Deposition_Date__c) become custom fields on the People record or a linked custom Witness object. This requires a two-pass migration where People records are created first before witness-specific custom object records are linked.

FactBox documents linked to cases migrate as Notes on the related Opportunity. Document name becomes the Note title; document content or file reference becomes the Note body or a link field. Large file attachments are re-uploaded to Twenty's storage with the original filename preserved.

FactBox issues (legal issues tracked per case) have no direct Twenty equivalent. Issue names and codes migrate as a custom multi-select field (Case_Issue__c) on the Opportunity object, enabling filtering and reporting by legal issue in Twenty's views. This allows teams to maintain issue categorization without losing the ability to segment cases by legal matter type.

FactBox activities logged against cases migrate as Twenty Tasks or Events on the related Opportunity. Original timestamps and assigned user preserved during migration. If FactBox tracks calendar events with specific start and end times, these map to Twenty Events with full datetime preservation for calendar synchronization and deadline tracking.

All FactBox custom fields on contacts, companies, cases, witnesses, and evidence migrate as Twenty custom fields. Field types map: text→text, number→number, date→date, picklist→select, multi-select→multi-select. Custom fields must be created in Twenty Settings → Data Model before migration runs to avoid import errors or skipped field values.

FactBox users are matched to Twenty Workspace Members by email. Unmatched owners are flagged before migration — your team invites them to Twenty first or assigns records to a fallback member. No record lands in Twenty without a resolved owner to maintain accountability and assignment integrity.

FactBox integrations with billing systems, document platforms, or court e-filing services do not transfer to Twenty. Twenty's REST/GraphQL API and webhook support enable rebuilding these connections using custom scripts or middleware. FlitStack provides an integration reference document listing each connection that requires rebuild, including endpoint URLs, authentication methods, and payload formats from the original FactBox configuration.