Migrate from Zuper to Freshsales

Zuper Customers map directly to Freshsales Contacts. Email, phone, address, and job title fields carry over with field-level mapping. If a Zuper Customer has no email address, Freshsales requires a unique identifier — we flag records missing email before migration and create a fallback handling plan.

Zuper Customers with no associated Deals can route to Freshsales Leads, preserving lead status and source attribution. Customers with at least one completed or open Job route to Contact to preserve the account relationship in Freshsales. Your team decides the routing rule before migration runs.

Zuper Organizations map 1:1 to Freshsales Accounts. Organization name becomes Account Name, domain maps to Website, industry maps via value mapping against Freshsales' default industry pick-list. Parent-child organization hierarchies in Zuper map to Freshsales' Parent Account field if both parent and child exist in the migration scope.

Zuper Jobs are the most complex object to migrate. Each Job maps to a Freshsales Deal with job-specific attributes (priority, category, status, technician assignment) stored in custom fields on the Deal. Job pipeline and stage in Zuper map to Freshsales Deal Stages — we generate a stage-value map during planning so pipeline visibility is preserved.

Job-level activity logs including status notes, technician updates, and internal comments merge into Freshsales Tasks attached to the corresponding Deal. Original timestamps from each activity log entry are preserved in custom datetime fields on the Task record. This approach keeps the complete activity history accessible in Freshsales without creating duplicate Deal records, maintaining referential integrity across the migration.

Zuper Assets linked to an Organization map to the corresponding Freshsales Account with asset details in custom fields (asset name, serial number, installed date). Standalone Assets without a parent Organization require a custom Asset module in Freshsales — we create this as part of the migration plan for accounts that need it.

Zuper Properties are custom fields on Jobs, Customers, Organizations, and Assets. Each Property maps to a Freshsales custom field on the appropriate object. Property data type (text, number, date, pick-list) determines Freshsales field type. Pick-list values in Zuper require Freshsales custom pick-list setup per field.

Zuper Products, Parts, and Services map directly to Freshsales Products. Product name, SKU, unit price, and description transfer field-by-field. Products linked to Jobs in Zuper map as Deal Line Items in Freshsales using Freshsales' native Product lookup feature to maintain the product-to-deal relationship after migration.

Zuper Users and Technicians map to Freshsales Users by email match. Owner assignment on Jobs becomes Owner assignment on the corresponding Freshsales Deal. Unmatched Zuper users are flagged before migration — teams either create Freshsales accounts for them or reassign records to a fallback owner.

Zuper Teams have no native Freshsales equivalent. Team membership maps to a custom field on the Deal (e.g., Team_Assigned__c) storing the team name as a pick-list value. If granular team-to-user routing is needed, a custom Team object with a junction to Users can be built post-migration.

Zuper Timesheets have no Freshsales equivalent. We create a custom module called Timesheet in Freshsales linked to the User (owner) and optionally to the related Deal. Timesheet entries include hours worked, date, and timeoff type. This preserves historical labor data without forcing it into CRM fields not designed for it.

Zuper Job Categories (Plumbing, HVAC, Electrical, etc.) map to a custom pick-list field on the Freshsales Deal object (Job_Category__c). Each unique category value is created as a pick-list option. This preserves the service-type dimension for reporting without conflating it with Freshsales' deal stage model.