Migrate from Maple CRM to Microsoft Dynamics 365 Sales

Maple CRM Client records map to Salesforce-style Contact attached to an Account. The Account is created from the Client record (using firm/organization name as Account Name) before Contact migration so that AccountId is available at Contact insert time. Individual applicant clients without a firm organization map to an Account named after the client's full name. Nationality, passport data, and address fields map to Contact standard fields or custom fields on Contact.

Maple CRM Cases map to Microsoft Dynamics 365 Sales Opportunity. The Case stage progression (Application, Review, Submission, Approval, Denial/Appeal) maps to a configured Sales Process with matching stage values. We pre-create the Sales Process and its stage whitelist during schema setup, then map each Maple Case stage string to the corresponding Dynamics stage name and probability percentage. ClientId on Case resolves to ContactId on Opportunity at migration time.

Maple CRM Documents attached to Cases or Clients migrate as Dynamics 365 Notes with file attachments. Document type (passport, proof of funds, visa application) maps to a custom Note field or tag; upload timestamp maps to CreatedOn. If the destination org uses SharePoint integrated document management, we map Documents to SharePoint locations tied to the Contact or Opportunity record, preserving folder structure where the source exposes it.

Maple CRM Lead records with intake form data from initial inquiry map directly to Dynamics 365 Lead. Jurisdiction-specific intake fields (IRCC-relevant fields for Canada) map to custom Lead fields; jurisdiction labels and validations are not preserved and must be reconfigured as field validation rules in Dynamics post-migration. Lead source and assigned executive map to standard Lead fields.

Maple CRM Quotation Builder records map to Dynamics 365 Quote. Line items, pricing, and status migrate as QuoteLineItems. The Quote PDF itself is not migrated; only the underlying data record transfers. Quote status (Draft, Sent, Accepted, Lost) maps to the Dynamics Quote status field. If the customer uses the Opportunity-linked Quote pattern, we associate Quote to the Opportunity resolved from the original Quotation context.

Maple CRM Invoice records with line items, amounts, payment terms, and outstanding balance map to Microsoft Dynamics 365 Sales Order. If the destination org has Finance modules or uses the Invoice entity in Service Cloud, we map to Invoice instead. Historical paid invoices retain their paid status; outstanding balance and payment due date migrate as Order or Invoice fields. We do not migrate payment gateway transaction records.

Maple CRM Agreement records linked to Clients migrate as Dynamics 365 Contract records. Service terms, renewal dates, and pricing map to Contract fields (Contract Term, Start Date, End Date, Annual Invoice Amount). Renewal scheduling must be reconstructed as a Power Automate flow or Dynamics workflow post-migration. Note: agreement template definitions are not API-exportable; we migrate rendered agreement records and document the template structure for manual rebuild.

Maple CRM Support Request records migrate to Microsoft Dynamics 365 Sales Case (or Customer Service Case if Service Cloud is in scope). Status, priority, assignee, and timestamps migrate directly. TAT tracking data and escalation SLA rules are platform-specific configurations that cannot be exported; we document the existing SLA tiers and escalation queue structure so the customer's admin can rebuild entitlement processes and SLA definitions in Dynamics 365 Service.

Maple CRM user accounts with role-based access control export with role and team assignment. We match users by email against the destination Dynamics 365 org's User table. Any Maple CRM user without a matching Dynamics User goes to a reconciliation queue for the customer's admin to provision before record migration resumes. HR data (compensation, PTO) is not stored in Maple CRM and does not migrate.