Migrate from Resco – Mobility & Productivity to Nutshell

Resco mirrors the underlying CRM Account entity directly. We migrate Account records 1:1 to Nutshell Company with all standard fields (name, address, phone, website) preserved. Company serves as the dedupe anchor for any subsequent Contact import. This mapping assumes the source Resco data is extracted from the underlying Dynamics 365, Dataverse, or Salesforce instance where the Account lives, not from Resco's offline cache.

Resco Contact records map to Nutshell Contact with email used as the dedupe key. First name, last name, phone, title, and address fields migrate directly. The Owner field from Resco maps to Nutshell's User assignment, resolved by email match against the Nutshell User table. Any Resco Contact without a matching Nutshell User goes to a reconciliation queue for manual assignment.

Work Orders are Resco's field-service transaction records and have no direct Nutshell equivalent. During scoping, we determine whether Work Orders should become Nutshell Deals (revenue-tracking service contracts or project-based work) or Cases (support tickets or issue tracking). We apply the customer's chosen conversion rule across all Work Order records, mapping status, assignment, line items, and any photos attached to the Work Order into Notes on the resulting Nutshell record.

Inspection Questionnaire definitions are Resco-specific artifacts configured in Woodford. We extract the questionnaire response data (field entries, checkboxes, signatures, attached photos) and migrate them as Notes on the related Account, Contact, or Work Order record. For recurring inspection templates, we recommend the customer evaluate Nutshell Custom Fields to capture key metrics post-migration. The questionnaire schema itself (logic branches, conditional fields) cannot migrate and must be rebuilt manually if needed in Nutshell.

Location tracking records in Resco's Mobile Auditing entity are stored with the Owner field set to the tracking user, not to the related asset or work order. These records have limited value in a standard sales CRM context. We preserve the most recent location entries as Notes on the related Contact or Account for audit purposes, but we flag that their primary value was operational (routing, asset GPS) and recommend the customer document the decision to exclude historical location history during scoping.

Route Plans in Resco are optimized sequences of work orders and inspections generated by the routing engine. These are configuration data rather than transactional CRM records and have no equivalent in Nutshell. We do not migrate Route Plans. During handoff, we deliver a written inventory of active route configurations so the customer's admin can evaluate whether Nutshell's Calendar and Tasks provide sufficient scheduling capability or whether a third-party routing tool is needed.

Custom entities created in Woodford that are not mirrored in the underlying CRM require explicit schema re-modeling. We assess each custom entity during discovery, determine whether it should become a set of Nutshell Custom Fields on Company or Contact, or whether it warrants a separate data store outside Nutshell. Custom entity relationships (lookup fields) cannot map to Nutshell's simpler schema and require the customer to define how the relationship should be represented post-migration.

Resco routes attachments to external storage (Dropbox, Google Drive, OneDrive, SharePoint) or stores them on the CRM server. We migrate attachments linked to CRM records as Nutshell Files attached to the relevant Company or Contact. For attachments routed to external services, we update the record to link the existing external file URL rather than re-uploading, maintaining the original storage location if the customer's Google Drive or SharePoint integration is active in Nutshell.

Activities sync through the standard Resco-to-CRM channel and migrate to Nutshell Activity records (calls, emails, meetings, tasks) with timestamps, assignments, and body content preserved. The Owner field resolves to Nutshell User by email match. Activity ordering is preserved by timestamp for the activity timeline.

Resco user records reference the underlying CRM user identity. We extract distinct users from Resco's user list and map them to Nutshell Users by email. Any Resco user without a matching Nutshell User account is flagged in the reconciliation report for the customer to provision before record migration begins, since OwnerId references are required on most Nutshell record types.