Migrate from ServicePRO to Zendesk

ServicePRO Service Requests map directly to Zendesk Tickets. We map status, priority, category, assigned technician, created date, and resolved date. Custom form field values migrate as Zendesk custom ticket fields after field type alignment from ServicePRO's integer-encoded enumerated type system. Conversation threads (customer comments and technician notes) migrate as Zendesk Ticket Comments preserving the original timestamp and author attribution. The Service Center assignment maps to a Zendesk Group determined during the multi-Center consolidation phase.

ServicePRO technicians with system access map to Zendesk Agents. We extract via the Employee API endpoint (GetEmployeeInfoByEmployeeId) and map department and ServiceCenter assignments to Zendesk Group membership. The migration user provisioning uses Zendesk's REST API to create agents in Zendesk Groups corresponding to the source Service Center or department boundary. Technicians without system login credentials in ServicePRO map to End Users in Zendesk.

ServicePRO customers who submit Service Requests but do not have agent credentials map to Zendesk End Users. We extract customer records from the Target Records API (filtered by targettypeid for customer-type records) and map name, email, and address fields to Zendesk User. Multi-site customers with multiple location records generate multiple Zendesk User records or a single User with multiple Organization memberships depending on the customer's scoping choice.

ServicePRO asset records (asset name, type, serial number, and custom asset fields) migrate via ServicePRO's CSV Import Utility or REST API. In Zendesk without the Explore Asset Management add-on, asset records map to a custom ticket field (asset lookup) and/or an Organization-level custom field. With Explore, they map to the native Asset object. We align asset type and serial number to the selected Zendesk target field during schema design.

ServicePRO Target Categories are hierarchical lookup structures (GetTargetCategoryList, GetTargetCategoryByTargetCategoryId) that organize vendors, customers, locations, and equipment types. In Zendesk, we flatten these into a combination of Organization fields and custom ticket fields. The isRelated and UsedInSharedRef flags from the API determine whether a Category maps to an Organization-level custom field (for vendor/customer types) or a ticket-level custom field (for location/equipment types).

Individual Target Records within a Category (vendors, customers, locations, equipment) map to Zendesk Organizations (for vendor and company-type records) or Zendesk Users (for individual contact records). We deduplicate by name and email, resolving any multi-location Target Records to a single Organization with location data stored in a custom Organization field. Program and event links on Target Records are preserved as tags on the migrated Organization or User.

ServicePRO Programs define service offerings linked to inventory items, branches, and events. They have no direct Zendesk equivalent. We migrate Program associations as Zendesk Tags on the linked Ticket (tag format: program_<programname>) and/or as a custom ticket field of dropdown type listing the active Programs. Program-to-ProgramEvent links are preserved as additional tags. The customer selects the tag-versus-field strategy during scoping.

ServicePRO Custom Forms define ticket intake layouts with flexible field types (text, numeric, date, checkbox, dropdown, masked entry). Professional edition caps at 25 forms; Enterprise is unlimited. We export form structure and field definitions from the Setup API metadata, then create equivalent Zendesk custom ticket fields. The integer-encoded field type pair from ServicePRO's API maps to Zendesk's explicit field type selection. Masked-entry types (telephone, SSN, credit card) are flagged for PII handling and may be stored in a restricted-access custom field or excluded per customer policy.

ServicePRO System Email Accounts define sending and receiving addresses used in ticket communications. These do not migrate to Zendesk because Zendesk manages inbound email routing through its own Admin configuration (Support address, forwarding, email authentication). We document every System Email Account (SMTP settings, default reply address, shared mailbox assignments) in the migration handoff document. The customer's Zendesk admin configures Zendesk email routing post-migration using the documented source settings as a reference.

ServicePRO attachments linked to tickets, assets, and forms are extracted via REST API or direct database reference where accessible. Large binary attachments (PDFs, images over 1MB) are chunked for extraction to avoid timeout. We upload attachments as Zendesk Ticket Comment attachments via the Zendesk Attachments API, linking them to the correct ticket and preserving the original filename. Asset-linked attachments migrate as comments on the related ticket or as separate file records if the destination org uses Explore Asset Management.