Migrate from Workiz to Freshsales

Workiz clients map directly to Freshsales contacts. Email, phone, mobile phone, and address fields carry over as standard Freshsales contact fields. Clients without a company association land as standalone contacts — if the client represents a business entity, the company name should map to the Freshsales Account Name and the contact linked via AccountId.

Workiz clients that represent companies (with business address, domain, and multiple service locations) map to Freshsales accounts. Business name maps to Account Name, business address maps to Account Address fields, and domain maps to Website. The client's primary contact becomes a Freshsales Contact linked to the Account via AccountId lookup.

Workiz leads map 1:1 to Freshsales leads — all lead fields including name, email, phone, source, and custom lead fields transfer directly. Freshsales lead status pick-list values (New, Contacted, Qualified, Unqualified) map from Workiz lead status. Lead scoring from Workiz Genius Leads (if applicable) migrates as a custom numeric field in Freshsales.

Workiz jobs have no native equivalent in Freshsales CRM. FlitStack creates a custom Job module in Freshsales with fields for job status, job type, scheduled start and end time, assigned technician (user lookup), service address, client link, and description. This custom module is linked to the Freshsales Contact representing the Workiz client. Jobs can also be mapped into Opportunities as deals with custom job-type fields for teams that prefer a single-object view.

Workiz job status values (Scheduled, En Route, In Progress, Completed, Cancelled) migrate as a pick-list custom field on the custom Job module in Freshsales. These are preserved exactly as written in Workiz with no value transformation — the pick-list is created to match the source values.

Workiz job type (the service performed — e.g., HVAC repair, plumbing, electrical) maps as a text or pick-list custom field on the custom Job module. If Workiz uses a controlled vocabulary for job types, those values are reproduced as pick-list options in Freshsales. If job types are free-form, they migrate as text fields.

Workiz technicians are mapped to Freshsales users by email match. The technician's name in Workiz becomes a User lookup field on the custom Job module. Unmatched technicians are flagged during pre-migration validation — your Freshsales admin either creates matching user accounts first or assigns those jobs to a fallback user.

Workiz estimates contain a client link, job details, line items (service + product), and a total. In Freshsales, the estimate can become a custom Estimate module or be split: the client and high-level scope map to an Opportunity (with amount = estimate total), and line items map to Product records linked as Opportunity Line Items. We recommend the custom Estimate module approach for audit continuity.

Workiz invoices (issued after job completion) map to Freshsales as a custom Invoice module linked to the Job and Contact, with invoice number, issue date, due date, line items, and total amount preserved. The invoice total can also update the linked Opportunity amount. Paid invoices carry a 'Paid' status custom field; unpaid invoices carry 'Open' or 'Overdue' status migrated from Workiz.

Workiz line items and products (parts, labor rates, service packages) map to Freshsales Products with Name, Unit Price, and Description. Products are then linked to Opportunity Line Items during estimate and invoice migration. Product inventory data from Workiz (if tracked) migrates as a custom numeric field on the Product record.

Workiz automations (job-triggered alerts, client reminders, tech assignment rules) have no migration path to Freshsales. We export your Workiz automation definitions as a structured reference document that your Freshsales admin or FlitStack consultant uses to rebuild equivalent rules in Freshsales Workflows (available on Growth and above). This is a manual rebuild step outside the data migration scope.

Workiz GPS tracking data (technician locations, route history) is not applicable to Freshsales CRM. Freshsales does not have a field-service dispatch or GPS module. If GPS history is business-critical, it should be exported from Workiz as a separate report before the migration cutover and archived independently.