Migrate from Mobile Worker to Freshsales

Active field workers with completed jobs route to Freshsales Contact. Workers with no associated customer account or unqualified status route to Lead. The split is based on the worker's last job status and account association in the source platform. If a worker has multiple completed jobs across different accounts, the most recent job determines the routing.

Customer organizations in the mobile worker platform map 1:1 to Freshsales Accounts. Account name, industry, employee count, and annual revenue transfer as standard Account fields. Multi-location customers create one Account with address fields populated from the primary location record. When a customer has several sites, the primary site address is used for the Account's billing address, and additional site details are stored in a custom field.

Work orders map to Freshsales Deals with the pipeline determined by job type (service, installation, maintenance). Deal Name is constructed from Job Number + Customer Name. Amount maps from the estimated or actual job value field. Stage maps from job status using value-mapping rules per pipeline.

Each distinct job workflow in the mobile worker platform (e.g., Service Jobs, Install Jobs) becomes a separate Freshsales Pipeline. Job status values (Created, Assigned, Dispatched, En Route, On Site, Completed, Invoiced) map to corresponding Freshsales stage names per pipeline using value-by-value mapping rules.

Job site addresses populate the Account's shipping address fields in Freshsales. Multiple sites per customer create a primary Account with site-specific address data stored in a custom multi-select or text field for reference — Freshsales does not natively support N:1 site-to-account hierarchies.

Worker clock-in/clock-out records and total hours worked per job migrate as Freshsales Tasks with Type = 'Custom Activity' and subject = 'Field Time Entry'. Original timestamps and duration in minutes are preserved in custom datetime and number fields on the task.

GPS checkpoint records showing worker arrival and departure at job sites migrate as Freshsales Events with original start/end datetime, linked to the corresponding Deal. Event subject is set to 'Site Visit' with location details in the description field. If multiple checkpoints exist for a single job, each is recorded as a separate Event, preserving the full visit timeline for audit and reporting purposes.

Equipment records associated with jobs require Freshsales Enterprise for custom module creation. Without Enterprise, equipment serial number, make/model, and service history migrate as custom fields on the Deal or Account. Equipment-to-job associations are preserved as a text or lookup field.

Worker records include an owner or assigned technician field. FlitStack resolves this against Freshsales Users by email match. Unmatched owners are flagged before migration — either invite them to Freshsales first or assign their records to a fallback owner. If a worker has multiple assigned technicians, the primary technician is used for the OwnerId, and secondary technicians are stored in a custom multi-select field.

Photos and documents attached to work orders download and re-upload to Freshsales Files, linked to the corresponding Deal record. File size limits per Freshsales plan apply (Growth: 2GB/user; Pro: 5GB/user; Enterprise: 100GB/user). Inline images in notes are extracted and rehosted as separate attachments.

Any custom properties on worker records (certification level, vehicle ID, skill set) migrate as Freshsales custom fields on Contact or Lead. Field type mapping is applied: text to text, number to number, picklist to picklist. Custom field creation is scoped to the migration plan before data loads.

Job-level notes and internal comments migrate as Freshsales Notes attached to the corresponding Deal. Original create datetime and author (worker name) are preserved in note metadata fields. If a note contains references to attachments or other work orders, those links are recreated as Freshsales file attachments or related deal links to maintain context across records.

Invoice records and billing status from the mobile worker platform have no direct Freshsales equivalent — Freshsales does not include a billing or accounting module. Invoice amount, status, and payment date are preserved as custom fields on the Deal for reporting continuity.

Dispatch rules, geofence triggers, and route optimization logic built in the mobile worker platform do not transfer. These are rebuilt as Freshsales Workflows: auto-assignment rules handle worker routing, and location-based triggers require Freshsales territory management configuration. During the rebuild, FlitStack documents the existing rule conditions and priority order so that Freshsales workflows can replicate the original dispatch logic as closely as possible.