Migrate from Orderry to Microsoft Dynamics 365 Sales

Orderry clients map directly to Dynamics 365 Accounts. The client's primary address becomes Account.Address1; secondary address becomes Address2. Multi-location clients with separate Orderry location records become child Accounts under the parent Account using ParentAccountId lookup to maintain hierarchical relationships.

Named contacts within an Orderry client map to Dynamics 365 Contacts linked via AccountId lookup. Primary contact flag from Orderry becomes the Primary Contact lookup on the Account. All contact phone numbers, emails, and job titles migrate to Contact fields directly.

Orderry work orders serve two purposes — pipeline tracking (job status, revenue) and service history. We map revenue-bearing work orders to Opportunities (using estimated amount and stage from status). Pure service/repair work orders with no revenue map to Incidents (Cases) for historical record. The routing decision uses Orderry's work order type field and presence of line items.

Orderry work order status values (New, In Progress, On Hold, Completed, Cancelled) map to corresponding Opportunity StageName values in Dynamics 365. Each stage has a probability and forecast category applied from Dynamics 365 defaults. We preserve the original status-transition timestamps as custom datetime fields.

Work order line items in Orderry (products used, services rendered, labor hours) map to OpportunityProduct records — the junction between Opportunity and Product. Quantity, unit price, and manual discount all migrate. If the product does not yet exist in D365 Sales, we create the Product record first before linking.

Orderry estimates map to Dynamics 365 Quotes with all associated line items and values. Quote status (Draft, Active, Accepted, Revised, Closed) migrates directly to D365 Sales Quote StateCode and StatusCode. The Quote Detail records carry the same line items as the OpportunityProduct structure. Original estimate date becomes the Quote's EffectiveFrom date.

Orderry products with stock levels, SKU, unit cost, and unit price map to Dynamics 365 Product records. The product's Name, SKU/Product Number, Standard Price (Cost), and Current Cost migrate. Note that D365 Sales does not natively track on-hand inventory — stock levels and warehouses require Field Service or Business Central integration and are surfaced as informational fields only.

Orderry warehouse stock levels per product per location have no direct D365 Sales equivalent. We create a custom location identifier field on the Product record and store per-location quantity as a serialized JSON custom field or separate custom inventory table. This is for reference only — actual inventory tracking requires a separate Field Service module.

Orderry employees resolve to Dynamics 365 users by email address. Unmatched employees are flagged before migration — your admin either invites them to D365 Sales first or assigns their work orders to a fallback owner (UserId). Orderry employee roles map to Dynamics 365 Security Roles assigned post-migration.

Orderry invoice records map to Dynamics 365 Invoice entities. Payment status and payment method from Orderry migrate to the Invoice's payment terms and status fields. Actual payment transactions (Stripe, Square) are external — those integrations must be rebuilt in D365 Sales via Payment Services or a connector.

Orderry custom fields per entity map to new_ prefix custom columns in Dataverse. Text, number, date, and pick-list field types translate directly. Multi-select pick-lists in Orderry map to option-set fields in D365 Sales. Custom fields are created in a Dataverse solution before data migration runs so fields are available during field mapping.

Orderry file attachments on work orders, clients, or products migrate to Dynamics 365 Notes with a Regarding lookup pointing to the target record. If your D365 Sales environment uses SharePoint for document management, we re-upload files to the corresponding SharePoint Document Location and link them via the entity's primary record.