Migrate from ServeManager to Freshsales

ServeManager job status has no direct Freshsales equivalent — misconfigured pipeline mapping causes silent stage errors

ServeManager tracks service jobs through a discrete status model (Pending, In Progress, Served, Unsuccessful). Freshsales deal stages are configurable pick-list values scoped per pipeline. If your Freshsales pipeline does not have stage values that map cleanly to ServeManager statuses, migration validation fails on those records silently. We pre-validate stage mapping with your Freshsales admin before migration runs and surface any unmapped status values as action items — do not proceed to full migration until every ServeManager status value has a corresponding Freshsales stage.

GPS and photo attachments require custom field setup in Freshsales before migration

ServeManager captures GPS coordinates, photo proofs, and electronic signatures as part of every attempt record. Freshsales has no native GPS, photo, or signature fields on Sales Activities. We create custom fields (GPS_Latitude__c, GPS_Longitude__c, Signature_URL__c) on the activity object before migration begins, but those fields must be permitted by your Freshsales plan. Growth plan limits custom fields per object — Pro and Enterprise plans support the field count needed for full GPS preservation. We confirm plan tier before creating the schema.

Multi-pipeline Freshsales setups require per-pipeline stage mapping — default pipeline alone may not match your service workflow

Freshsales Pro and Enterprise plans allow multiple sales pipelines, each with its own stage set and automation triggers. If your firm uses ServeManager to track multiple service types (eviction, family law, commercial), those likely correspond to separate Freshsales pipelines. A single pipeline mapping collapses all job types into one stage set, which can produce confusing reports. We recommend creating separate Freshsales pipelines before migration and mapping each ServeManager service type to its corresponding pipeline via a Pipeline_ID custom field on the Deal.

ServeManager invoice-to-payment tracking does not map to Freshsales native objects — a shadow accounting model is required

ServeManager generates invoices and tracks payments separately from jobs. Freshsales has no native invoice or payment record object — the Amount field on a Deal represents expected deal value, not paid invoices. We handle this by mapping invoice totals to Deal.Amount and creating custom Sales Activity entries for each payment record. However, Freshsales will not automatically calculate outstanding balances or generate aging reports for your service fees. If your firm requires accounts-receivable tracking, plan to either use a Freshsales integration with an accounting tool post-migration or maintain a separate financial record system.

Freshsales Growth plan caps custom fields and pipelines — Enterprise features needed for full schema parity

ServeManager supports unlimited custom fields on jobs and companies. Freshsales Growth plan limits custom fields to a subset per object, and pipelines are restricted to one on the base tier. If your ServeManager setup uses more than 10 custom fields per object or multiple service-type pipelines, your Freshsales account must be on Pro or Enterprise to support full migration parity. We audit your ServeManager schema before migration and report any feature-gating findings — your team upgrades the Freshsales plan before we create custom fields beyond Growth-plan limits.