Migrate your FieldFX data
Field service management built as a Salesforce managed package with tight mobile-back-office sync. Best for mid-to-large operations in construction, manufacturing, and utilities that already run on Salesforce.
In its favor
Why people choose FieldFX
The signal that keeps FieldFX on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Deep Salesforce integration means FieldFX inherits Salesforce security, sharing models, and reporting — ideal for organizations already standardized on the platform.
Modules like FX E-Ticketing, FX Schedule & Dispatch, FX Timecards, and FX Invoicing cover the full field-to-back-office lifecycle without requiring a separate accounting integration.
Offline-capable FieldFX Mobile with Sync Engine allows technicians to work without connectivity and have data reconcile automatically when back online.
Customer Self-Service portal gives end customers secure read-and-approve access to tickets and job data without requiring a full back-office user license.
DataGuide enables configurable digital forms with validation and PDF output, supporting compliance-heavy workflows in safety inspections and regulatory maintenance.
Steep Salesforce admin and consultant requirement — organizations without dedicated Salesforce expertise struggle with custom field configuration, API limits, and package upgrades.
Quarterly push upgrades can introduce breaking changes to customizations, workflow rules, and field dependencies without warning.
API rate limits tied to Salesforce edition and per-user app limits can throttle sync-heavy operations during peak dispatch seasons.
Complex licensing model with per-module licenses (FX CPQ, FX EAM, FX Invoicing, etc.) adds up quickly as teams expand.
Mobile sync errors can cause data staleness for field crews in low-connectivity environments, with limited visibility into sync failure root causes.
Reasons to switch
Why people leave FieldFX
The recurring reasons buyers give for replacing FieldFX. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where FieldFX 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
FieldFX pricing overview
FieldFX pricing is sold as a Salesforce add-on managed package with per-module licenses. Each module — FieldFX Base Package, FX E-Ticketing, FX CPQ, FX EAM, FX Invoicing, FX Schedule & Dispatch, and FX Timecards — requires a separate license. Pricing is not publicly published and is negotiated through Salesforce account executives based on user count and module selection.
ServiceMax FieldFX
Tier 1 of 1
From $137.50 / user / month (10-user minimum)
What's included
Need help selecting your CRM?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on FieldFX's schedule — see our quote-based pricing →
What gets migrated
FieldFX object support
Object-by-object support for FieldFX migrations. Per-pair details surface during scoping.
Tickets
Fully supportedTickets are the primary work-order object in FieldFX. The Ticket object carries the core dispatch and service record and is fully accessible via the Salesforce REST API. We migrate Tickets with their status workflows and owner assignments intact.
Ticket Items
Fully supportedTicket Items are line-item records attached to Tickets, tracking parts, labor, and extended amounts via formula fields. They map cleanly between FieldFX orgs using standard Salesforce record-type and product associations.
Jobs
Mapping requiredJobs are an alternative parent object to Tickets in certain FieldFX configurations, used primarily in FX Schedule & Dispatch. Where Jobs and Tickets coexist, we preserve the parent-child linkage and flag records with no assigned Ticket for manual review.
Accounts and Contacts
Fully supportedStandard Salesforce Account and Contact objects used for customers and locations. Full field-level mapping supported; we handle both person accounts and business accounts.
Assets
Fully supportedAsset records represent installed equipment at customer locations. We migrate Asset records with their linked Account and Contact relationships and any custom Asset fields configured in the FieldFX org.
Custom Fields
Mapping requiredFieldFX allows extensive custom fields on every major object. Custom field API Names have a length limit important for FieldFX Mobile users. We preserve all custom field definitions and values; long API Names are flagged if they may cause browser errors on mobile.
FX Timecards
Mapping requiredTimecards track labor hours against Jobs or Tickets. The Timecard object and its line-item child objects are migrated, but timecard calculations on migrated records may require appointments to be rescheduled to recompute correctly.
FX Invoices and Payments
Mapping requiredFX Invoicing generates invoices from Ticket Items and maintains payment and credit memo records. We migrate invoice headers and line items; workflow state for partially-paid invoices requires manual verification post-migration.
FX Schedule & Dispatch Records
Mapping requiredScheduling data includes technician assignments, appointment windows, and route information. We preserve the scheduling records and their linkages to Tickets and Technicians, though route-optimization results are non-transferable.
DataGuide Forms and Responses
Mapping requiredDataGuide introduces Form Objects, Form Versions, Form Data Objects, and Form Response Objects. We migrate the form definitions and version history. Form Responses are linked to parent Tickets or Jobs and are migrated with their data, but the WYSIWYG form designer layout is not portable.
Files and Attachments
Mapping requiredThe Attachments feature is deprecated in FieldFX and replaced by the Files API. We migrate existing Attachment records by converting them to Salesforce ContentVersion/File records during import, preserving content and linking to parent records.
Workflow Rules (Legacy)
Mapping requiredFieldFX has migrated many legacy Workflow Rules to Flow. We identify active workflow rules at migration time and map them to their Flow equivalents, flagging any that have no direct Flow replacement for manual rebuild.
| Object | Support | Notes |
|---|---|---|
| Tickets | Fully supported | Tickets are the primary work-order object in FieldFX. The Ticket object carries the core dispatch and service record and is fully accessible via the Salesforce REST API. We migrate Tickets with their status workflows and owner assignments intact. |
| Ticket Items | Fully supported | Ticket Items are line-item records attached to Tickets, tracking parts, labor, and extended amounts via formula fields. They map cleanly between FieldFX orgs using standard Salesforce record-type and product associations. |
| Jobs | Mapping required | Jobs are an alternative parent object to Tickets in certain FieldFX configurations, used primarily in FX Schedule & Dispatch. Where Jobs and Tickets coexist, we preserve the parent-child linkage and flag records with no assigned Ticket for manual review. |
| Accounts and Contacts | Fully supported | Standard Salesforce Account and Contact objects used for customers and locations. Full field-level mapping supported; we handle both person accounts and business accounts. |
| Assets | Fully supported | Asset records represent installed equipment at customer locations. We migrate Asset records with their linked Account and Contact relationships and any custom Asset fields configured in the FieldFX org. |
| Custom Fields | Mapping required | FieldFX allows extensive custom fields on every major object. Custom field API Names have a length limit important for FieldFX Mobile users. We preserve all custom field definitions and values; long API Names are flagged if they may cause browser errors on mobile. |
| FX Timecards | Mapping required | Timecards track labor hours against Jobs or Tickets. The Timecard object and its line-item child objects are migrated, but timecard calculations on migrated records may require appointments to be rescheduled to recompute correctly. |
| FX Invoices and Payments | Mapping required | FX Invoicing generates invoices from Ticket Items and maintains payment and credit memo records. We migrate invoice headers and line items; workflow state for partially-paid invoices requires manual verification post-migration. |
| FX Schedule & Dispatch Records | Mapping required | Scheduling data includes technician assignments, appointment windows, and route information. We preserve the scheduling records and their linkages to Tickets and Technicians, though route-optimization results are non-transferable. |
| DataGuide Forms and Responses | Mapping required | DataGuide introduces Form Objects, Form Versions, Form Data Objects, and Form Response Objects. We migrate the form definitions and version history. Form Responses are linked to parent Tickets or Jobs and are migrated with their data, but the WYSIWYG form designer layout is not portable. |
| Files and Attachments | Mapping required | The Attachments feature is deprecated in FieldFX and replaced by the Files API. We migrate existing Attachment records by converting them to Salesforce ContentVersion/File records during import, preserving content and linking to parent records. |
| Workflow Rules (Legacy) | Mapping required | FieldFX has migrated many legacy Workflow Rules to Flow. We identify active workflow rules at migration time and map them to their Flow equivalents, flagging any that have no direct Flow replacement for manual rebuild. |
Gotchas
What to watch for in FieldFX migrations
Issues we've hit on past FieldFX migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
API rate limits vary by Salesforce edition and request type
Deprecated Attachments feature requires Files API migration
Workflow Rules retirement leaves automations without a migration path
Travel time calculations require appointment rescheduling post-migration
Custom field API name length causes browser errors on mobile
| Severity | Issue |
|---|---|
| High | API rate limits vary by Salesforce edition and request type |
| Medium | Deprecated Attachments feature requires Files API migration |
| Medium | Workflow Rules retirement leaves automations without a migration path |
| Medium | Travel time calculations require appointment rescheduling post-migration |
| Low | Custom field API name length causes browser errors on mobile |
Leaving FieldFX?
Where FieldFX customers move next
12 destinations FieldFX can migrate to.
How a FieldFX migration works
Four steps, FieldFX-specific
Connect
OAuth 2.0 (Salesforce connected app) into FieldFX. Scopes limited to read-only on the data we move.
Map
We translate FieldFX-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate FieldFX quirks before production.
Migrate
Full migration with FieldFX rate-limit handling. Rollback available throughout.
FAQ
FieldFX migration FAQ
Answers to the questions buyers ask most during FieldFX migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your FieldFX migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate FieldFX.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your FieldFX setup and destination — written quote back within a business day.