Migrate from Zuper to Twenty CRM

Zuper Customers (individuals requesting service) map directly to Twenty People records. Each customer's name, email, phone, and address fields transfer as standard People fields. The customer's primary location address is preserved as supplementary address data on the related Company record.

Zuper Locations (service addresses linked to customers) map to Twenty Company records. A Zuper customer with multiple locations generates multiple Company records in Twenty — each with its own address, industry classification, and linked People records for on-site contacts at that location.

Zuper Jobs are the primary migrated record. Each Job becomes a Twenty Opportunity linked to the target Company (the service location). Job status (Pending/In Progress/Completed) maps to Opportunity Stage values using a configured value-mapping table. Job scheduled date maps to Opportunity Expected Close Date for work-order tracking.

Zuper's four-tier job status (Pending, In Progress, Completed, Cancelled) maps to a simplified Four-Stage sales pipeline in Twenty: Appointment Scheduled → Work In Progress → Closed Won (for Completed) or Closed Lost (for Cancelled). Stage probability is assigned per stage value.

Zuper job priority levels (Low, Medium, High, Urgent) have no native equivalent field type in Twenty CRM's standard Opportunity object. We create a custom select field named Job_Priority__c on the Opportunity object under Settings → Data Model to preserve priority ordering and maintain visibility into service-level agreements. Priority values are mapped verbatim from Zuper's pick-list options during the migration.

Zuper job categories (HVAC, Plumbing, Electrical, etc.) from the Job Category Hub have no native CRM equivalent in Twenty. A custom select field on Opportunity captures the service category. Category values are mapped from Zuper's category names to Twenty pick-list options.

Zuper Teams and individual Technicians are resolved by email to Twenty Workspace Members. A Team in Zuper becomes a Group of individual member links in Twenty. Unresolved technicians (no matching email) are flagged and assigned to a fallback workspace member or held for manual assignment.

Zuper Timesheets and Timelog entries (hours logged per technician per job) are translated into a custom Timesheet object in Twenty linked to the Opportunity (Job) and the WorkspaceMember (Technician). This preserves labor history without forcing it into a standard CRM object.

Zuper job notes and internal comments migrate as Twenty Note records attached to the corresponding Opportunity (Job). Original timestamps and author attribution are preserved. Notes with attachments (photos, signed forms) are flagged for manual re-upload since CSV import does not carry binary file references.

Zuper job attachments (before/after photos, signed forms, compliance documents) are not included in standard CSV exports. We export the attachment list and metadata, then re-upload via Twenty's API or manual file attach. This step is documented in the migration checklist and can be parallelized with the data migration.

Every Zuper custom field (created per module via Settings → Custom Fields) is audited and recreated in Twenty under Settings → Data Model before the main import. Custom field type mapping: Zuper text → Twenty text, Zuper number → Twenty number, Zuper date → Twenty date, Zuper select → Twenty select.