Migrate from FRONTU to Freshsales

Frontu technician records map to Freshsales Users so field staff appear as owners on Work Order records migrated as Deals. Email, name, phone, and role transfer directly. Frontu's role field (e.g., 'Field Engineer', 'Dispatcher') becomes a custom field on Freshsales User since Freshsales does not have a native role-labeling mechanism for users outside of profile assignments.

Frontu client records become Freshsales Accounts. The primary contact person from the client record becomes a Contact linked to the Account via AccountId. If Frontu stores multiple contact persons per client, secondary contacts migrate as additional Freshsales Contacts. The client's primary email and phone map to the Contact record; the business phone maps to the Account.

Frontu work orders map to Freshsales Deals with job-type and status data stored in custom fields. Deal Name uses the Frontu work order name or ID. Deal Amount pulls from service fee or parts cost fields if present. If Frontu tracks multiple line items per job, they map to Deal Products in Freshsales. Deal stage is assigned based on Frontu's job status value mapping (Open → 'Proposal/Price Quote', In Progress → 'Value Proposition', Completed → 'Closed Won', Cancelled → 'Closed Lost').

Individual task steps within a Frontu work order migrate as Freshsales Tasks linked to the parent Deal. Task Subject carries the step description. Task Status maps from the step completion flag. Original timestamps and assigned technician (as Task Owner) are preserved. These are not Freshsales Workflow automations — they are migrated data records of what was completed.

Frontu site records attach to the corresponding Freshsales Account as address fields (street, city, state, zip, country). If a single Frontu client has multiple service locations, each site becomes an Account Contact Relationship or is surfaced as address notes on the Account. Freshsales Account supports one billing address and one shipping address natively; additional site addresses require custom fields.

Frontu job status values (Open, In Progress, On Hold, Completed, Cancelled) have no direct Freshsales equivalent because Freshsales tracks deal stage at the pipeline level, not per-record status flags. We create a custom pick-list field Job_Status__c on the Deal object and map each Frontu status value individually. Deal Stage is set independently based on the stage in the Freshsales pipeline.

Frontu job types (e.g., 'Preventive Maintenance', 'Emergency Repair', 'Installation') are field-service classifications with no Freshsales native equivalent. We create a custom pick-list field Job_Type__c on the Deal object and migrate each unique value from Frontu. This allows Freshsales reporting to filter deals by service category after migration.

Frontu time entries recording technician hours worked do not map to any Freshsales native object. Freshsales has no time-tracking module. We store estimated duration and actual duration as custom number fields (Estimated_Hours__c, Actual_Hours__c) on the Deal, and per-step time as custom fields on individual Tasks. Labor cost, if tracked, becomes a custom currency field.

Frontu file attachments on work orders migrate as Freshsales Notes with the file content attached. Photos and signed documents attach to the corresponding Deal record. Large files (over Freshsales' 25MB limit) are flagged and re-uploaded manually or via Freshsales Files with a download link stored in the Note.

Any custom properties configured in Frontu on Work Order or Technician objects migrate as Freshsales custom fields on the corresponding object. Custom fields must be pre-created in Freshsales before migration (on the Enterprise plan or via Freshsales admin for Growth/Pro). We deliver a custom-field creation plan as part of the pre-migration schema setup.