Migrate from ChartMogul to HighLevel

ChartMogul's parent Customer record carries name, email, tags, custom attributes, notes, call logs, and opportunities. We map these directly to GoHighLevel Contact fields. The ChartMogul external_id becomes a custom field chartmogul_id__c on the GoHighLevel Contact for cross-system referencing. Tags migrate as GoHighLevel Tags; custom attributes migrate as custom fields on Contact with naming convention cf_chartmogul_<attributename>.

Each ChartMogul Data Source Customer (one per billing source: Stripe, Chargebee, Recurly) belongs to a parent Customer. We consolidate all child data source records into the single GoHighLevel Contact by writing the primary billing source (name, customer_id from billing system, plan details) into custom fields on the Contact. If the customer has multiple active billing sources, we create a primary contact record and store secondary billing source details in a JSON-encoded custom field or separate linked custom object.

Active, trial, and cancelled Subscriptions map to GoHighLevel Opportunities using a Subscription record type we create in the destination. We store plan_id, quantity, billing interval, and MRR as custom fields on the Opportunity. Cancelled subscriptions become Closed-Lost opportunities with a cancellation reason field. This is a configuration mapping rather than a direct 1:1 because GoHighLevel does not natively track subscription state the way ChartMogul does.

Plan definitions from ChartMogul (name, interval, amount, currency, trial period) migrate to a GoHighLevel custom object Plan__c. Each Plan__c record stores the billing interval, amount, currency, and trial days. Opportunity records link to Plan__c via a lookup relationship. If the destination GoHighLevel account uses the Standard plan tier, API access is limited and custom object creation may require the Unlimited plan; we confirm plan tier during scoping.

Invoice records including line items, amounts, taxes, and transaction fees migrate to a GoHighLevel custom object Invoice__c linked to the Contact record. We map invoice_number, amount, currency, status (paid, open, void), and due_date as custom fields. Line items migrate as separate Invoice_Line_Item__c records with a lookup to Invoice__c. Invoice PDFs do not migrate via API; we flag them for manual upload post-migration.

Payments, refunds, and chargebacks map to GoHighLevel Transaction__c records linked to Invoice__c. We handle the transaction fee handling discrepancy (Google Play and PayPal deduct fees automatically; Stripe and Chargebee do not) by reading ChartMogul's current fee handling setting during scoping and applying it consistently to all imported transactions. Any fee discrepancies are flagged before import so the customer can validate before records land in GoHighLevel.

Tags on ChartMogul parent Customer records migrate to GoHighLevel Tags directly. Tag counts and tag membership are preserved 1:1. GoHighLevel Tags apply across contacts and companies, matching ChartMogul's flat tagging model. We validate tag character encoding during scoping since special characters may differ between platforms.

ChartMogul CRM Opportunities (with stage, value, and owner) map directly to GoHighLevel Opportunities. The deal stage maps to a GoHighLevel pipeline stage; the deal amount maps to Amount. Owner assignment resolves by email match to the GoHighLevel User. We create a pipeline stage set in GoHighLevel matching ChartMogul's stage names before migration begins.

Open tasks on ChartMogul Customer records migrate to GoHighLevel Tasks linked to the Contact. We migrate due date, completion status, assignee, and task body. Completed tasks with no future action are optionally omitted to reduce import volume; the customer chooses this during scoping. Task assignment resolves by email match to GoHighLevel User.

ChartMogul Notes and call logs migrate to GoHighLevel Notes linked to the Contact. Call logs include duration and disposition where available as custom Note fields. Plain text content migrates as-is; rich formatting differences between platforms may require light normalization. Call recordings referenced by URL migrate as a custom URL field rather than embedded media.