Migrate from ChartMogul to Pipedrive

ChartMogul's parent Customer record carries CRM data: name, email, tags, custom attributes, notes, call logs, opportunities, and tasks. We migrate this to a Pipedrive Person record using ChartMogul's customer UUID as the external_id on the Person. ChartMogul's tags migrate as Pipedrive custom text fields or as activity tags depending on customer preference. Custom attributes from ChartMogul map to Pipedrive custom fields using the attribute key as the field name.

ChartMogul's child Data Source Customer records hold billing data linked to the parent via external_id. For teams using a single billing source, the child data source customer maps to the same Pipedrive Person created from the parent record. For teams using multiple billing sources (Stripe plus Chargebee, for example), the billing identifiers and transaction counts go into custom fields on the Person record. Organizations are created from ChartMogul Company data when present; otherwise the Person holds the organizational context in custom fields.

ChartMogul Subscriptions contain plan_id, quantity, billing interval, MRR contribution, and status (active, trialing, cancelled). We capture these in Pipedrive custom fields on the Person record: cm_subscription_status, cm_plan_name, cm_billing_interval, cm_mrr_contribution, cm_quantity. Pipedrive does not have a native subscriptions object, so this data lives as attributes on the Person. For subscription-linked deals, a Deal record is created with the MRR value in the deal value field.

ChartMogul Invoices contain line items, amounts, taxes, transaction fees, and payment dates. We import the full invoice history as Pipedrive Activities of type 'note' with a standardized invoice summary body, and key fields (invoice_number, total_amount, currency, payment_status) migrate to custom fields on the related Person. Transaction fee details are preserved in the note body since Pipedrive custom field types are limited.

Payments, refunds, and chargebacks from ChartMogul map to custom fields on the Person record. Transaction type (payment, refund, chargeback) and the net amount after fees go into cm_last_transaction_type and cm_last_transaction_net fields. For full transaction history, we maintain a structured note per transaction on the Person. The transaction fee handling setting (Google Play and PayPal deduct fees automatically) is preserved as a flag on the Person record so the customer's finance team can account for it in any MRR reconstruction.

ChartMogul Plan definitions (name, interval, amount, currency, trial period) map to Pipedrive Products. The ChartMogul plan_id becomes the Pipedrive Product code. If the customer uses Pipedrive Deals linked to Products (Advanced tier and above), the deal line items can reference these Products. Plan change history over time is preserved as structured notes on the Person record rather than as versioned Product records.

ChartMogul Opportunities track deal stage and value. These map directly to Pipedrive Deals with the deal name, value, stage, owner, and expected close date preserved. ChartMogul's opportunity stages map to Pipedrive pipeline stages that we configure during schema setup. Closed-won and closed-lost statuses translate to Pipedrive deal statuses. Any ChartMogul opportunity linked to a subscription is linked in Pipedrive to the same Person that carries the subscription custom fields.

ChartMogul Tasks with due dates, assignees, and completion status migrate to Pipedrive Activities of type 'task'. Open tasks migrate fully; completed tasks with no pending follow-up are optionally omitted to reduce import volume and stay within Pipedrive's action limits on mid-tier plans. Task assignees are resolved by email match against Pipedrive Users.

ChartMogul Notes migrate as Pipedrive Activities of type 'note' linked to the Person record. Call logs migrate as Pipedrive Activities of type 'call' with call duration and disposition stored in custom fields on the Activity. ChartMogul's rich text formatting normalizes to plain text with line breaks preserved. Call recording URLs from ChartMogul are stored as a text field on the Activity record for reference.

Customer-level custom attributes from ChartMogul migrate as key-value pairs to Pipedrive custom fields on the Person record. We use the ChartMogul attribute key as the Pipedrive field name with the closest matching field type (text, number, date, dropdown). Attributes that contain multi-value data (arrays, JSON) are stored as text fields with the original value preserved. Pipedrive custom fields are configured in the destination account before migration.

ChartMogul tags are flat string labels on parent customer records. We migrate them as a comma-separated string in a Pipedrive custom text field (cm_tags). The customer can alternatively choose to create individual Pipedrive Activities per tag for more granular filtering, but the flat-field approach preserves tag counts for segmentation and is simpler to migrate without data expansion.

ChartMogul calculates MRR movements (new business, expansion, contraction, churn) from subscription state changes. These calculated metrics have no Pipedrive equivalent and do not migrate. We preserve the MRR source data (current MRR per customer, billing interval, plan) in custom fields so that the customer can rebuild MRR calculations in a BI tool post-migration. This is documented as a gap in the migration handoff and is not considered data loss because the metrics are derived, not raw, data.