Migrate from Clientjoy to Twenty CRM

Clientjoy Leads map to Twenty Persons. Clientjoy stores lead name, email, phone, source, status, pipeline stage, and custom fields on Leads. Twenty's Person object is sparse by default (per GitHub issue #13953, standard fields like jobTitle, department, website, and socialProfiles must be created manually). We create these fields during schema setup before import so that Clientjoy's lead properties map to typed Twenty fields rather than custom fields. Pipeline stage assignments from Clientjoy preserve as a custom field on Person for reporting continuity.

Clientjoy Customers (companies or organizations tied to leads) map to Twenty Companies. Clientjoy stores company name, domain, address, contact count, custom fields, and lifecycle status on Customers. We map these to Twenty's Company object fields and create any missing standard fields (industry, employeeCount, website) during schema setup. Company is created before Person import so that the Person-Company relationship is satisfied at insert time.

Clientjoy Pipelines map to Twenty Opportunities grouped by pipeline name. Clientjoy pipelines define stages with names, probabilities, and ordering; these migrate as Opportunity custom fields and a Stage picklist we create in Twenty. Multiple Clientjoy pipelines require multiple Twenty opportunity groupings via a pipeline_name custom field, since Twenty does not have a native multi-pipeline feature like Clientjoy's pipeline selector.

Clientjoy Deals map to Twenty Opportunities. The Clientjoy deal amount, close date, stage, owner, and associated pipeline migrate to Twenty Opportunity fields. We resolve HubSpot-equivalent fields (dealstage maps to stage_name, pipeline maps to pipeline_name custom field, owner email resolves to Twenty User). Closed-won and Closed-lost reasons from Clientjoy custom properties become Opportunity custom fields.

Clientjoy Invoices (one-time and recurring) have no native Twenty CRM equivalent. Twenty is a CRM without billing functionality. We export invoice headers, line items, tax rates, payment status, due dates, and currency as a structured CSV. This CSV is delivered alongside the migration for import into a complementary billing tool (Stripe, Quaderno, Zoho Invoice, or similar) or manual recreation. Recurring invoice schedules are documented as metadata. This is a functional gap that the customer must address post-migration with a separate tool.

Clientjoy Documents and Templates migrate as Twenty File attachments linked to the parent Person, Company, or Opportunity. We extract document content, template merge field associations, and e-sign status metadata. Clientjoy's e-sign audit trails (cryptographic signing records) do not have a Twenty equivalent; signed PDFs are exported and delivered as files. Document formatting may not survive translation intact due to Clientjoy's document builder limitations. We recommend reviewing document outputs in a staging environment.

Clientjoy Email Sequences (automation sequences tied to triggers and delays) do not migrate as functional code. Twenty's Workflow feature supports record-triggered automations but does not replicate Clientjoy's sequence cadence model. We deliver a written inventory of every Clientjoy Email Sequence with its trigger conditions, step count, delay rules, and CRM actions for the customer's admin to rebuild in Twenty Workflows or a dedicated sales engagement tool post-migration.

Clientjoy custom fields on Leads and Customers migrate to Twenty custom fields on Persons and Companies. Clientjoy's field types (text, dropdown, date, checkbox, number) map to equivalent Twenty field types. Custom field definitions are created in Twenty's Settings → Data Model before data import. Note that Clientjoy custom fields are only available on the Agency plan and above; Starter-plan users will not have custom field definitions to migrate.

Clientjoy's Client Portal configurations including white-label settings, custom domain, CSS styling, and embedded widgets have no Twenty CRM equivalent. We export the portal configuration as a written specification document describing current settings, branding, and access controls. Rebuilding a client portal requires custom development on top of Twenty or adopting a dedicated client portal tool (Hyperlane, Casca, or similar) post-migration.

Clientjoy Appointments migrate to Twenty CalendarEvent records with date, time, invitee, status, and location preserved. Booking page configurations are exportable as metadata but require recreation in a separate scheduling tool (Cal.com, Calendly, or similar) since Twenty does not have a native appointment booking feature. We deliver the booking page configuration as a setup guide for the customer's admin.

Clientjoy Web Form definitions and field-to-Lead mappings migrate as a written specification document. Twenty has no native web form builder. We preserve the form field structure, routing logic, and field mapping so that forms can be rebuilt in a dedicated form tool (Typeform, HubSpot Forms, or similar) with submissions routed to Twenty via API or webhook. Form-to-Lead associations are documented in our mapping table for post-migration routing setup.

Clientjoy Owners (team members assigned to Leads, Customers, Deals) map to Twenty Users. We resolve by email match. Any Clientjoy Owner without a matching Twenty User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Clientjoy users are mapped to inactive Twenty Users to preserve assignment history.