Migrate from ChartMogul to Microsoft Dynamics 365 Sales

ChartMogul parent Customer records decompose into both an Account and a Contact in Microsoft Dynamics 365 Sales . The Customer name becomes the Account Name, and a primary Contact record is created with the same name and email. We preserve the ChartMogul customer_id as an external_id field on both Account and Contact for lookup resolution during subsequent imports. Tags migrate to a multi-select picklist or a custom Tags field on Account. Custom attributes migrate as typed custom fields on Account or Contact based on attribute type during schema design.

Each ChartMogul Data Source Customer (Stripe, Chargebee, Recurly) is a billing-system-specific child record with no direct Microsoft Dynamics 365 Sales equivalent. We create a custom SubscriptionSource entity in Dataverse to hold the data source reference, customer ID in the billing system, and a lookup to the parent Account. If the customer also runs Business Central, we coordinate the Account GUID so that the custom entity can be joined to the Business Central Customer table.

ChartMogul Opportunities map directly to Microsoft Dynamics 365 Sales Opportunities. The opportunity amount becomes EstimatedRevenue, stage maps to a configured Sales Process stage name, and close date migrates as CloseDate. We create the Sales Process and Record Type in Dynamics before migration so that stage values are whitelisted and probability percentages are set per stage. Owner resolution uses email matching to the Dynamics User table.

ChartMogul Subscriptions (plan_id, quantity, billing cycle, status, MRR contribution) have no standard Microsoft Dynamics 365 Sales equivalent. We create a custom Subscription entity in Dataverse with fields for PlanName, Quantity, BillingCycle, Status, MRR, and a lookup to the parent Account. The entity is deployed via Dataverse API before any subscription data is imported. If the customer also licenses Business Central, we map the custom Subscription entity to the Business Central Subscription table via a Power Automate flow.

ChartMogul Plan definitions (name, interval, amount, currency, trial period) are billing metadata. We create a custom Plan entity in Dataverse to store these records with fields for PlanName, Interval, Amount, Currency, and TrialPeriodDays. This entity is populated during migration and maintained by the customer's admin going forward. If the customer uses Business Central for product and pricing management, Plan records can be reconciled with Business Central Items post-migration.

ChartMogul Invoices (line items, amounts, taxes, transaction fees) are billing records without a standard Microsoft Dynamics 365 Sales equivalent. We create a custom Invoice entity in Dataverse with fields for InvoiceNumber, InvoiceDate, TotalAmount, TaxAmount, Status, and a lookup to the parent Account. Invoice line items store as a related custom InvoiceLine entity. The customer can attach PDF copies of invoices as Notes or SharePoint document library files linked to the Invoice record.

ChartMogul Transactions (payments, refunds, chargebacks) are mapped to a custom Transaction entity in Dataverse with Type, Amount, Date, PaymentMethod, and a lookup to the parent Invoice record. Transaction fee handling from ChartMogul's billing source configuration (particularly for Google Play and PayPal) is preserved as a custom FeeAmount field so that the net revenue calculation can be reconstructed if needed.

ChartMogul tags on parent Customer records migrate to a multi-select picklist field on the Account. The picklist values are populated from the distinct set of tags in the source data during scoping. If the tag cardinality exceeds the Dynamics multi-select picklist limit of 500 values, we create a custom Tags entity with a many-to-many relationship to Account instead.

ChartMogul customer-level custom attributes are key-value pairs set via API or CRM sync. We map each attribute to a typed custom field on the Account or Contact entity based on data type: string attributes become text fields, numeric attributes become decimal or integer fields, boolean attributes become checkbox fields, and date attributes become date fields. We validate field types during schema design and create the custom fields in Dataverse before migration.

ChartMogul Tasks on Customer records migrate to Microsoft Dynamics 365 Sales Tasks with Subject, Description, Status, Priority, and DueDate preserved. Task assignment resolves ChartMogul owner_id to Dynamics User ID via email matching. Open tasks migrate; completed tasks with no future action are optionally omitted to reduce import volume.

ChartMogul Notes and Call Logs are unstructured text on Customer records. We import them as Dynamics 365 Notes linked via the Regarding field to the corresponding Account. Call-specific fields (call disposition, duration) migrate to custom Note extension fields if present in ChartMogul.

ChartMogul Owners (user records tied to customers, opportunities, and tasks) map to Microsoft Dynamics 365 Sales User records. We resolve owners by email match. Any ChartMogul Owner without a matching Dynamics User is placed in a reconciliation queue for the customer's admin to provision before record import resumes.