Migrate from ChartMogul to Twenty CRM

The parent Customer record (with tags, custom attributes, notes, call logs, opportunities, and tasks) maps to a Twenty Company. The ChartMogul customer name becomes the Company name field. We use ChartMogul's customer UUID as the Company record's external_id so that child Data Source Customer records can reference it correctly. Tags migrate as text tags on the Company; custom attributes migrate as custom fields on the Company object after the customer configures the field schema in Twenty's Data Model settings.

Each child Data Source Customer created by a connected billing source (Stripe, Chargebee, Recurly) maps to a secondary Company record tagged as a billing source instance, linked to the parent Company via a custom Company relationship field. This preserves the ChartMogul two-level model as two distinct Company records with a defined relationship rather than collapsing it into one record and losing the billing source attribution.

ChartMogul Subscriptions (with plan_id, quantity, billing cycle, MRR contribution, status) do not have a direct Twenty CRM equivalent since Twenty has no native subscription tracking object. We map active subscriptions to custom fields on the Company record (subscription_status__c, subscription_mrr__c, subscription_plan__c) and import plan definitions as Product records in Twenty's Products module so that opportunity line items can reference them.

ChartMogul Plan definitions (name, interval, amount, currency, trial period) map to Twenty Product records. The plan's monthly recurring amount becomes the Product's price. Plan intervals (monthly, annual, quarterly) map to Product billing intervals where applicable. We import plan definitions before subscriptions so that subscription_plan__c references resolve correctly.

ChartMogul Invoices (with line items, amounts, taxes, and transaction fees) migrate as a combination of a closed-won Opportunity record (with the invoice amount as the Opportunity amount and the invoice number as the Opportunity name) and a Note record attached to the Company holding the full invoice detail. We read ChartMogul's transaction fee handling setting during scoping and apply it consistently so that the Opportunity amount reflects the net revenue after fees.

Payments, refunds, and chargebacks are imported as Notes attached to the parent Company, preserving the transaction type, amount, date, and currency. For accounts with high transaction volume, we consolidate transactions into monthly summary records on the Company rather than importing each individual payment as a separate Note, reducing import volume while preserving financial history.

ChartMogul's MRR Movement records (new business, expansion, contraction, churn, reactivation) are not natively supported as objects in Twenty. We derive a current MRR figure and MRR movement history from ChartMogul's export and store the most recent MRR state as custom number fields on the Company record (current_mrr__c, mrr_last_updated__c). Historical movement breakdowns are documented in a CSV delivered alongside migration for the customer to build reporting on in Twenty's dashboarding.

ChartMogul CRM Opportunities (with stage, amount, owner) map directly to Twenty Opportunities. The ChartMogul dealstage maps to a Twenty Opportunity stage (which the customer configures during workspace setup). Open and won opportunities migrate with stage, amount, close date, and owner preserved. Closed-lost opportunities migrate at the customer's discretion to preserve historical pipeline data.

ChartMogul call logs migrate to Twenty Task records with the call disposition, duration, and notes preserved in the Task body. The Task is linked to the correct Company or Person record by resolving the customer reference at migration time. Activity timestamps are preserved so the timeline ordering is maintained.

ChartMogul email engagement records migrate as a Task (representing the activity timeline entry) with a linked Note holding the email body and metadata (sender, recipient, subject). The Task is linked to the Company or Person record; the Note is attached via Twenty's file linking mechanism. Email attachments migrate as Note attachments where present in the source record.

ChartMogul meeting engagements (with attendees, location, start and end time) migrate as Task records with the meeting title as the Task subject and meeting notes in the Task body. Attendee information is stored as a text list in the Task since Twenty does not have a native EventAttendee object equivalent.

ChartMogul Notes and call logs migrate as Note records attached to the parent Company record. The note creation date and author are preserved in the Note metadata. Call logs include disposition and duration in the note body as plain text since Twenty does not have a structured call log object.