Migrate from OneSuite to Twenty CRM

OneSuite Clients hold both company and contact data on a single record (contact details, company info, social links, revenue, ICP status). We split this into a Twenty Company record (company-level fields) and a Twenty People record (contact-level fields) linked to the Company via a relationship field. The split is computed using the presence of company name, domain, and revenue fields to determine which fields belong to Company versus People.

OneSuite Leads map directly to Twenty People records with a custom lead_status field preserving the original OneSuite stage (New, Contacted, Qualified, Converted). Source attribution and scoring values from OneSuite migrate as custom fields on People. We use email address as the dedupe key during import to avoid creating duplicate People records for Leads that share an email with an existing Client contact.

Twenty has no native project object. We create a Project custom object in Twenty's Data Model with fields for name, description, status, client (linked to the Company record), start date, end date, and budget. The Client-to-Project relationship is preserved by linking the custom object's company field to the migrated Company record. If the customer uses Project templates, we migrate template metadata separately and flag the template automation logic for manual rebuild.

OneSuite Invoices contain line items, tax rates, payment status, and currency. Twenty has no native invoice object. We migrate invoice records as Note records attached to the relevant Company or People record, with the invoice number, amount, status, and currency preserved in the Note body and as custom fields. Complex multi-currency invoices or custom tax configurations are flagged for manual reconciliation post-migration.

OneSuite Documents can be associated with Clients or Projects. We migrate document metadata (name, type, URL, created date) as attachments on the relevant Company, People, or Project custom object. Binary file content is not migrated directly; we transfer URLs and flag any Documents exceeding the source account's tier storage cap (30 GB Freelancer, 60 GB Growing Agency) for a separate post-migration file transfer step.

OneSuite custom fields are flattened directly onto entities with slug-based keys (e.g. clientTier, projectPriority). We parse the API response, create equivalent typed fields in Twenty's Settings → Data Model before migration, and map each slug to the destination field name. If a destination field does not exist, we flag it for creation and hold that entity's migration batch until the field is provisioned. This prevents custom field values from being silently dropped during import.

OneSuite Members are team users assigned to Projects, Clients, and Invoices. We extract all Members referenced across entities and map them to Twenty Members. We resolve by email match. Any OneSuite Member without a matching Twenty User is held in a reconciliation queue. Per Twenty's documentation, users must be invited and accept before importing records that reference them, otherwise Owner relationships cannot be mapped.

OneSuite Lead pipeline stages are user-defined. We map stage names and ordering to a custom select field on the People object in Twenty. Stages with custom automation or scoring rules are flagged in the migration inventory for manual reconfiguration in Twenty because automation logic cannot be replicated in the migration scope.

OneSuite Project and Document templates contain metadata and field structure. We migrate template names, descriptions, and field definitions as Note records on the relevant objects. Template automation logic (workflow triggers, auto-assignment) cannot be replicated automatically and is included in the written automation inventory delivered post-migration.

OneSuite Files attach to Projects, Tasks, or Invoices. We transfer file metadata (name, type, URL, size) as attachments on the relevant migrated record. Files approaching or exceeding plan storage caps (30 GB Freelancer, 60 GB Growing Agency) are flagged before migration so the customer can decide whether to upgrade OneSuite storage, archive files externally, or migrate file URLs only.