Migrate from ServicePRO to Freshdesk

ServicePRO Service Requests map to Freshdesk Tickets. Standard fields (status, priority, category, assigned technician) have direct equivalents in Freshdesk. Custom form fields require field-type decoding from the integer pair in the ServicePRO metadata API response before mapping to Freshdesk custom fields. We extract full conversation history (customer replies, technician notes, status-change log) via the ServicePRO REST API and write them as Freshdesk Conversation records (inbound/outbound email types). Attachments linked to tickets migrate as Freshdesk ticket attachments via the Freshdesk Attachments API endpoint.

ServicePRO Employee records map to Freshdesk Agents. The ServicePRO CSV Import Utility handles bulk user load with department or company assignments; we use this alongside API extraction for individual user records. Agent permissions in ServicePRO (Professional system-level, Enterprise granular RBAC) map to Freshdesk Agent Roles and Profiles. We preserve the original department and permission scope as Freshdesk group membership and custom fields so that post-migration permission validation is possible.

ServicePRO asset records (name, type, serial number, custom asset fields) map to Freshdesk Assets via the Freshdesk Assets API. The ServicePRO CSV Import Utility can mass-import assets and link them to users or locations; we use the utility for bulk loads and the API for records with complex custom field dependencies. Asset-to-ticket linkage is preserved by mapping the ServicePRO asset reference field to Freshdesk Asset's associated_ticket relationship.

ServicePRO Target Categories are a hierarchical lookup structure (vendors, customers, locations, equipment types) exposed via GetTargetCategoryList and GetTargetCategoryByTargetCategoryId. We map these to Freshdesk Groups (for organizational boundaries like departments or ServiceCenters) and Freshdesk Products (for equipment types and service classifications). The isRelated and UsedInSharedRef flags from the API determine whether the target category maps to a Group, a Product, or a custom field dropdown.

ServicePRO Programs define service offerings and link to inventory items, branches, and events. We map Program records to Freshdesk Products and preserve Program-to-ProgramEvent relationships as Freshdesk Product Bundle associations or custom field lookups, depending on the destination Freshdesk edition. Programs that represent service tiers map to Freshdesk SLA policies if the destination edition supports SLA configuration.

ServicePRO Enterprise multi-Center setups define independent ticket queues, user pools, and routing rules per Service Center. Freshdesk uses a single-queue model with Groups and Teams as the organizational layer. We consolidate Center boundaries into a unified Freshdesk Group schema during scoping, with customer sign-off required before extraction begins because the wrong Center-to-Group mapping redirects tickets to incorrect teams post-migration. Professional edition migrations (single ServiceCenter) map directly to one Freshdesk Group.

ServicePRO Custom Forms define ticket intake layouts with flexible field types (text, numeric, date, checkbox, dropdown, masked entry). Field type is encoded as a pair of integer values in the metadata API response. We decode each type pair explicitly and map to the nearest Freshdesk custom field equivalent. Masked-entry types (telephone, SSN, credit card) are flagged for PII handling: we exclude these fields from migration unless the customer explicitly approves PII transfer and the destination Freshdesk instance has appropriate data-privacy configuration.

ServicePRO System Email Accounts define sending and receiving addresses (Professional capped at 10, Enterprise unlimited). We export account configurations including SMTP settings via the Setup API and map them to Freshdesk Support Email configurations. Email-to-ticket routing (the email address that creates a Freshdesk ticket when a customer emails it) is configured in Freshdesk's Admin > Email > Support Email settings.