Migrate from Resco – Mobility & Productivity to Salesforce Sales Cloud

Resco mirrors the underlying CRM's Account entity directly. We migrate Account records 1:1 with all standard fields intact — Account Name, Website, Industry, Billing Address, Phone, and Ownership. The dedupe key is the combination of Account Name and Website domain. Account is created before any related Contact or Work Order import so that the AccountId lookup is satisfied at insert time.

Contact records sync through the standard Resco-to-CRM channel. We preserve contact ownership, email, phone, mailing address, and the relationship link to the parent Account via AccountId lookup. The customer decides whether to maintain the Resco-specific contact photo (stored as an attachment) as a Salesforce custom field or as a ContentDocument linked via ContentDocumentLink.

Resco Work Orders are first-class entities in the Field Service+ layer and include status, assignment, line items, and photos captured in the field. We map Work Order to Salesforce WorkOrder if the destination org has Field Service Lightning licensed. If not, Work Orders map to Case with a custom field work_order_number__c and status mapped to Case Status. Work Order Line Items map to ServiceAppointment or WorkOrderLineItem depending on the Field Service schema in use.

Inspection questionnaire definitions configured in Woodford are Resco-specific artifacts. The questionnaire schema (question text, response type, branching logic) does not migrate automatically. We export the questionnaire definition separately from response data, map each question to a custom field on a Questionnaire custom object, and flag the branching logic for Salesforce Flow rebuild. The questionnaire response data migrates as records of the Questionnaire custom object.

Inspection response records (the filled-out answers, not the template) migrate to Salesforce custom object records linked to the parent Work Order or Account. Each response field maps to a typed Salesforce custom field (Text, Number, Picklist, Checkbox, Date). Photos and signatures captured in the inspection migrate as ContentDocument records linked via ContentDocumentLink to the parent inspection record.

Location tracking records in Resco are stored as Mobile Auditing entity entries where the Owner field is set to the initiating user, not to the work order or asset. This means location history is tied to user identity rather than operational context. We preserve these records by migrating them as Task records with custom fields location_latitude__c, location_longitude__c, and tracked_user__c. We flag that their primary value is audit and compliance rather than asset management, and the customer may choose to filter these records if volume is high.

Route plans are optimized sequences of work orders or inspections generated by Resco's routing engine. These are configuration data, not transactional records, and do not migrate as routing rules. We deliver a written map of the active route plan configurations (stop order, geographic sequence, time windows) and recommend Salesforce Field Service's Service Territory, Operating Hours, and Work Order scheduling approach as the re-modeling target. Route plan regeneration in Salesforce Field Service is an admin task post-migration.

Custom entities created in Woodford that are not mirrored in the destination Salesforce org require explicit schema re-creation. We pre-create the destination custom object with all custom fields, lookup relationships to Account, Contact, and Work Order, and validation rules before any data import. Custom object API names follow the Salesforce __c suffix convention. Any custom entity with a lookup dependency on another custom entity is migrated last after the dependency chain is validated.

Resco routes documents and photos to external services (Dropbox, Google Drive, OneDrive, SharePoint) or stores them on the CRM server. We migrate attachments linked to CRM records as Salesforce ContentDocument records attached via ContentDocumentLink. Standalone local files not yet routed to external storage require explicit export before migration. Documents originally stored in SharePoint migrate with their SharePoint URL preserved in a custom field for re-linkage post-migration.

Activities and calendar events sync through the standard CRM integration channel. We migrate Event records with Subject, StartDateTime, EndDateTime, Location, and WhoId (Contact or Lead lookup) preserved. Event attendance (attendee records) maps to EventRelation records linked to the corresponding Contacts and Users.

Task records migrate to Salesforce Task with Status, Priority, Subject, ActivityDate, and OwnerId resolved by matching the Resco user email to a Salesforce User record. Tasks assigned to Resco users without a Salesforce User counterpart go to a reconciliation queue for the customer's admin to provision before task migration resumes.

User records in Resco reference the underlying CRM user identity. When migrating from a Resco-connected Dynamics 365 or Dataverse org into Salesforce, user IDs and ownership assignments must be re-mapped to destination Salesforce User IDs. We resolve by email match. Any Resco user without a matching Salesforce User is held in a reconciliation queue. Ownership on Account, Contact, Work Order, and custom object records is updated to the resolved Salesforce OwnerId during migration.