Migrate from ChartMogul to Freshsales

ChartMogul parent Customer records map to Freshsales Contact. We extract name, email, phone, address, and company name from the parent object. ChartMogul's external_id on the parent becomes Freshsales' unique_id field for cross-system reconciliation. Tags from the parent Customer migrate to Freshsales Contact tags. The ChartMogul data source customer child records are resolved to the same Contact via external_id matching before subscription data is attached.

Each ChartMogul Data Source Customer (one per billing system: Stripe, Chargebee, Recurly) is linked to the parent Contact via matched external_id. We store the data source identifier and original ChartMogul customer UUID as custom fields on the Freshsales Contact for traceability. This mapping is necessary because Freshsales has no native data source concept; the billing origin is preserved as metadata rather than as a separate object.

Active Subscriptions from ChartMogul migrate to Freshsales in two places: plan-level details (plan name, interval, quantity, MRR contribution) store as custom fields on the Contact record; open Deals in ChartMogul (if any) map to Freshsales Deals with the subscription MRR as the deal value. Cancelled and trial subscriptions store with status as custom fields but do not create open Deals. We use the subscription state_at field to determine active versus churned.

ChartMogul Plan definitions (name, interval, amount, currency, trial period) store as custom fields on the Freshsales Contact or as a Product record if the customer's Freshsales instance uses Products for deal line items. Plan history is preserved by capturing the current plan at migration time; plan change attribution that ChartMogul calculates as MRR expansion or contraction is not migratable as a movement but is preserved as a field value for Freshsales reporting.

ChartMogul Invoices do not have a native equivalent in Freshsales. We migrate invoice metadata (invoice number, date, amount, currency, status) as a JSON blob or structured custom fields on the Contact record. Full invoice PDF files are not migratable as Salesforce-style attachments in Freshsales via standard API; we document the invoice record count and recommend the billing system as the source of truth for invoice PDF retrieval post-migration. Transaction-level records (payments, refunds, chargebacks) migrate as structured custom fields or are documented for manual reconciliation.

ChartMogul customer-level custom attributes migrate to Freshsales Contact custom fields. We map attribute types (string, number, date, boolean) to equivalent Freshsales field types. Attributes synced from Pipedrive or HubSpot via ChartMogul's CRM sync migrate with their original values. We create the custom field schema in Freshsales during the schema design phase before data import begins.

ChartMogul flat string tags on parent Customer records migrate 1:1 to Freshsales Contact tags. Tag counts for segmentation are preserved. Tags are imported after Contact records exist so that tag assignments resolve at insert time rather than requiring a post-import tag migration step.

ChartMogul CRM Opportunities map to Freshsales Deals with stage, value, owner, and close date preserved. ChartMogul deal stages map to Freshsales pipeline stages; we configure the Freshsales pipeline before migration to match the ChartMogul stage names and probabilities. The Deal's linked Contact (from the parent Customer mapping) attaches at import time via the Contact's unique_id.

Open Tasks from ChartMogul migrate to Freshsales Task with subject, due date, assignee, and completion status preserved. Completed tasks with no future action are optionally omitted to reduce import volume. Task assignment resolves via ChartMogul owner email matched to Freshsales User email. Notes and call logs from ChartMogul migrate as Freshsales Note records attached to the parent Contact via ContentDocumentLink.

ChartMogul MRR Movements (new business, expansion, contraction, churn) are computed metrics generated by ChartMogul's metric engine from subscription state changes. They are not raw records but analytical outputs tied to ChartMogul's calculation methodology. We do not migrate MRR Movements. We migrate the underlying Subscription and Invoice data that drives them, and we deliver a written MRR reporting inventory (current MRR by plan, by cohort, by data source) for the customer's admin to rebuild in Freshsales analytics or a BI tool post-migration.