Migrate from Resco – Mobility & Productivity to Microsoft Dynamics 365 Sales

Resco mirrors the parent CRM's Account entity directly through its sync channel. In a Resco-to-Microsoft Dynamics 365 Sales migration, Account records move 1:1 with all standard fields (name, address, industry, website, annual revenue) intact. We use Account as the parent record that must be created before Contact import to satisfy lookup dependencies. Any Resco Account-level custom fields sync from the underlying CRM layer are mapped to equivalent Dataverse columns on Account.

Contact records sync through the standard Resco-to-CRM channel and migrate 1:1 to Microsoft Dynamics 365 Sales Contact. We preserve contact ownership (transferred from the Resco-synced user ID to the Dynamics 365 User) and relationship links to Accounts. The Contact-to-Account lookup is resolved at migration time using the Account mapping as the parent reference.

Work orders are first-class entities in Resco's Field Service+ layer and may map to Dynamics 365 Field Service Work Order (if the customer licenses Field Service) or to a custom entity in Microsoft Dynamics 365 Sales . This decision is made during discovery: Field Service provides a native Work Order schema with status, assignment, line items, and product usage; if Field Service is not licensed, we design a custom Dataverse Work Order table and replicate the schema. Work order photos captured in the field migrate as note attachments linked to the Work Order record.

Resco inspection templates are Woodford-configured artifacts with branching logic and response schemas. These do not have a native Microsoft Dynamics 365 Sales equivalent. We export the questionnaire definition (question text, response types, conditional branching) and deliver a written specification for rebuilding as Dynamics Forms or Power Apps canvas apps. The inspection response data (completed questionnaire records) migrates as custom Dataverse records linked to the parent entity (Work Order, Account, or Contact) with a flattened response field structure.

Completed inspection response records migrate to a custom Dataverse table created to mirror the Resco questionnaire schema. Each response is linked to the parent Work Order or Account. We map numeric responses to Decimal fields, pass/fail to Boolean, photo captures to Image fields (stored as attachments), and free-text responses to Text fields. Conditional branching logic from the questionnaire definition is not migratable; we document it for the Power Apps rebuild.

Location tracking records in Resco are stored as Mobile Auditing entity entries where the Owner field is set to the user who initiated tracking, not to the work order or asset being tracked. This is a key data-model difference: Resco location history is user-centric, not asset-centric. We migrate these records to a custom Dataverse table (or the customer's existing audit log entity) with the Owner preserved and the gps_coordinates mapped to custom Decimal fields. We flag during scoping that the value of these records is primarily audit-related and may require re-segmentation by the customer post-migration.

Resco Route Plans are optimized sequences of work orders and inspections generated by the routing engine. These are runtime configuration data that reference current Work Order IDs and scheduling windows. They are not migratable as static records because the referenced Work Order IDs will change in the destination environment. We deliver a written map of the route optimization criteria (distance, time windows, technician skill matching) so the customer's admin can regenerate routes in the destination using Dynamics 365 Resource Scheduling Optimization or Power Automate.

Custom entities created in Woodford are exported as part of the Resco project data and mapped to custom Dataverse tables in Microsoft Dynamics 365 Sales . We pre-create the destination schema including all custom fields, lookup relationships to standard entities (Account, Contact, Work Order), and field types mapped from Resco to Dataverse equivalents. Any custom entity not mirrored in the destination requires explicit schema design during discovery; we flag these as re-modeling decisions before migration begins.

Documents and photos captured in Resco are stored on the CRM server or routed to external services (Dropbox, Google Drive, OneDrive, SharePoint). We migrate attachments linked to CRM records as SharePoint document locations (if the destination uses SharePoint integration) or as CRM note attachments. Standalone local files that Resco stored without a CRM link require explicit customer decision on routing. We verify the destination's SharePoint integration is active before migrating document libraries.

Activities sync through the standard CRM integration channel and migrate to Microsoft Dynamics 365 Sales Activity entities. Call logs map to Task with TaskSubtype=Call; emails map to Email; meetings and appointments map to Appointment (Event). We preserve activity timestamps, assignments, status, and description fields. The Activity-to-Contact and Activity-to-Account lookups are resolved at migration time using the Contact and Account mapping tables.