Migrate from Formitize to Nutshell

Formitize's Client entity maps to Nutshell's Company object. Client name becomes Company name, address fields map to the address block, and the domain/website maps to the website field. Multi-location clients may require multiple Nutshell Company records if your team uses separate client records per location.

Formitize Contact maps to Nutshell Person. Each Contact belongs to one Client; the Client-to-Company relationship is established by linking the Person to the mapped Company record via Nutshell's person-company association. Contact status (active/inactive) maps to a custom flag if retention of inactive records is required.

Formitize's Contact Variables (e.g., birthday, internal customer order numbers) migrate to Nutshell Person custom fields. The type (text, date, number, choice) must be matched to Nutshell's field type options. Nutshell supports custom fields on People, Companies, and Leads only — not on Deals or Activities.

Formitize deals map to Nutshell Deals with the deal name, value (amount), and linked contact preserved. Pipeline stages in Formitize map to Nutshell milestones — a value-by-value mapping is required if stage names differ. Close date and owner assignment transfer directly.

Formitize Jobs have no native Nutshell equivalent. Each Job migrates as an Activity Note attached to the linked Company or Person record in Nutshell. The Note captures job status, key dates, and summary text. If granular job data is critical, your team should evaluate Nutshell's custom data approach before migration.

Formitize Assets (GPS coordinates, zones, serial numbers, asset-type custom columns) do not map to any Nutshell object. The migration strategy is to surface key asset data as Company-level custom fields (e.g., Primary_Asset_Serial__c) and attach a summary Note with full asset detail. Zone and location data migrates as text fields. Serialized asset tracking cannot be replicated in Nutshell natively.

Formitize asset types (e.g., HVAC Unit, Safety Equipment, Vehicle) are value sets that map to a Company-level custom pick-list field in Nutshell. The asset type value for each asset's parent client migrates as that value. If multiple asset types exist per client, the primary type is used.

Formitize form submission data (filled form content, timestamps, submitter) has no Nutshell equivalent. Submissions migrate as Notes attached to the relevant Company or Person record. The Note captures form type, submission date, and a text summary. Actual form file attachments are preserved separately.

Formitize user assignments on Jobs, Assets, and Contacts resolve to Nutshell Person records by email matching. Unmatched owners are flagged before migration; your team either creates Nutshell users first or assigns records to a fallback owner. Formitize's role/permission model does not map to Nutshell's sharing settings.

Formitize file attachments on Clients, Contacts, Jobs, and Assets are preserved by re-uploading to Nutshell's attached file storage. File size limits follow Nutshell's storage policy. The attachment is linked to the target Company, Person, or Deal record. Inline images in Formitize notes are downloaded and rehosted as Note attachments.

Formitize Workflows for multi-stage compliance processes, auto-tasks, and form-triggered actions have no Nutshell equivalent. These must be rebuilt in Nutshell's automation layer or re-implemented via a third-party automation tool. FlitStack exports workflow definitions as a structured document to assist your Nutshell admin during rebuild.

Formitize integrations connected via Zapier, API, or webhook do not transfer to Nutshell. Each integration must be rebuilt with Nutshell as the target application. Common integrations (e.g., accounting tools, scheduling apps) may have existing Nutshell connectors in Zapier or Nutshell's native integration directory.