Migrate from Actionstep to Twenty CRM

Legal accounting data has no Twenty CRM destination

Actionstep's trust accounts, IOLTA ledgers, client ledger balances, and billing totals are legal-specific financial records with no equivalent object in Twenty CRM. Twenty ships with no accounting module — it is a CRM, not a practice management accounting tool. We export this data as CSV for loading into a dedicated legal billing platform (such as LawPay, Clio Grow, or a custom spreadsheet). Attempting to store trust data in Twenty's Opportunity or custom objects would misrepresent financial records and create audit risk. This limitation must be acknowledged before migration scope is finalized.

Actionstep API rate limits require batched extraction

From April 2024, Actionstep introduced rate limiting across all public API endpoints. The API uses a user-context model — all API activity runs under the authenticating user's security context and is logged against that user session. The System Administrator account cannot be used for API access. Page size is capped at 200 records per request. We extract data in paginated batches, throttling to avoid limit hits, and use the sandbox environment first to validate extraction logic. Rate limit errors during extraction are retried with exponential back-off; extraction resumes from the last successful page cursor.

Twenty import order is strict — Companies must precede People

Twenty's CSV import enforces referential integrity: you cannot import a Person with a companyId unless the Company record already exists. Similarly, Opportunities must reference an existing companyId. We sequence the migration in this exact order: (1) Companies, (2) People linked to Companies by domain or email-domain match, (3) Opportunities linked to Companies and People, (4) Custom Objects last after parent records exist. Circular references (company A lists company B as parent; company B lists A as parent) are flagged and resolved manually before the migration runs. If your Actionstep data has Participants without any company link, they land in Twenty as People with no companyId — this is valid and handled by Twenty's schema.

Participant roles need a custom field in Twenty

Actionstep Participants have a role field (Client, Witness, Opposing Counsel, etc.) that is native to the platform. Twenty People has no native role field — there is no built-in equivalent for contact roles in the legal sense. We create a custom SELECT field (Participant_Role__c) on the People object and populate it with the exact role values from Actionstep. Roles that have no natural Twenty equivalent (e.g., 'Barrister', 'Mediator') are preserved as custom pick-list values. If your firm uses roles to drive downstream logic, this custom field must be recreated in Twenty's Settings → Data Model before migration — we cannot create it automatically through CSV import.

Workflows and step automations do not transfer

Actionstep's Builder workflow system — step triggers, email automations, document generation rules, and matter-typed process automations — is a proprietary configuration layer that has no equivalent in Twenty's schema. Twenty's Workflows feature (Settings → Workflows) provides automation for record-level triggers, but the Actionstep workflow logic must be manually rebuilt. We export your Actionstep workflow definitions as structured JSON plus human-readable HTML documentation describing every trigger, condition branch, and action sequence. Your Twenty admin uses this as a rebuild checklist. Budget 1–3 days of admin time per significant workflow for manual reconstruction in Twenty's visual workflow builder.