Migrate from Resco – Mobility & Productivity to Zoho CRM

Resco mirrors the parent CRM's Account entity directly, so the source records live in Dynamics 365, Dataverse, or Salesforce depending on the Resco configuration. We extract Account records from the underlying CRM API using the same field set and ownership that Resco syncs. The Account Name, Website, Industry, Phone, Billing Address, and OwnerId migrate 1:1 to Zoho's Accounts module. Owner resolution uses email-based matching against Zoho Users; any unresolved owners go to a reconciliation queue for the customer to provision before import continues.

Contact records sync through Resco's standard CRM integration channel. We extract from the parent CRM API with all standard fields (First Name, Last Name, Email, Phone, Title, Account Lookup) preserved. The Account lookup resolves to Zoho Accounts by Account Name or Website domain match before Contact import. Contact ownership migrates by email-to-Zoho-User lookup.

Work Orders are first-class entities in Resco's Field Service+ layer. We extract Work Order records from the parent CRM API including status, assignment, scheduled date, priority, line items, associated photos, and digital signatures captured in the field. We pre-create a Zoho custom module named 'Work Orders' with custom fields mapped by type (status values become picklists, dates become date fields, photo attachments migrate as Zoho file attachments). Work Order to Account and Contact lookups resolve at migration time via name or email match.

Inspection Questionnaires are two-part artifacts in Resco: the questionnaire definition (schema with logic branches, question types, and conditional paths) configured in Woodford, and the response records submitted by field technicians. The questionnaire definition does not migrate as configured code; we document its structure in a written specification so the customer's Zoho admin can recreate it using Zoho's custom module builder. Inspection response data migrates as records in a Zoho 'Inspections' custom module, with each question answered mapped to a multi-line text or appropriate field, and the parent Work Order lookup resolved at migration time.

Resco Mobile Auditing records store location history tied to the initiating user (Owner field = tracking user, not the record creator), not to work orders or assets. We migrate these records as a custom 'Location History' module or as Notes linked to the corresponding Contact record, depending on the customer's preference during scoping. Latitude, longitude, timestamp, and user are preserved as custom fields. The primary value of these records is audit-related; Zoho does not have a native location-tracking entity equivalent to Resco's Mobile Auditing.

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 are tied to the Resco routing algorithm's output format. We extract Route Plan metadata (assigned date, sequence order, associated work orders) as a custom Zoho module, but the optimized route geometry does not map directly because Zoho lacks a native routing engine. The customer decides whether to regenerate route sequences post-migration using Zoho's calendar and scheduling tools.

Custom entities created in Woodford are migrated as part of the Resco project export. Any entity not mirrored in Zoho requires pre-creation of a destination custom module with equivalent fields (text, number, date, picklist, lookup, boolean) before data import. Lookup relationships to standard entities (Account, Contact, Work Order) are resolved at migration time using name-based matching against the pre-imported parent records. Validation rules and required field constraints in Zoho must be temporarily relaxed during bulk import or set to allow migration-context bypass.

Resco routes documents and photos to external services (Dropbox, Google Drive, OneDrive, SharePoint) or stores them on the parent CRM server. We migrate attachments linked to CRM records as Zoho file attachments on the corresponding Account, Contact, Work Order, or Inspection record. For files stored in external services, we download from the source (SharePoint, OneDrive) and re-upload to Zoho CRM's native file storage, or flag them for the customer to re-link post-migration. Zoho's 5 GB file storage per user cap (Standard tier) or higher tiers should be confirmed against total attachment volume before migration.

User records in Resco reference the underlying CRM user identity. When extracting from the parent CRM, we map Owner references by email to Zoho User accounts. Any Owner without a matching Zoho User is flagged in a reconciliation report. The customer's Zoho admin provisions missing Users (active or inactive depending on whether the Resco user is still active) before record import resumes, because Zoho requires OwnerId on most standard modules.

Activities (calls, emails, meetings, tasks) sync through the standard Resco-to-CRM channel. We extract from the parent CRM API preserving activity type, subject, date, status, assigned user, and linked record references (AccountId, ContactId, WhatId for related-to). Zoho Activities map directly to Zoho's Tasks and Events module. The activity timeline ordering is preserved by setting the Zoho Activity date to the original CRM timestamp.