Migrate from Zuper to Salesforce Sales Cloud

Zuper customers can be companies or individuals. We split by customer type: organizations map to Salesforce Account with address and industry fields; individual customers map to Contact with the Account linked via AccountId. Company-level custom fields migrate to Account, individual fields to Contact.

Jobs are the central Zuper object. We migrate to a custom Work_Order__c object in Salesforce to preserve job-specific fields (job type, priority, status, scheduled date, completion date). Alternatively, jobs can map to standard Case if your team prefers service-ticket semantics. The choice is made during scoping based on your Salesforce admin's preference.

Every custom field on a Zuper Job requires a corresponding custom field in Salesforce. Text fields become Text(255) or Long Text Area; number fields become Number; date fields become Date; pick-list fields become Pick-list with explicit value mapping. We create all fields during the migration setup phase before data loads begin.

Zuper customer custom fields are evaluated by scope — company-level fields create Account custom fields, individual-level fields create Contact custom fields. Pick-list values on Zuper custom fields require explicit value-by-value mapping to Salesforce pick-list options. During the scoping phase, we document each custom field’s data type, pick-list values, and any default settings, then generate a Salesforce field-creation checklist that your admin can execute before the data load.

Zuper job status values (New, In Progress, Completed, Cancelled, On Hold) map to Salesforce pick-list values on the custom Work_Order__c.Status__c field. Each Zuper status value is explicitly mapped to a Salesforce value. If Salesforce is a Case migration, status maps to Case.Status.

Zuper job priority levels map to a custom Priority__c pick-list on Work_Order__c. Standard Zuper priorities (Low, Medium, High, Urgent) translate directly. Custom priority levels added by your Zuper admin require value-by-value mapping. If your Zuper environment includes priority levels with associated SLAs or color coding, we preserve those as custom attributes on the Work_Order__c record to maintain operational context after migration.

Zuper assigns technicians to jobs. We resolve Zuper users to Salesforce Users by email match. Unmatched technicians are flagged before migration — your team either creates Salesforce users first or assigns those job records to a fallback owner. The resolved UserId becomes the Assigned_Technician__c lookup.

Zuper timesheet records migrate to a custom TimeSheet__c object with Start_Date__c, End_Date__c, Status__c, and Total_Hours__c fields. Each timesheet is linked to the technician's Salesforce User record via a lookup. Overtime and break data stored as additional custom fields. We also map timesheet approval status to a Status__c pick-list, and store any Zuper notes or attachments as Salesforce Files linked to the TimeSheet__c record.

Zuper Teams map to Salesforce Territories if your org uses territory management, or to a custom Team__c junction object that links multiple Users. We recommend the custom junction approach for most migrations because Salesforce Territories are tied to forecasting and require additional licensing.

Zuper Quotes and Proposals map to Salesforce Opportunities with line items. If your Salesforce org has CPQ installed, quotes migrate to the CPQ Quote object with product, quantity, and pricing preserved. Without CPQ, Opportunity Products capture line-item data at a basic level.