Migrate from Zuper to Microsoft Dynamics 365 Sales

Zuper Customer records representing organizations map directly to Dynamics 365 Sales Account records. The Account Name, Website, Industry, Phone, and Address fields carry over with direct field-level mapping. Zuper Customers that represent individual persons must be split into both Account (for the company, if any) and Contact records.

Zuper Customers without an associated organization, or where the individual is the primary record, map to Dynamics Contact. The Contact inherits the customer's name, email, phone, and address fields directly. The Contact links to the primary Account via the Parent Customer ID lookup field in Dynamics.

Zuper Jobs transform into Dynamics Opportunities when the job has revenue or sale potential. The job name becomes the Opportunity name, the job amount or estimate maps to the Estimated Revenue field, job status maps to Opportunity Stage via value mapping, and the expected completion date becomes the Estimated Close Date. Jobs that represent service-only work with no revenue map to Task records instead.

Zuper Jobs without revenue potential — maintenance visits, inspections, or non-billable service calls — map to Dynamics Task records. The Task subject carries the job title, description maps to the Task's description field, and the assigned technician resolves to the Task's OwnerId. Tasks preserve the original job's create date for audit continuity.

Zuper job line items representing products or services on a billable job map to Dynamics Opportunity Product records. Each line item creates an Opportunity Product entry linked to the parent Opportunity. The product name, quantity, unit price, and discount carry over. Products that do not exist in Dynamics are created as basic Product records during migration.

Zuper Teams map to Dynamics 365 Sales Teams. Teams in Zuper represent groupings of technicians for scheduling and dispatch purposes. In Dynamics, Teams serve a similar grouping function for user access and record ownership. Each Zuper Team becomes a Dynamics Team record, with team members (Users) assigned to the team post-migration.

Zuper Users who are technicians map to Dynamics System User records. Owner resolution happens by email match — if the technician's email matches an existing Dynamics user, the UserId links directly. Unmatched users are flagged before migration for your admin to create Dynamics accounts or assign records to a fallback owner.

Zuper custom fields on Customer records require corresponding custom columns in Dynamics on the Account and/or Contact table. We analyze each custom field's data type — text, number, date, pick-list — and create matching column types in Dynamics. Pick-list fields require value-by-value mapping if the option set differs between platforms.

Zuper custom fields on Job records map to custom columns on the Opportunity or Task record in Dynamics, depending on how the job transforms. Job-specific custom properties (e.g., site location, job type classification, priority flags) carry as custom columns on the target entity. The original Zuper custom field values populate these columns during migration.

Zuper file attachments on Jobs or Customers re-upload to Dynamics as Notes with file attachments or SharePoint document locations. File size limits apply — Dynamics default is 32MB per file. Inline images in job descriptions download and rehost as Note attachments. Attachments preserve the original file name and any associated description.

Zuper job status values (Scheduled, In Progress, Completed, Cancelled) map to a custom pick-list column on the Opportunity or Task. We create a Zuper_Job_Status__c custom column and map each source status value to the nearest Dynamics-equivalent option. Completed jobs map to Closed Won or Closed Lost based on the job outcome.

Zuper timesheets and time-off records have no native equivalent in Dynamics 365 Sales CRM. We preserve timesheet data as a custom Dataverse table with columns for User, Date, Hours, Time-Off Type, and Status. This custom table provides reference data post-migration but does not connect to Dynamics payroll or resource management features.