Migrate from BigChange to Microsoft Dynamics 365 Sales

BigChange Person maps directly to Dynamics 365 Contact. The Person's primary Company determines the AccountId lookup. Email, phone, and role fields map to Contact.Email, Contact.Phone, and Contact.JobTitle (or a custom Role__c field). During migration, Persons are imported after Companies so that AccountId lookups are available. Duplicate Persons (same email) are flagged for manual resolution before the Contact import proceeds.

BigChange Company maps to Dynamics 365 Account. Company name becomes Account.Name, domain becomes Account.Website, employee count and industry map as direct fields or via value mapping to Account.Industry pick-list. Parent/child company hierarchies map to Account.ParentAccountId. We preserve the original BigChange company_id in a custom Source_System_ID__c field for traceability and to support delta-run de-duplication during cutover.

BigChange Job is the central object — it contains operator, site, schedule, and outcome data. With Dynamics 365 Field Service licensed, Job maps to msdyn_workorder. Without Field Service, it maps to a custom Job__c table in Dataverse. Job status maps to msdyn_WorkOrder.StatusCode or custom status values.

The Person and Company linked to a Job determine the ContactId and AccountId on the destination record. We preserve the relationship by resolving Person to Contact by email match, then linking to Account via the Company-to-Account map. Jobs without a linked Person or Company are flagged in the pre-migration audit and assigned to an 'Unassigned Contact' placeholder record to maintain referential integrity in Dynamics 365.

BigChange Operator assignment maps to a Dynamics 365 BookableResource (if Field Service is licensed) via email-to-SystemUser resolution. ScheduleDateTime becomes the booking start/end time. Operator availability flags require Power Automate rebuild since they are not data records. Unmatched operators (no corresponding SystemUser in Dynamics 365) are logged and assigned to a fallback resource during migration to avoid orphaned WorkOrder records.

BigChange site/location data on a Job maps to msdyn_ServiceTerritory (Field Service) or as custom address fields on the Account record. Multi-site companies may need a custom Site__c table with latitude/longitude preserved as custom fields. Site records are imported before Jobs to ensure Territory lookups are available, and we validate that each site has a valid address before mapping to avoid null territory references on WorkOrder records.

BigChange Quote header fields (total, status, reference) map to Dynamics 365 Quote. Quote line items map to quotedetail with ProductId lookup, Quantity, and UnitPrice. Discount fields on line items map to ManualDiscountAmount on quotedetail. Quote status (Draft, Sent, Accepted) maps to StatusCode values.

BigChange Invoice maps to Dynamics 365 SalesInvoice. Invoice total, status (Issued, Paid, Overdue), and payment reference map to corresponding Invoice fields. Line items map to invoicedetail. The Invoice's linked Contact and Account are resolved via email match before migration. Any payment transactions or credit notes linked to the Invoice in BigChange are preserved as notes on the Dynamics 365 Invoice record for audit trail continuity.

BigChange file attachments on Jobs and Persons are downloaded and re-uploaded as Dynamics 365 Annotation records attached to the mapped Contact or WorkOrder. File size limits (Dynamics default 25MB per file) are respected. Inline images in notes are extracted and re-hosted as AnnotationBody.

BigChange custom job properties (type-aware: text, number, pick-list, date) become Dataverse custom fields with 'new_' prefix on the WorkOrder or custom Job__c table. Pick-list custom properties require value-by-value mapping to the new pick-list options defined in Dynamics before migration runs.

Custom properties on BigChange Persons map to new_* custom fields on Dynamics 365 Contact. Custom properties on Companies map to new_* fields on Account. Each custom field requires creation in Dynamics 365 before data lands, with type matching (string, integer, decimal, picklist) from BigChange's type definitions.

BigChange scheduling automations, job-triggered notifications, and workflow rules do not migrate. They must be rebuilt as Power Automate flows in Dynamics 365. We export BigChange workflow definitions as a structured reference document for your Dynamics admin to use during the rebuild phase.