Migrate from ServicePRO to Zoho Desk

ServicePRO Service Requests map to Zoho Desk Tickets. We extract standard fields (status, priority, category, assigned technician, created date, modified date) via the Service Request API and construct a migration-ready CSV matching Zoho Desk's assisted migration file format (Tickets_XX.csv). Custom form fields on ServicePRO tickets are mapped field-by-field to Zoho Desk custom fields, with ServicePRO's integer-encoded field type pairs decoded to Zoho Desk field types (text, numeric, date, checkbox, dropdown) during the transform phase. Dropdown option lists must be validated as identical between source and destination before finalizing import.

ServicePRO Employee records map to Zoho Desk Agents via email match as the dedupe key. We use ServicePRO's documented Employee API (GetEmployeeInfoByEmployeeId) to extract user profiles, department assignments, and role metadata, then format the output as Agents_XX.csv per Zoho Desk's assisted migration specification. Active and inactive status is preserved; the customer's Zoho Desk admin assigns Agent profiles and Department memberships during post-migration setup.

ServicePRO Asset records map to a Zoho Desk custom Assets module (available on Enterprise tier) or to Zoho CRM Assets if the customer uses Zoho CRM alongside Zoho Desk. We extract asset name, type, serial number, linked user, and any custom asset fields via ServicePRO's CSV export, then import into the destination Assets module. Asset-to-Ticket linking is preserved as a lookup field in the destination.

ServicePRO Target Categories are a hierarchical lookup structure used for categorizing vendors, customers, locations, and equipment types. Zoho Desk does not have a native Target Category equivalent. We map top-level Target Categories to Zoho Desk Tags for ticket classification, and map second-level Target Records to custom fields (dropdown or lookup) where the destination schema supports it. The customer validates dropdown option coverage during scoping.

ServicePRO Programs define service offerings and link to inventory items, branches, and events. We map Programs to Zoho Desk Products for items that appear in service billing, and map Program-linked events to Zoho Desk Tasks or a custom Events module depending on the destination tier. Program-to-ProgramEvent relationships are documented as a written reference for the customer's admin to configure in Zoho Desk.

ServicePRO System Email Accounts define sending and receiving addresses for ticket communications (Professional capped at 10, Enterprise unlimited). We export SMTP configurations from ServicePRO and provide a written configuration guide for Zoho Desk's Email setup, includingimap/pop fetch settings, SMTP relay, and department-level email routing. Email account mapping is a manual configuration step post-migration because destination email configs require authenticated setup in the Zoho Desk portal.

ServicePRO Contracts link customers, sites, and service agreements for fast relationship navigation. If the customer uses Zoho CRM alongside Zoho Desk, Contracts migrate as CRM Contracts linked to the Account. If the customer uses Zoho Desk standalone, Contract links migrate as a custom text or lookup field on the Account or Ticket. Contract-to-site relationships are preserved as address fields on the Account.

ServicePRO attachments linked to tickets, assets, and forms migrate to Zoho Desk Ticket Attachments. We extract binary attachment data via ServicePRO's API where accessible, then upload to Zoho Desk via the Attachment API endpoint. Large binary attachments (PDFs, images over 10MB) may require chunked upload handling. Knowledge Base article attachments are flagged as not migratable per Zoho Desk's documented exclusion.

ServicePRO Enterprise multi-Center configurations present a consolidation risk during migration. Each Service Center has its own ticket queues, users, and routing rules. We map each Service Center to a Zoho Desk Department during migration, but the customer must approve the Center-to-Department mapping before extraction begins because incorrect routing at this level redirects tickets to the wrong teams post-migration. Professional edition single-Center accounts migrate to a single Department.

ServicePRO Custom Forms define ticket intake layouts and capture structured data (Professional capped at 25 forms, Enterprise unlimited). We export form structure and field definitions from ServicePRO's metadata API, then map each custom field to a Zoho Desk custom field of equivalent type. Masked-entry fields (telephone, SSN, credit card) are flagged for PII handling and may be omitted from migration depending on the customer's data policy. The customer validates dropdown option lists are identical before finalizing.

ServicePRO Business Rules define automated routing, escalation, and notification logic. They have no documented API export endpoint and are therefore not migrated as automation code. We document every Business Rule discovered during the discovery phase in a written rules inventory with trigger conditions, actions, and a Zoho Desk Blueprint equivalence guide. The customer's admin rebuilds rules in Blueprint post-migration. This is explicitly out-of-scope for data migration and is delivered as a separate handoff document.

ServicePRO email templates do not export via API. We document template names, associated Business Rules, and field placeholders in a written inventory for the customer's admin to rebuild using Zoho Desk MACROs and Template Editor. This inventory is delivered alongside the Business Rules inventory as part of the standard migration handoff.