Migrate from Resco – Mobility & Productivity to Freshsales

Resco mirrors the parent CRM's Account entity directly. We extract Account records from the underlying Dynamics 365, Dataverse, or Salesforce instance and write them to Freshsales Account. The parent CRM's Account identifier is preserved in a custom field original_account_id__c for audit reconciliation. Account is the first object migrated so that Contact and Deal records can satisfy their AccountId lookups on insert.

Contact records from the underlying CRM migrate to Freshsales Contact. Ownership assignments migrate by email-match against Freshsales Users. Any Contact without a matching User goes to a reconciliation queue for the admin to provision before Contact import resumes. Relationship links to Account (via AccountId) are preserved using the original Account ID cross-referenced through the Account mapping.

Work Orders are first-class Resco Field Service+ entities with no direct Freshsales equivalent. We assess the Work Order's primary purpose at migration time: field-service records with asset linkage and status workflows migrate to Freshsales Case (via the Cases module) with custom fields for asset name, work order type, and resolution notes; commercial Work Orders tied to revenue recognition migrate to Freshsales Deal with a custom Work_Order_Number__c field. The customer chooses the split strategy during scoping. We do not migrate work-order-specific form logic or status transition rules.

Work Order line items migrate to Freshsales Deal Products attached to the target Deal (for commercial splits). Each line item's product name, quantity, and unit cost migrate as a line item entry. Freshsales requires the associated Deal to exist before line items are inserted; we sequence accordingly.

Inspection templates configured in Woodford are Resco-specific artifacts with schema and conditional branching logic that has no Freshsales equivalent. We export the questionnaire definition (question text, response types, conditional logic) as a structured JSON document and deliver it as a written artifact. The customer's admin can use Freshsales' custom object builder to recreate the form as a custom object with conditional field visibility, or they can adopt a dedicated inspection tool. Completed inspection responses migrate as custom object records linked to the parent Contact or Account.

Location tracking records in Resco are stored in the Mobile Auditing entity with the Owner field set to the initiating user, not to the work order or asset. These records have limited Freshsales analog. We migrate Mobile Auditing entries as Freshsales Tasks with a custom field location_data__c storing the GPS coordinates and timestamp, linked to the originating Contact or Account. The audit context is preserved but the records do not map to a dedicated location entity in Freshsales.

Route Plans in Resco are optimized sequences of work orders or inspections generated by the routing engine. They are configuration data rather than transactional records and do not have a direct Freshsales equivalent. We export route plan definitions (sequence, scheduled date, assigned user, and linked work orders) as a structured JSON artifact for the customer's admin to review. Route plan regeneration is recommended post-migration using Freshsales Tasks with a custom route_plan__c lookup, or a dedicated routing add-on.

Custom entities created in Woodford that are not mirrored in Freshsales require explicit schema re-creation. We pre-create the destination custom object in Freshsales (with API name matching the original entity name with _c suffix), define all custom fields with appropriate Freshsales field types, and configure lookup relationships to standard objects (Account, Contact, Deal) before data import. Any custom entity that references a Resco-only entity with no Freshsales target is flagged during scoping and held for a re-modeling decision before migration.

Resco documents and photos are stored on the CRM server or routed to external services (Dropbox, Google Drive, OneDrive, SharePoint). We migrate attachments linked to CRM records as Freshsales Notes with the file content stored as an attachment or linked via URL. Standalone local files not linked to a CRM record require explicit customer instruction on routing. External storage references are preserved as URL fields pointing to the original storage location.

Activities sync through the standard CRM integration channel. We migrate activity records (calls, emails, meetings, tasks) from the underlying CRM to Freshsales Tasks and Events, preserving assignments, status, and timestamps. Activity timeline ordering is preserved by setting the original timestamp on the Freshsales record. Calls map to Tasks with TaskSubtype=Call and call duration preserved in a custom field.