Migrate from Method CRM to Microsoft Dynamics 365 Sales

Method CRM Contact records split by qualification status into Salesforce Lead or Contact. We use Method's contact status and assigned owner properties to apply a split rule designed during scoping. Contacts from active sales relationships map to Dynamics 365 Contact tied to an Account. Unqualified or cold contacts map to Lead. The original Method Contact record ID migrates into a custom field mth_contact_id__c on both Lead and Contact for audit traceability. If the customer used Method's QuickBooks customer link, the QB entity reference is preserved in a custom field qb_customer_ref__c for accounting reconciliation.

Method CRM Company records map 1:1 to Microsoft Dynamics 365 Sales Account. Company Name becomes Account Name, and the primary address maps to the billing address fields. Company is created before Contact insert so that the AccountId lookup is satisfied at the moment of Contact write. If a Method Company has no associated Contacts, it still migrates as an Account with no Contact child records.

Method CRM Opportunities map to Microsoft Dynamics 365 Sales Opportunity. The stage field from Method maps to a Microsoft Dynamics 365 Sales Process (Record Type) that we configure before migration. Close date, estimated amount, and probability migrate directly. OwnerId is resolved via email match against the Dynamics 365 User table during the Owner reconciliation phase. Closed-won and closed-lost reasons from Method become custom Opportunity fields for loss analysis.

Method CRM call activities map to Dynamics 365 Task with TaskSubtype set to Call. Call disposition, duration in seconds, and any recording URL stored in custom Task fields. ActivityDate preserves the original Method timestamp for timeline ordering. The WhoId (Contact or Lead reference) and WhatId (Opportunity reference) are resolved via the mth_contact_id__c and mth_opportunity_id__c lookup fields created during the parent record migration phase.

Method CRM email activities migrate as Dynamics 365 EmailMessage records (the email content and headers) linked to an Activity Task record (the timeline entry). The email direction (inbound/outbound) maps from Method's activity type field. Attachments are extracted as ContentDocument records and linked via ContentDocumentLink. We set the Regarding (WhatId) to the parent Opportunity or Account using the lookup fields established on the Contact migration.

Method CRM meeting activities map to Dynamics 365 Event with StartDateTime and EndDateTime preserved from the Method timestamp. Location migrates to the Event Location field. Attendees are mapped to EventRelation records linked to the corresponding Contact, Lead, or User records.

Method CRM task activities migrate to Dynamics 365 Task with Status, Priority, Subject, and ActivityDate preserved. Owner assignment migrates by resolving the Method owner email to Dynamics 365 UserId via the User mapping table built during Owner reconciliation.

Method CRM Note activities migrate to Dynamics 365 Note records linked via ContentDocumentLink to the parent Contact, Lead, Account, or Opportunity. Rich text formatting in Method notes is preserved as HTML body content in the Note. File attachments within notes migrate as separate ContentDocument records.

Method CRM Estimates are QuickBooks-synced transactional documents with line items, totals, and status. Microsoft Dynamics 365 Sales does not have a native Estimates object. We evaluate two paths: (1) if the customer licenses Microsoft Dynamics 365 Sales Professional, we map Estimates to Quote records with a flag indicating QB origin; (2) if transactional fidelity is required, we design a Dataverse custom table (Estimates) with line items, totals, and status fields matching the Method schema, then link it to the parent Account or Contact via lookup. QuickBooks linkage metadata is preserved in a custom field for accounting reconciliation. Customers needing full transactional history should evaluate a parallel Business Central scope.

Method CRM Invoices are QuickBooks-synced transactional records with payment status and line items. Microsoft Dynamics 365 Sales has no native Invoice object. If the customer does not have Business Central, we create a Dataverse Invoice table with invoice number, date, amount, balance due, and payment status fields matching the Method schema, linked to the Account via lookup. QB linkage metadata is preserved in a custom field. Invoices with payment data should be considered for a Business Central scope addition if accounting-level detail is required.

Method CRM custom fields on Contacts, Companies, Opportunities, and Activities vary by account configuration. We inventory every custom field name and data type during scoping, then pre-create matching custom fields in Dynamics 365 using the appropriate Dataverse field type (text, integer, decimal, datetime, picklist, bit). Custom field values migrate as flat field writes during the parent object migration phase.

Method CRM file attachments (binary content via REST API Files endpoints) migrate to Microsoft Dynamics 365 Sales as ContentDocument records stored in SharePoint Online. We create a SharePoint document library linked to the Dynamics 365 organization, then create ContentDocument records with the binary content and ContentDocumentLink records connecting each file to the parent Contact, Account, or Opportunity. File metadata (name, size, created date, created by) migrates from the Method API response.