Migrate from Resco – Mobility & Productivity to Odoo CRM

Resco mirrors the parent CRM's Account entity directly. We extract Account records from the underlying Dynamics 365, Dataverse, or Salesforce via the Resco integration layer and map them to Odoo Contact records with the company_name field populated. Standard address fields (street, city, state, zip, country) transfer 1:1. If the parent CRM uses Account-Contact separation, we optionally create a separate Odoo Contact record for the company and child Contact records for individuals, depending on the customer's Odoo configuration preference.

Contact records migrate 1:1 to Odoo Contact. Name, email, phone, mobile, job title, department, and address fields transfer directly. We preserve contact ownership by resolving the Resco owner's email to an Odoo User record. Any Resco-specific contact properties not present in the destination CRM are stored as custom fields. Relationship links to Accounts are preserved via the company_name reference on the Odoo Contact record.

Resco Work Orders are first-class entities in the Field Service+ layer and map to Odoo Project Tasks within a dedicated Field Service project. We map Work Order status (Scheduled, In Progress, Completed, Cancelled) to Odoo Task stage values, assignment to Odoo User or Team, line items to Task descriptions or Subtasks, and field-captured photos to Odoo Documents attached to the Task. The Work Order's customer asset reference maps to an Odoo Contact or Product record depending on whether the asset is modeled as a Contact (customer asset) or Product (equipment catalog).

Resco inspection templates are Woodford-configured artifacts with conditional logic branches. We export the questionnaire definition as a structural document and map it to Odoo Survey questions. Because Woodford's branching logic uses JavaScript hooks and Resco-specific condition syntax, the Odoo Survey equivalent requires manual re-modeling by the customer's admin or a consultant. We deliver a written questionnaire inventory with each Woodford question mapped to an equivalent Odoo Survey question type, noting any conditional branching that must be manually rebuilt in Odoo Survey's conditional logic builder.

Individual inspection response records (completed questionnaires with filled answers, photos, and signatures) migrate to Odoo Survey Submission records linked to the parent Work Order Task. Response timestamps, user who completed the inspection, and photo attachments transfer. Conditional answer branches that determine follow-up questions are preserved in the response data even if the conditional logic itself cannot be migrated.

Location tracking records in Resco are stored in the Mobile Auditing entity with Owner set to the initiating user, not the record subject. GPS coordinates (latitude, longitude) and timestamp transfer to Odoo as custom fields on the related Task or Contact record, or into a dedicated Odoo project task used as an audit log. We flag during scoping whether the customer wants full location history preserved (high data volume) or a summary audit trail (low data volume). Route-level location history may need to be condensed to avoid migrating millions of individual GPS pings.

Resco Route Plans are optimized sequences of work orders or inspections generated by the Resco routing engine. These are configuration artifacts (scheduling preferences, optimized stop ordering) rather than transactional records and do not have a direct Odoo equivalent. We document each Route Plan's stop sequence, scheduling constraints, and vehicle assignments. The customer's Odoo Field Service administrator rebuilds these as Odoo planning shifts or scheduling rules. Route Plan regeneration is outside the data migration scope.

Custom entities created in Woodford are extracted from the parent CRM as part of the Resco project export. Any entity not mirrored in Odoo requires explicit schema re-creation. We assess each custom entity for Odoo equivalents: Odoo Studio custom fields, Odoo custom models (Python), or third-party Odoo Apps from the Odoo Store. We deliver a custom entity inventory document listing each Woodford entity, its field list, its relationships to standard entities, and a recommended Odoo modeling approach. Schema creation happens in the customer's Odoo instance before data import.

Resco routes documents and photos to the CRM server or to external services (Dropbox, Google Drive, OneDrive, SharePoint). We extract CRM-linked attachments directly from the parent CRM during migration. External storage attachments require explicit customer authorization to access the linked service. Photos captured in the field as Work Order attachments migrate as Odoo IrAttachment records linked to the corresponding Task. SharePoint-linked attachments migrate by re-uploading to Odoo Documents or by configuring an Odoo SharePoint integration if the customer maintains SharePoint post-migration.

Activities synced through the standard Resco-to-CRM channel migrate to Odoo Calendar Events (meetings, appointments) and Odoo Tasks (calls, to-dos). Calendar Event migrates with title, start datetime, end datetime, location, and attendee list. Call activities migrate as Tasks with a custom Call Duration field. Email activities migrate as Odoo Mail Message records linked to the Contact. We preserve activity timestamps and assignment to maintain the historical activity timeline in Odoo's CRM chatter and calendar views.

Resco user records reference the underlying CRM user identity. We match Resco users by email to Odoo User records. Any Resco user without a matching Odoo User is placed in a reconciliation queue for the customer's admin to provision before record import proceeds. Owner assignments on Contacts, Companies, Work Orders, and Activities are re-mapped to the resolved Odoo User IDs at migration time.

Resco Guides, the step-by-step workflow instruction component for field technicians, has been discontinued and has no migration path to Odoo or any other platform. We flag this during discovery and recommend that the customer document existing Guides content before migration. Replacement options include Odoo Knowledge (internal wiki), Odoo Discuss (for step-by-step instructions in tasks), or a standalone knowledge management tool. Guides content must be rebuilt as documentation; no automated migration is possible.