Migrate your ServicePRO data

Service Requests are the core ticket object. We map standard fields like status, priority, category, and assigned technician. Custom form fields are supported via field-level mapping at import time using ServicePRO's enumerated field type system (text, numeric, date, checkbox, dropdown, etc.). Source ticket status history is preserved as a linked audit log.

ServicePRO has a documented Employee API endpoint (GET api/v1/Setup/GetEmployeeInfoByEmployeeId) and a built-in CSV Import Utility that can mass-import users with department or company assignments. The import utility also detects existing users and updates records. We pull full user profiles including role assignments and permissions.

Assets are supported via the CSV Import Utility, which can mass-import asset records and link them to users or locations. We map asset name, type, serial number, and any custom asset fields defined in the customer's ServicePRO configuration. Asset-to-ticket linkage is preserved during migration.

Target Categories are a hierarchical lookup structure exposed via the Setup API (GetTargetCategoryList, GetTargetCategoryByTargetCategoryId). The API returns isRelated and UsedInSharedRef flags that indicate lookup relationships. We map these as normalized taxonomy records but customer-specific category trees may require manual review for naming consistency.

Target records are the individual entities within Target Categories (vendors, customers, locations, equipment types). Exposed via GetTargetList and filtered by targettypeid. We map target name, type, and cross-references. Deep Target Category hierarchies require field-level mapping against the destination schema.

Programs define service offerings and link to inventory items, branches, and events. Exposed via GetProgramList and GetProgramByProgramTypeId. We preserve Program-to-ProgramEvent and Program-to-ProgramInventoryItem relationships as linked records. Custom programs require value-level mapping.

Custom Forms define ticket intake layouts and capture structured data. Professional edition is capped at 25 forms; Enterprise has unlimited. We export form structure and field definitions from the metadata API but form layouts are not machine-exportable; we reconstruct equivalent forms in the destination system using the field definitions captured.

Business Rules define automated routing, escalation, and notification logic within ServicePRO. They are configuration-level objects with no documented API export endpoint. We document all rules during discovery and provide a written rules inventory so the customer can manually rebuild them in the destination system.

System Email Accounts define sending and receiving addresses used in ticket communications. Professional is limited to 10; Enterprise has unlimited. We export account configurations including SMTP settings and routing rules. Email templates linked to accounts require separate template mapping.

Service Centers define organizational boundaries for ticket queues and users. Professional supports a single Service Center; Enterprise supports multiple. When migrating from multi-center Enterprise to a single-center destination, we flag the consolidation as a migration-critical decision requiring explicit scope alignment.

ServicePRO stores attachments linked to tickets, assets, and forms. We attempt to export attachments via the API or via direct database reference where accessible. Large binary attachments (images, PDFs, signed forms) may require separate file transfer and re-linking in the destination system.