Migrate from ServicePRO to Salesforce Service Cloud

ServiceDesk Tickets map to Salesforce Case records. Standard fields (status, priority, category, assigned technician) migrate directly. We resolve Service Center boundaries into Salesforce Queues during scoping so that routing assignments are preserved. Ticket conversations migrate as EmailMessage records linked to the Case. Custom form fields on ServiceDesk Tickets migrate as custom Case fields, with field types explicitly mapped from ServicePRO's enumerated type system (text, numeric, date, checkbox, dropdown) to Salesforce field types. Masked-entry fields (telephone, SSN) are flagged for PII review before import and may be encrypted or excluded based on customer policy.

ServicePRO Employees extracted via the Employee API (GET api/v1/Setup/GetEmployeeInfoByEmployeeId) map to Salesforce User records. The CSV Import Utility is used for bulk user loads where the source data is already formatted, while the REST API covers incremental and real-time extraction. We match by email as the dedupe key. Any ServicePRO Employee without a matching Salesforce User is held in a reconciliation queue for the customer's admin to provision before ticket import begins, because Case OwnerId requires a valid Salesforce User reference.

ServicePRO Asset records map directly to Salesforce Asset. We map asset name, type, serial number, and any custom asset fields defined in the ServicePRO form schema. Asset location links to the mapped Salesforce Account (from ServicePRO's Target Records for locations). Asset linked to a user in ServicePRO links to the corresponding Salesforce Contact via the Asset's ContactId field. The CSV Import Utility is available for bulk asset loads, but we extract via API to ensure custom fields and relationship links are preserved in a single migration dataset.

ServicePRO Target Categories are hierarchical lookup structures exposed via GetTargetCategoryList and GetTargetCategoryByTargetCategoryId in the Setup API. The API returns isRelated and UsedInSharedRef flags that indicate cross-category relationships. We assess whether the category structure warrants a custom Salesforce object with lookup relationships or a global picklist value set, and we present the trade-off to the customer during scoping. Target Categories used only as ticket categorization labels become Case Origin or Case Type picklist values in Salesforce.

ServicePRO Target Records are individual entities within Target Categories (vendors, customers, locations, equipment types). We export Target Records via GetTargetList filtered by targettypeid and map them to Salesforce by type: vendors to Account with Account Type = Vendor, customers to Account with Account Type = Customer, locations to Account with Address fields populated, and equipment types to a custom AssetType__c picklist or custom object depending on the data relationship complexity. The customer signs off on the target type mapping before extraction.

ServicePRO Programs define service offerings and link to inventory items, branches, and events. Exposed via GetProgramList and GetProgramByProgramTypeId. We assess whether Programs function as Products (sellable service items) or as service templates. Programs with line-item pricing migrate to Salesforce Product2 with Standard Pricebook entries. Programs used as internal service templates without pricing migrate to a custom ServiceTemplate__c object. Program-to-ProgramEvent relationships migrate as custom lookup fields or a junction object depending on the relationship cardinality.

ServicePRO Custom Forms define ticket intake layouts and capture structured data. Professional edition caps at 25 forms; Enterprise has unlimited. We export form structure and field definitions from the metadata API and map them to Salesforce custom Case fields. Each custom field receives a corresponding custom field on the Case object in Salesforce with the same field label, help text, and picklist values (for dropdown and multi-select types). Field-level security and field sets are configured in the destination org during the sandbox migration phase. Dropdown option lists must be validated as identical between source and destination before finalizing the import.

ServicePRO Business Rules define automated routing, escalation, and notification logic. They have no documented API export endpoint. We do not migrate Business Rules as automation code. During discovery, we flag every Business Rule we discover, capture its trigger conditions, actions, and target entities, and document it in a written rules inventory with a recommended Salesforce Flow equivalent for each. The customer's admin rebuilds rules in Flow post-migration. This inventory is a deliverable, not a rebuild service.

ServicePRO 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, FROM addresses, and routing rules. In Salesforce, we map these to Org-Wide Email Addresses and Email-to-Case routing addresses. If the customer runs Salesforce Inbound Email Services for case creation, we configure the routing rules in Service Cloud Email-to-Case settings during the sandbox migration phase.

ServicePRO Service Centers define organizational boundaries for ticket queues and users. Professional supports a single Service Center; Enterprise supports multiple. When migrating from an Enterprise multi-Center setup to Salesforce, we map each Service Center to a Salesforce Queue with appropriate Case sharing rules and assignment rule entries. This is the highest-risk migration decision for Enterprise customers because incorrect Center-to-Queue mapping redirects tickets to incorrect teams post-migration. We handle it as an explicit scope item with customer sign-off before extraction begins.

ServicePRO stores attachments linked to tickets, assets, and forms. We export attachments via the API or via direct database reference where accessible. Large binary attachments (images, PDFs, scanned documents) migrate as Salesforce ContentVersion records linked to the parent record (Case, Asset, or custom object) via ContentDocumentLink. We set the FileType, ContentSize, and Title fields from the source metadata. Attachments exceeding 25 MB per file are flagged for alternative handling (external storage with link reference) because Salesforce ContentVersion has a 25 MB per-file limit for standard uploads.

ServicePRO SLA configurations define response and resolution time targets tied to priority levels and Business Rules. They do not export via API. We document the SLA matrix during discovery (First Response Target, Next Response Target, Resolution Target per priority level) and map it to Salesforce Entitlement Processes and Milestones. The customer's admin configures the Entitlement in Salesforce Setup after migration, using the documented matrix as the configuration source. Entitlements require Service Cloud Premier or Unlimited edition.