Migrate your Zuper data

Jobs are Zuper's primary work-order object. They carry status, assigned Users or Teams, Job Categories, locations, and line items. The schema is well-documented and stable across tiers. We migrate Jobs 1:1 with all standard fields and preserve checklist attachments as metadata.

Customers in Zuper include contact details, address, and linked Job history. Standard fields are consistent. We map Customer records including phone, email, and company association to the destination's contact or account object.

Zuper supports custom fields on Customer records. The API allows creating and updating custom field values via PATCH endpoints. We capture the custom field definitions and apply them at import time, handling value mapping for picklist and date types that may have different option sets in the destination.

Quotes in Zuper are linked to Jobs and carry pricing and service options. Customer reviews indicate the estimate module is underdeveloped with limited functionality. We migrate Quote line items and totals but recommend reviewing the destination's quote or estimate object schema for parity before committing, as some Zuper quote fields may not map cleanly.

Zuper exposes a full Timesheets CRUD API including get, create, update, delete, and summary endpoints. We migrate timesheet entries linked to Users and Jobs, preserving billable vs non-billable flags and duration data.

Timeoff is split across Timeoff Requests, Timeoff Request Types, and Timeoff Availability. These are related to the User object. We migrate Timeoff records with status and dates, noting that approval workflow states in the destination may differ and require manual review.

Teams are a named grouping of Users with dedicated CRUD endpoints. We preserve team memberships and map them to the destination's group or team objects.

Users represent field technicians and office staff. Zuper's API exposes User endpoints for timelog, assignment, and team membership. We migrate User records with active/inactive status and link them to Timesheet and Job history.

Job Categories are a classification system for Jobs. The API exposes Job Category configuration. We migrate category names and hierarchies but note that if the destination uses a different classification model, we collapse to text labels rather than recreating the full taxonomy.

Zuper's Workflow Builder uses a node-based UI to define automation sequences tied to Jobs and Quotes. There is no documented export format or API for workflow definitions. We do not migrate workflows automatically. We document the existing workflow triggers and actions for manual reconstruction at the destination.