Migrate from MotionOps to Microsoft Dynamics 365 Sales

MotionOps Customer records hold both company and person contact data in a single object. We split on the presence of a company_name field: records with a company name map to Account with a child Contact; records without a company name map to a standalone Contact with AccountName set to the full name for reference.

MotionOps Job objects do not have a direct Dynamics 365 Sales equivalent. We map each Job to an Opportunity record using the job number as the Opportunity name, job status as a custom Opportunity Status field, and the associated customer as the Account lookup. Job line items map to Opportunity Product records via the Opportunity (OpportunityId) relationship.

MotionOps job statuses (e.g., Scheduled, In Progress, Completed, Cancelled) map to a custom pick-list field (MotionOps_JobStatus__c) on the Opportunity since Dynamics 365 Opportunity stage is already consumed by the sales pipeline stages. Status transition timestamps are preserved in a custom datetime field.

MotionOps Invoices generated from jobs are mapped to Dynamics 365 Invoice records with a linked Order record for the closed-won Opportunity. Invoice totals, tax amounts, and payment status use value mapping since MotionOps and Dynamics handle fiscal rounding differently. Partial payments stored as Payment records reference the parent Invoice.

MotionOps Proposals map directly to Dynamics 365 Sales Quote entities. Proposal line items map to Quote Details (quotedetail). Proposal expiration dates map to the Quote's ExpirationDate field. The Proposal's acceptance status determines whether the Quote is in draft or active state.

MotionOps users and technicians resolve by email match against Dynamics 365 SystemUser records. Email is the primary lookup key since both platforms use email as the user identifier. Unmatched users are flagged before migration; their records are assigned to a fallback owner or held for admin review.

MotionOps custom fields of type text, number, select, date, phone, email, and checkbox create corresponding custom columns in Dataverse. MultiSelect and RelatedTo fields require a custom table or connection entity in Dynamics 365. All custom fields must be provisioned in a Dataverse solution before data can be written via the Web API.

MotionOps schedule entries map to Dynamics 365 Appointment entities with the original start/end times and assigned technician as the OwnerId. If the Scheduling module is not in scope for Dynamics Field Service, appointments map to Tasks with a custom Schedule_Type__c field indicating the original MotionOps scheduling context.

MotionOps file attachments linked to jobs, proposals, or invoices are downloaded via the API and re-uploaded to Dynamics 365 as Notes (Annotation entities). If SharePoint integration is enabled in your Dynamics environment, files are stored in SharePoint with a reference link on the parent record, preserving the original filename and MIME type for downstream retrieval.

MotionOps workflow rules, scheduling automations, and payment-triggered actions have no direct equivalent in Dynamics 365 Sales core platform. FlitStack exports all workflow definitions as a structured JSON reference document your admin can use to rebuild equivalent flows in Power Automate, including trigger conditions, action sequences, and conditional branching logic extracted from the MotionOps configuration.

MotionOps payment records documenting partial or full payments against an invoice are stored as annotations on the Dynamics 365 Invoice record since Dynamics does not have a standalone Payment entity at the base CRM level. Payment method (card vs. ACH) and transaction IDs are preserved in custom fields on the annotation.

MotionOps company-level addresses and service-area information map directly to the Account entity's standard address fields (address1_line1, address1_city, address1_state, address1_postalcode, address1_country). When a customer has multiple service locations or branch offices, each additional location maps as a child Account record linked via the Parent Account lookup field, maintaining the hierarchical relationship from MotionOps.