Migrate from Resco – Mobility & Productivity to Pipedrive

Resco mirrors the parent CRM's Account entity directly. We extract Account records from the underlying Dynamics 365, Dataverse, or Salesforce instance and map them to Pipedrive Organization records 1:1. The Organization's address, phone, domain, and industry fields carry over from the corresponding Account fields. We use the organization's primary email domain as a deduplication key during import to flag duplicates in the Pipedrive destination.

Resco Contact records sync through the standard parent CRM channel and map to Pipedrive Person records with a 1:1 relationship. Contact ownership, email, phone, title, and the link to the parent Account (which becomes the Person's linked Organization) are preserved. We resolve the Organization lookup at migration time so that Persons are linked to Organizations on insert rather than requiring a post-migration linkage pass.

Resco Work Orders (from the Field Service+ layer) have no direct Pipedrive equivalent — Pipedrive has no work order or field service object. We map Work Order records to Pipedrive Deals and use custom Deal fields to carry work order attributes: work_order_number becomes a text custom field, status maps to a deal stage or custom picklist, assigned technician maps to the Deal owner, and work order line items become Deal Product entries or Activity-linked notes. Customers choose during scoping whether to use Deals as work order proxies or to archive closed work orders as historical records.

Resco Work Order Line Items map to Pipedrive Deal Products attached to the corresponding Deal (sourced from the parent Work Order). Product name, quantity, unit price, and line item status transfer to the Deal's product entries. If a Resco work order has no associated product catalog (service-only work orders), we create the line items as Activity notes instead.

Inspection questionnaire definitions configured in Woodford are Resco-specific artifacts with conditional branching logic that has no Pipedrive equivalent. We export the questionnaire schema separately from response data and deliver it as a structured document for the customer's admin to rebuild using Pipedrive's custom fields and activity notes. Completed inspection responses (the data) migrate as Activity records linked to the parent Deal or Organization with a structured note body capturing the response tree.

Resco Mobile Auditing records store location history as entity entries where the Owner field is the tracking user, not the asset or work order. These records are audit artifacts rather than sales CRM data. We preserve location records as Activity entries on the corresponding User's timeline or as a linked Note on the relevant Work Order/Deal, with GPS coordinates, timestamp, and user identity captured in custom Activity fields. Customers who do not need audit-trail location history can elect to exclude these records to reduce migration volume.

Route plans are optimized sequences of work orders and inspections generated by Resco's routing engine. These are configuration data produced by a proprietary optimization algorithm and have no equivalent in Pipedrive. We document every route plan as a written inventory (route name, stop sequence, associated work orders, geographic waypoints) and recommend rebuilding using a routing optimization tool or manually reconstructing in Pipedrive's Activity sequence. Route plan data itself does not transfer as executable configuration.

Custom entities created in Woodford that are mirrored in the underlying CRM migrate as Pipedrive custom fields on the matching standard object. Any custom entity not mirrored in the destination CRM requires explicit schema re-creation: we pre-create Pipedrive custom fields with the correct data type (text, number, date, picklist, person, organization) before data import, and the customer's admin validates the field structure against the original Woodford entity definition delivered in the discovery export.

Resco routes documents and photos to external storage (Dropbox, Google Drive, OneDrive, SharePoint) or stores them on the CRM server. We migrate CRM-linked attachments as Pipedrive Files attached to the corresponding Person, Organization, or Deal. Files stored externally in Resco's connected cloud services are inventoried with their source URLs; if the customer uses the same external storage provider, we preserve the link. Files stored only locally in Resco require explicit export before the migration window closes.

Activities (calls, emails, meetings, tasks) sync through the standard CRM integration channel and map 1:1 to Pipedrive Activities. Meeting location, start and end time, assigned user, and linked Organization or Person transfer directly. Call disposition, duration, and outcome map to custom Activity fields or to the standard outcome picklist. Activity timestamps are preserved to maintain the historical timeline.

Resco user records reference the underlying CRM user identity. We resolve users by email match against the Pipedrive destination User table. Any Resco user without a matching Pipedrive User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Active/inactive status and role assignments are preserved as documented in the discovery export.

Products synced from the underlying CRM to Resco map to Pipedrive Product records. We preserve product name, SKU (product_code), unit price, and any product description. If the parent CRM was Salesforce, the Pricebook2 structure maps to Pipedrive's product pricing model, with the customer choosing whether to use standard pricing or multi-tier pricing.