Migrate from Zuper to HubSpot

Zuper Customer maps 1:1 to HubSpot Contact. Email, phone, address, and name fields translate directly with no transformation required. Owner assignment resolves by matching the customer's owner email against HubSpot user accounts. Any Zuper custom fields defined on the Customer object are inventoried during the pre-migration audit and mapped to equivalent HubSpot contact properties. Pick-list custom fields receive value-mapping tables for HubSpot admin review before migration runs.

Zuper Organization maps to HubSpot Company — business name, domain, industry, and employee count fields translate directly. Zuper's parent-organization hierarchy maps to HubSpot's parent-company field. Multi-contact organizations (Zuper allows N:N) collapse to a primary Company record with associated Contact records.

Zuper Job maps to HubSpot Ticket for service-dispatch use cases. Job subject, status, priority, job_category, and assigned technician map to Ticket subject, status, priority, ticket category, and owner. Original scheduled_start and scheduled_end times preserve as custom datetime fields on the Ticket.

Jobs that carry financial line items — estimate amounts, service fees, parts costs — merge into a HubSpot Deal (for revenue tracking) plus a linked Ticket (for field-service details). The Deal captures Amount, Stage, and CloseDate; the Ticket captures job status, category, and technician. We preserve the linkage via Deal-Ticket association.

HubSpot has no native project object. We create a zuper_project custom object (requires Operations Hub Starter or higher). Project name, description, start_date, end_date, status, and milestones map to custom properties. Project-phase records may map as child records or as a multi-select milestone property.

Zuper job categories (HVAC, Plumbing, Electrical, etc.) map to HubSpot ticket-category values via a value-by-value mapping table. If a category does not exist in HubSpot, we create it during schema setup. Unmapped categories are flagged for admin review before migration runs.

Zuper Teams map directly to HubSpot Teams using the same team name and member roster. HubSpot Team membership controls record-level access permissions and assignment routing for migrated data. Teams with no matching HubSpot Team name are flagged for admin creation before migration begins, ensuring all technicians and dispatch staff have proper access assignments. Team-based visibility rules and ownership hierarchies transfer to maintain operational continuity after cutover.

Zuper Users who are internal employees migrate as HubSpot Users by email match — the technician flag, user role, and team assignment transfer as HubSpot user properties. Zuper Users flagged as external contractors or part-time technicians may map to Contacts instead, depending on your HubSpot licensing model.

HubSpot has no native timesheet object. We create custom datetime and number fields on the User or Contact record to store timesheet hours per period, timeoff requests, and approval status sourced from Zuper. Zuper's Timeoff Request Types map to a custom pick-list on the user record.

Zuper quotes and proposals migrate as HubSpot Deals with custom fields capturing the quote number, validity date, and line-item summary. Individual line items with product, quantity, and price migrate to Deal line items (available in HubSpot Sales Hub Pro and Enterprise). Status (Draft, Sent, Accepted, Rejected) maps to a custom pick-list.

Zuper invoices with payment status, amount, and line items do not have a native HubSpot equivalent. We create a zuper_invoice custom object or store invoice metadata as custom fields on the associated Deal. Invoice PDF attachments re-upload to HubSpot's file storage and linked to the record.

Zuper file attachments on Jobs, Customers, and Organizations download and re-upload to HubSpot Files. Files are linked to the corresponding HubSpot record (Contact, Company, Ticket). Size limits per HubSpot apply — files over the limit are flagged for manual review.