Migrate from Zuper to Pipedrive

Zuper customers map directly to Pipedrive Persons — name, email, phone, and address fields transfer as-is. The Zuper customer notes field maps to the Pipedrive Person's note field. If a Zuper customer has no email, the record is still created in Pipedrive with available contact details.

Zuper stores a customer-level company name as a text property. In Pipedrive, this becomes a linked Organization record, with the customer Person associated via the primary organization relationship. If no company name exists in Zuper, no Organization is created — the Person record stands alone.

Every Zuper job becomes one Pipedrive Deal. The job title maps to the deal name, the job status value maps to a Pipedrive pipeline stage (see Pipeline Stage mapping), the job's total value or estimate becomes the deal amount, and the scheduled date maps to the expected close date. Job description maps to the deal's visible notes or a custom field depending on length.

Zuper job status values (created in Zuper settings) map to Pipedrive pipeline stages value-by-value. Stages must exist in Pipedrive before migration runs. Any Zuper status with no matching Pipedrive stage is mapped to the closest existing stage, and the original Zuper status value is preserved as a custom field (Original_Job_Status__c) on the deal.

Zuper line items attached to a job (materials, labor, services) become Pipedrive Products linked to the corresponding deal via deal-products. The product name, unit price, quantity, and tax fields map to Pipedrive Product fields. If Zuper uses flat item descriptions rather than a product catalog, items are created as one-off products during migration.

Zuper teams and individual technicians map to Pipedrive users. We resolve each Zuper user by email to a Pipedrive user account — matched users receive deal ownership directly; unmatched users are flagged for pre-migration invitation to Pipedrive. Zuper team groupings (beyond individual users) have no native Pipedrive equivalent and are preserved as a custom field on the deal.

Zuper timesheet entries become Pipedrive Activities of type 'task' or 'call', linked to the corresponding deal. The logged duration (in minutes or hours) is stored as a custom numeric field on the activity record. Original timestamps are preserved. Activities without a linked job are attached to the associated customer Person record.

Every custom field defined in Zuper's field builder is recreated as a corresponding Pipedrive custom field on the Deal, Person, or Organization object. The field type is matched: Zuper varchar/int/double/date/datetime/map to Pipedrive varchar/int/double/date/datetime/address; Zuper multiselect (set) maps to Pipedrive set. Pipedrive custom fields must be created in the target Pipedrive account before migration runs — we deliver a creation checklist.

Zuper stores job location as an address (street, city, state, zip) plus GPS coordinates. If the job is associated with a customer, the location becomes the Organization's address in Pipedrive. If the job represents a one-off site visit at a location not tied to an existing organization, the full address is stored as a custom field (Job_Site_Address__c) on the deal.

Zuper job categories (configured in Zuper's Job Category hub) are used to classify work orders. In Pipedrive, these map to Labels on the deal or a custom pick-list field (Job_Category__c). We recommend using a custom field rather than labels for searchability, but the choice is configurable in the migration plan.

Zuper's Workflow Builder creates node-based automations with event triggers and branching logic tied to job and customer objects. Pipedrive Automations use a trigger-condition-action model with no equivalent branching capability. Workflow definitions are exported as a PDF/JSON reference document for rebuild in Pipedrive's automation builder. Guided Workflows (inspection and quote flows) also do not migrate.

Files attached to Zuper jobs or customers are downloaded and re-uploaded as attachments on the corresponding Pipedrive Deal or Person record. File size limits apply — Pipedrive's file size limit is 150MB per file. Inline images in Zuper notes are extracted and re-hosted as attachments.