Migrate from Formitize to Freshsales

Formitize Client maps directly to Freshsales Account. The Client name becomes Account Name. Formitize client-level address, phone, and custom fields migrate to Account address fields and Freshsales custom fields. Clients with no associated contact records create standalone Accounts in Freshsales.

Formitize Contact maps to Freshsales Contact. Freshsales requires an AccountId lookup for each Contact — the Contact's parent Client resolves to a Freshsales Account before the Contact migration runs. Formitize contact-level custom fields map to Freshsales Contact custom fields and preserve data fidelity.

Formitize Contacts that have not converted to an active client relationship split to Freshsales Lead. If a Formitize Contact has associated open deals or recent activity, it routes to Freshsales Contact instead to preserve the relationship history. The split rule is configurable based on your pipeline definition.

Formitize Deal maps to Freshsales Deal. Deal name, amount, stage, expected close date, and owner all translate directly. Formitize's single-pipeline stage names map to Freshsales pipeline stage values. Multi-pipeline setups in Formitize require multiple Freshsales pipelines, which requires Freshsales Pro or above.

Formitize Jobs that represent billable work or service engagements map to Freshsales Deals when the Job has deal-like attributes (amount, stage, client linkage). Job status (Pending, In Progress, Completed) maps to Freshsales Deal stage. Job-specific fields migrate as custom fields on the Deal.

Formitize Asset maps to Freshsales Asset. Asset name, description, location, GPS coordinates, and zone data migrate to Freshsales Asset fields. Zone data from Formitize stores as a text field or custom field in Freshsales since Freshsales Asset does not have a native Zone concept.

Formitize custom fields on Clients, Contacts, Deals, and Assets require Freshsales custom fields to be created before migration. Field types (text, number, date, dropdown) map to Freshsales equivalent types. Pick-list value sets require Freshsales option list creation with the same values.

Formitize users are resolved by email address against Freshsales user accounts. Unmatched owners are flagged before migration — either invited to Freshsales first or assigned to a fallback user. Formitize role-based permissions do not transfer; Freshsales profile and permission set assignment is a destination-side configuration step.

Formitize Documents attached to Clients, Contacts, Jobs, or Deals migrate to Freshsales Documents. Files re-upload to Freshsales file storage. Formitize document expiry alerts do not migrate — Freshsales does not have a native document expiry trigger mechanism or equivalent automation.

Formitize Smart Assist workflows, automated job-status updates, auto-invoice creation, and form-triggered actions cannot migrate. These must be rebuilt in Freshsales Workflows (Growth plan) or Freshsales Pro Automation. We export workflow definitions as a reference document for your Freshsales admin to guide implementation.

Formitize QuoteAccept quotes and PayNow payment records do not have direct Freshsales equivalents. Quote line items map to Freshsales Products and Deal Product Line Items. Payment status and transaction history migrate as custom fields on the Deal since Freshsales does not have a native payment reconciliation module.

Formitize form submission data linked to Jobs or Contacts migrates as Freshsales Notes on the parent record. The original form field values store in the Note body. Form-specific submission metadata that has no matching Freshsales field migrates as a custom field on the linked object or is flagged for archival.