Migrate from Fulcrum Snap to Twenty CRM

Twenty requires custom object fields to exist before CSV import

Fulcrum Snap's matter records contain billing type, practice area, responsible attorney, and client reference fields that have no direct equivalent in Twenty's standard schema. Twenty's import function creates records, not fields — we must pre-create Matter, Invoice, and TimeEntry as custom objects with all required custom fields in Twenty Settings → Data Model before any CSV data is loaded. If custom fields are missing, the import will reject records with unmapped column headers. We deliver the custom object and field definition plan as part of the pre-migration setup package so your Twenty admin can create the schema before data lands.

Import order constraint forces sequencing in migration script

Twenty's data model enforces referential integrity: Company records must exist before People records can reference a companyId, and People/Matter records must exist before TimeEntry records can link to them. If we attempt to load People records referencing a companyId that does not yet exist in Twenty, the import will fail or leave the relation null. We solve this by sequencing the migration as three phases: (1) Companies, (2) People with resolved companyId, (3) Opportunities and custom objects (Matters, Invoices, TimeEntries) in dependency order. This sequencing adds planning overhead and must be reflected in the migration script.

Fulcrum Snap workflows and automations have no migration path

Fulcrum Snap automations run within the SAP Business Workflow engine and do not export to a format compatible with Twenty's limited workflow builder. Sequences, approval chains, and triggered email notifications in Fulcrum Snap cannot be migrated — they must be rebuilt in Twenty or documented for manual recreation. Twenty's workflow builder supports basic conditional actions (create task, update field, send notification) but lacks the process-routing depth of SAP Business Workflow. We can export your Fulcrum Snap workflow definitions as a reference document for your Twenty admin to use during the rebuild phase.

Attachment re-hosting requires file-type compatibility check

Fulcrum Snap documents attached to matters are stored in Fulcrum's file management system and may include formats that Twenty's file storage does not support natively (e.g., SAP archive formats, .msg files, or large CAD attachments). During migration, each attachment is downloaded, checked against Twenty's supported file types, and either re-uploaded directly or flagged for manual conversion. If a significant portion of your Fulcrum Snap documents use unsupported formats, your team should budget time for pre-migration file conversion or accept that those attachments will be linked via URL reference rather than embedded in Twenty.

Twenty Pro tier caps custom objects at 10

Fulcrum Snap matter records often contain multiple related data types (time entries, billing records, document versions) that each become a custom object in Twenty. If your migration requires more than 10 custom objects — for example, Matter, Invoice, TimeEntry, DocumentVersion, ConflictCheck, EngagementLetter, Budget, Disbursement, TrustRecord, and MatterNote — the Twenty Pro plan at $9/user/month will not accommodate the full schema. You must upgrade to the Twenty Organization plan for unlimited custom objects. We surface the custom object count in the pre-migration audit and flag whether your target Twenty plan supports your data model scope.