Migrate your Formitize data
Mobile-first FSM and CRM hybrid for field service businesses that need forms automation, job management, and client tracking in one Australian-built platform.
In its favor
Why people choose Formitize
The signal that keeps Formitize on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
All-in-one platform eliminates separate tools — users cite going paperless and consolidating CRM, job management, and invoicing as the primary driver for switching to Formitize.
Mobile-first design with a companion app and real-time job status tracking appeals to field service teams who need live visibility across locations.
Drag-and-drop form builder with custom styling lets field teams deploy industry-specific workflows quickly without developer involvement.
Industry packs for pest control, food safety, building inspection, and landscaping pre-configure templates for regulated vertical use cases.
Zapier and Mailchimp integrations allow Formitize to connect into broader marketing and operations stacks without custom API work.
Performance degrades when multiple forms are chained into a single workflow, frustrating users who need complex multi-step processes on mobile devices.
Custom contact fields and asset custom fields require manual setup per account — no shared configuration templates across an organization.
Export capabilities are limited: Smart Table CSV exports are available but there is no unified bulk data export across all modules, complicating data portability.
The platform is Australian-focused with GST pricing and regional billing conventions, creating friction for non-Australian customers evaluating the platform.
Reasons to switch
Why people leave Formitize
The recurring reasons buyers give for replacing Formitize. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Formitize fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Formitize pricing overview
Formitize charges per user per month at $29.99 (excl. GST for Australian businesses) for its standard tier, which bundles all core FSM and CRM modules. Industry-specific packs, Enterprise configurations, and Not for Profit rates are available via sales inquiry — pricing is not publicly documented for these tiers. The platform's Australian pricing basis (GST-exclusive) requires non-Australian customers to factor in local tax implications.
Standard
Tier 1 of 4
$29.99/user/month (excl. GST)
What's included
Need help selecting your CRM?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Formitize's schedule — see our quote-based pricing →
What gets migrated
Formitize object support
Object-by-object support for Formitize migrations. Per-pair details surface during scoping.
Clients
Fully supportedClients are the top-level account entity in Formitize. Each Client has location, billing, and contact associations. We migrate Clients as the primary parent record, preserving location data and client-level custom fields.
Contacts
Mapping requiredContacts belong to Clients and support custom Contact Variables (custom fields). Import improvements in recent releases have improved bulk contact import handling. We map Contacts to the destination CRM's equivalent contact or person record, preserving the Client relationship and custom field values.
Jobs
Fully supportedJobs are the core operational record in Formitize's FSM module. Jobs link to a Client, optionally to an Asset, and carry status, attachments, and photos. We preserve job history, job type templates, and stage progression when migrating Jobs to another platform.
Assets
Mapping requiredAssets belong to Asset Types and carry location coordinates, zone information, and client associations. Custom fields are supported per asset. We extract full Asset records including GPS data and zone metadata. Destination mapping depends on whether the target platform has a native asset model.
Forms / Smart Forms
Mapping requiredForms are the data collection layer — they capture field data and can trigger Workflows. Custom form fields (variables) vary by form. We migrate form data captured in Jobs and standalone form submissions, but form builder templates require manual reconfiguration at the destination.
Documents
Mapping requiredFormitize stores documents linked to Clients, Jobs, and Assets. Document attachments (photos, PDFs, signed forms) are migratable via the Job and Asset export flows. We flag large attachment volumes upfront to scope the export correctly.
Workflows
Mapping requiredWorkflows automate multi-stage compliance processes including Incident Reporting, Near Miss, and Non-Compliance management. Workflow definitions are configuration-level data that do not transfer 1:1 — we rebuild workflow logic at the destination based on process mapping.
Sales Pipeline / Quotes
Mapping requiredFormitize's Sales Pipeline manages deals with QuoteAccept for online quote generation and conversion to invoices. Pipeline stages and deal records are migratable. We map pipeline stages to the destination CRM's opportunity stage values.
Smart Tables (DataGrids)
Mapping requiredSmart Tables provide customized DataGrid views with export-to-CSV capability introduced in 2024. We can extract Smart Table data where the underlying records (Assets, Jobs, Contacts) are in scope for migration.
Users / Team Members
Fully supportedUsers are licensed individuals accessing Formitize. User records include Qualifications, Training, and Notes (export requested by users but not yet implemented natively). We map active Users to Owner or Assignee fields in the destination system.
Custom Fields / Contact Variables
Mapping requiredCustom fields (Contact Variables) are created at Settings > Contacts > Contact Custom Fields. They are per-account configuration. We preserve custom field schemas and map field values during import but cannot transfer the field definition itself to platforms without equivalent custom field capability.
| Object | Support | Notes |
|---|---|---|
| Clients | Fully supported | Clients are the top-level account entity in Formitize. Each Client has location, billing, and contact associations. We migrate Clients as the primary parent record, preserving location data and client-level custom fields. |
| Contacts | Mapping required | Contacts belong to Clients and support custom Contact Variables (custom fields). Import improvements in recent releases have improved bulk contact import handling. We map Contacts to the destination CRM's equivalent contact or person record, preserving the Client relationship and custom field values. |
| Jobs | Fully supported | Jobs are the core operational record in Formitize's FSM module. Jobs link to a Client, optionally to an Asset, and carry status, attachments, and photos. We preserve job history, job type templates, and stage progression when migrating Jobs to another platform. |
| Assets | Mapping required | Assets belong to Asset Types and carry location coordinates, zone information, and client associations. Custom fields are supported per asset. We extract full Asset records including GPS data and zone metadata. Destination mapping depends on whether the target platform has a native asset model. |
| Forms / Smart Forms | Mapping required | Forms are the data collection layer — they capture field data and can trigger Workflows. Custom form fields (variables) vary by form. We migrate form data captured in Jobs and standalone form submissions, but form builder templates require manual reconfiguration at the destination. |
| Documents | Mapping required | Formitize stores documents linked to Clients, Jobs, and Assets. Document attachments (photos, PDFs, signed forms) are migratable via the Job and Asset export flows. We flag large attachment volumes upfront to scope the export correctly. |
| Workflows | Mapping required | Workflows automate multi-stage compliance processes including Incident Reporting, Near Miss, and Non-Compliance management. Workflow definitions are configuration-level data that do not transfer 1:1 — we rebuild workflow logic at the destination based on process mapping. |
| Sales Pipeline / Quotes | Mapping required | Formitize's Sales Pipeline manages deals with QuoteAccept for online quote generation and conversion to invoices. Pipeline stages and deal records are migratable. We map pipeline stages to the destination CRM's opportunity stage values. |
| Smart Tables (DataGrids) | Mapping required | Smart Tables provide customized DataGrid views with export-to-CSV capability introduced in 2024. We can extract Smart Table data where the underlying records (Assets, Jobs, Contacts) are in scope for migration. |
| Users / Team Members | Fully supported | Users are licensed individuals accessing Formitize. User records include Qualifications, Training, and Notes (export requested by users but not yet implemented natively). We map active Users to Owner or Assignee fields in the destination system. |
| Custom Fields / Contact Variables | Mapping required | Custom fields (Contact Variables) are created at Settings > Contacts > Contact Custom Fields. They are per-account configuration. We preserve custom field schemas and map field values during import but cannot transfer the field definition itself to platforms without equivalent custom field capability. |
Gotchas
What to watch for in Formitize migrations
Issues we've hit on past Formitize migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Limited bulk export mechanism complicates migration scoping
Custom field schemas are per-account, not organizational templates
Workflow definitions do not transfer between platforms
Asset zone and GPS data requires explicit extraction
| Severity | Issue |
|---|---|
| High | Limited bulk export mechanism complicates migration scoping |
| Medium | Custom field schemas are per-account, not organizational templates |
| Medium | Workflow definitions do not transfer between platforms |
| Low | Asset zone and GPS data requires explicit extraction |
Leaving Formitize?
Where Formitize customers move next
12 destinations Formitize can migrate to.
How a Formitize migration works
Four steps, Formitize-specific
Connect
API key into Formitize. Scopes limited to read-only on the data we move.
Map
We translate Formitize-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Formitize quirks before production.
Migrate
Full migration with Formitize rate-limit handling. Rollback available throughout.
FAQ
Formitize migration FAQ
Answers to the questions buyers ask most during Formitize migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Formitize migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate Formitize.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Formitize setup and destination — written quote back within a business day.