Migrate from AllClients to Twenty CRM

AllClients Contact records map directly to Twenty Person records. We extract Contacts.csv from the Data Migration menu and import it via Twenty's REST API. The Person.CompanyId field is resolved by matching the AllClients contact's company name against Twenty Company records created in a prior pass. Any contacts whose company does not resolve are held for manual review rather than inserted without a link.

AllClients exports Notes as a separate Notes.csv file that is not joined to Contacts.csv. We run a join step using the contact's email address as the key to associate each note with its Person record in Twenty. If the email address changed between exports, we fall back to first and last name matching and flag unmatched notes in a reconciliation report. Notes migrate as Comment records on the Person object.

AllClients Company property on the contact record maps to a separate Twenty Company object. We deduplicate company names during import using the domain as a secondary dedupe key. Company records are created before Person records so that the Person.CompanyId foreign key is satisfied at the time of Person insert. AllClients does not have a native Companies object; company data lives as a free-text property on each Contact row, so we deduplicate across all contacts to build the Company table.

AllClients account-level custom fields map to Twenty custom fields defined in Settings → Data Model before migration. Each custom field definition is discovered during scoping, and the equivalent Twenty field is created with the matching type (text, number, date, select). Custom field values from the Contact CSV populate the corresponding Twenty custom field at import time.

Tags applied to AllClients contacts are exported as comma-separated values within the contact record. We parse the tag string, create or match each tag in Twenty's Tag table, and create PersonTag records linking the Person to each Tag. Multi-value tag handling is direct since Twenty's tag model natively supports multiple tags per person.

AllClients Groups are logical contact collections with no independent export. We capture group membership by filtering contact exports by group and recreate each group as a custom multi-select picklist or a dedicated tag on the person record. For named groups with meaningful business context (e.g., VIP Clients, Referral Partners), we create a dedicated Workspace collection and document the membership list for manual enrollment or a post-migration bulk-tag script.

AllClients Workflow definitions are exported as inactive configuration templates. We document the trigger, conditions, actions, delays, and enrollment criteria for each active workflow and deliver a written inventory with recommended equivalents in Twenty's Settings → Workflows. Execution state and historical run data do not export; contacts already enrolled in AllClients workflows will not carry over their enrollment status.

AllClients email templates are HTML blobs stored under Email Marketing. Twenty has no native email template library. We export email templates as HTML files and deliver them as an asset package for the customer to import into their chosen email platform (Klaviyo, Mailchimp, Postmark). No native email template migration occurs because the destination platform does not store them.

AllClients Campaigns represent scheduled email sends linked to contact segments. Campaign history (send dates, open rates) is metadata rather than a discrete data object with a schema. We document campaign names and linked contact segments in a written handoff so the customer can recreate segments and schedule sends in their chosen email platform post-migration.

AllClients tasks attached to contact records are exported as part of the contact export or as a separate task list. We import task titles, due dates, completion status, and assigned owner to Twenty Task records linked to the Person. Task assignment resolves by matching the AllClients user email to a Twenty workspace member.

AllClients users are extracted from the user list (typically 1-2 on base plans). We map each user by email to the corresponding workspace member in Twenty. If a Twenty workspace member does not exist for a given user, we hold the OwnerId reference in a reconciliation queue for the customer's admin to provision the account before record import resumes.

Contact file attachments are downloaded from AllClients storage and re-uploaded as Twenty attachments linked to the Person record. Large binary files are chunked to avoid timeout during download. Attachment file names and upload timestamps are preserved where available from the AllClients export metadata.