Migrate from ChartMogul to Zoho CRM

ChartMogul's parent Customer record holds the customer's name, email, company, tags, custom attributes, notes, opportunities, and tasks. We import these as Zoho CRM Contacts. If the customer's Zoho instance uses an Account-based data model (common at Professional tier and above), we create a Zoho Account first and attach the Contact to it, using ChartMogul's external_id as the Contact's lookup anchor. Tags migrate to a multi-select picklist field on the Contact; custom attributes map to Zoho custom fields with type alignment during scoping.

Each billing connection in ChartMogul (Stripe, Chargebee, Recurly, PayPal, or app stores) creates its own child Data Source Customer record. We resolve these by matching the Data Source Customer's external_id to the parent Contact record and store the billing source name in a custom field billing_source__c on the Contact. If multiple billing sources apply to the same logical customer, we store each as a separate entry in a multi-line custom field or JSON-encoded custom field rather than creating duplicate Contact records.

ChartMogul Subscriptions carry plan_id, status (active, trialing, cancelled), quantity, billing interval (monthly, annual, custom), MRR contribution, and cancellation timestamps. We map these to Zoho Products with subscription-specific custom fields: subscription_status__c, plan_id__c, mrr_contribution__c, billing_interval__c, subscription_start_date__c, and cancellation_date__c. Active subscriptions link to the Contact via a lookup field. Cancelled subscriptions are imported with status preserved for churn history.

ChartMogul Plan definitions (name, amount, currency, interval, trial period, and plan changes over time) map to Zoho Products as separate records. We store plan details in Zoho custom fields: plan_amount__c, plan_currency__c, plan_interval__c, and trial_period_days__c. When a customer has changed plans over time, we create one Zoho Product record per unique Plan ID to preserve the historical plan attribution for MRR movement analysis.

ChartMogul invoice records contain line items, amounts, taxes, and transaction fees. We import these as Zoho Quotes linked to the Contact (and optionally the Account). Invoice line items map to Quote Items. We store the ChartMogul invoice_id as invoice_id__c on the Quote for traceability. Invoice status (paid, pending, void) maps to a custom field invoice_status__c. We preserve the full invoice history available from the connected billing source, respecting the source's transaction fee handling configuration.

ChartMogul calculates MRR movements (new business, expansion, contraction, churn) from subscription state changes. Zoho CRM has no native MRR object. We reconstruct the MRR timeline by creating a custom field mrr__c (numeric, currency) on the Contact record and populating it with the customer's most recent MRR value at migration time. Historical monthly MRR values and movement classifications (new, expansion, contraction, churn) are stored in a custom MRR history module or as JSON in a large-text custom field for reference. GRR and NRR are stored as custom numeric fields on the Account if Account-based model is used.

Payments, refunds, and chargebacks from ChartMogul map to Quote Line Items with a custom transaction_type__c field distinguishing payment, refund, and chargeback. Transaction fee handling (which applies to Google Play and PayPal sources in ChartMogul) is read during scoping and applied consistently. If the customer has a specific fee-handling preference that differs from the current ChartMogul setting, we flag the discrepancy before import so it does not propagate into the Zoho financial fields.

ChartMogul customer-level custom attributes are key-value pairs set via API or from CRM sync (including attributes synced from Pipedrive or HubSpot). We map each attribute to a Zoho CRM custom field on the Contact module, with data type alignment: string attributes become text fields, numeric attributes become number fields, dates become date fields, and boolean flags become checkbox fields. Attribute names are preserved as field labels; API-safe field names are generated during schema setup.

ChartMogul tags are flat string labels on parent customer records used for segmentation. We migrate them 1:1 to a Zoho CRM multi-select picklist field on the Contact module. If the customer's Zoho instance uses an Account-based model, tags are stored on both the Account and Contact records to preserve segmentation capability at both levels. Tag counts are preserved for use in Zoho's segmentation filters and workflow conditions.

ChartMogul CRM opportunities track deal stages and amounts. We map these to Zoho Deals with stage_name, deal_value, and owner preserved. ChartMogul's opportunity stages map to Zoho CRM pipeline stages; we configure the Zoho pipeline and stage values before migration to match the customer's current ChartMogul stage structure. Open and won opportunities migrate; closed-lost opportunities migrate with status preserved for historical pipeline analysis.

Open tasks from ChartMogul CRM migrate to Zoho Tasks with Subject, Status, Priority, Due Date, and Owner preserved. Task assignment migrates by resolving ChartMogul owner IDs to Zoho User emails. Completed tasks with no future action are omitted from the default migration scope to reduce import volume; the customer can elect to include them as Zoho Notes if historical activity tracking is required.

ChartMogul notes and call logs are unstructured text entries attached to customer records. We import them as Zoho Notes linked via ContentDocumentLink to the parent Contact (or Account). The note body migrates as-is. Call logs include timestamp and duration; we store these as custom fields on the Note record (call_duration__c, call_disposition__c) to preserve structured call data beyond the free-text body.