Migrate your Method:Field Services data
Field-service CRM built on a QuickBooks sync engine, pairing office dispatchers with mobile technicians through work orders, scheduling, and invoicing.
In its favor
Why people choose Method:Field Services
The signal that keeps Method:Field Services on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
QuickBooks-native integration eliminates double data entry for contacts, invoices, and sales receipts, which is the single most-cited reason field-service operators adopt Method:Field Services.
The two-role model (Dispatcher and Field Crew) is purpose-built for how small-to-mid field service companies actually staff their operations, making onboarding more relevant than generic CRM role assignment.
The platform offers free training sessions and a community forum where small businesses without dedicated developers can get customization help, reducing the total cost of ownership.
Unlimited contact records on all plans means growing companies are not penalized for adding customers as their service territory expands.
The drag-and-drop calendar scheduling and optimized map routing directly address the core pain of coordinating multiple technicians across job sites.
Per-user, role-based pricing scales unpredictably — adding dispatchers costs significantly more than adding technicians, and customers report sticker shock when the pricing conversation arrives.
Small companies without a developer on staff find customization time-consuming and expensive, especially when they need custom fields wired into screens beyond the defaults.
The scheduling interface has a steep learning curve; multiple reviewers note difficulty mastering the schedule view before becoming productive.
When comparing Method's per-user costs against flat-rate alternatives in the FSM space, companies with larger technician fleets report Method becomes the more expensive option at scale.
Reasons to switch
Why people leave Method:Field Services
The recurring reasons buyers give for replacing Method:Field Services. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Method:Field Services 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
Method:Field Services pricing overview
Method:Field Services uses a two-tier per-user pricing model: Dispatchers cost $44/user/month billed annually ($49 monthly), while Field Crew Technicians cost $15/user/month billed annually ($18 monthly). The role assigned to a user is determined by which packs are installed, not by a simple role dropdown, making user count and role mix the two variables that drive monthly cost.
Field Crew Technician
Tier 1 of 3
$15/user/month (annual) or $18/user/month (monthly)
What's included
Need help selecting your CRM?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Method:Field Services's schedule — see our quote-based pricing →
What gets migrated
Method:Field Services object support
Object-by-object support for Method:Field Services migrations. Per-pair details surface during scoping.
Contacts
Fully supportedMethod:Field Services offers unlimited contact records. Contacts sync bidirectionally with QuickBooks and serve as the customer anchor for all Work Orders and transactions. We migrate contacts 1:1 including standard address, phone, and email fields.
Work Orders
Fully supportedWork Orders are the central object of Method:Field Services. They capture job details, assignments, statuses, and attach to both the Dispatcher calendar view and the Field Crew mobile app. We preserve all Work Order fields and their linked customer references during migration.
Field Crew Assignments
Mapping requiredField Crew assignments link technicians to Work Orders. The Field Crew role is granted by having only the Contact Management Pack and Field Crew Pack — a pack-based role assignment that we carry forward as a role flag during migration to maintain correct permission boundaries in the destination.
Estimates
Fully supportedEstimates are created and managed before jobs are dispatched. They sync with QuickBooks as Sales Estimates or proposals. We migrate estimates with their line items, amounts, and customer associations intact.
Sales Transactions (Invoices/Receipts)
Fully supportedMethod:Field Services syncs invoices and sales receipts directly to QuickBooks. We map these transactions to the destination's invoice or payment object, preserving amounts, line items, and QuickBooks-linked customer references.
Time Tracking Entries
Mapping requiredTime Tracking entries are generated by the Field Crew mobile app and flow into QuickBooks. Entries include hours, dates, and work order associations. We migrate these but note they may need re-linking in the destination if the Work Order ID mapping changes.
Custom Tables
Mapping requiredMethod:Field Services allows users to create entirely new tables beyond the standard schema. These custom tables are documented via the MethodAPIFieldList API call. We discover all custom tables during scoping and map them individually, as they often hold industry-specific or business-critical data.
Custom Fields
Mapping requiredCustom fields can be added to existing tables via the Customize > Tables/Fields section. These fields are not automatically surfaced in screens — they must be manually added to relevant screens post-creation. We map all custom field definitions and values, but flag that destination-side screen setup may be needed.
Customer Communication History
Mapping requiredMethod stores email and transaction history against contact records. Communication logs and email campaign records migrate as notes or activity logs depending on the destination object's schema.
QuickBooks Sync Linkage
Mapping requiredMethod:Field Services maintains a live bidirectional sync with QuickBooks for contacts, transactions, and certain field values. During migration, we capture the QuickBooks IDs stored in Method records so the destination system can be reconciled with the existing QuickBooks company file.
| Object | Support | Notes |
|---|---|---|
| Contacts | Fully supported | Method:Field Services offers unlimited contact records. Contacts sync bidirectionally with QuickBooks and serve as the customer anchor for all Work Orders and transactions. We migrate contacts 1:1 including standard address, phone, and email fields. |
| Work Orders | Fully supported | Work Orders are the central object of Method:Field Services. They capture job details, assignments, statuses, and attach to both the Dispatcher calendar view and the Field Crew mobile app. We preserve all Work Order fields and their linked customer references during migration. |
| Field Crew Assignments | Mapping required | Field Crew assignments link technicians to Work Orders. The Field Crew role is granted by having only the Contact Management Pack and Field Crew Pack — a pack-based role assignment that we carry forward as a role flag during migration to maintain correct permission boundaries in the destination. |
| Estimates | Fully supported | Estimates are created and managed before jobs are dispatched. They sync with QuickBooks as Sales Estimates or proposals. We migrate estimates with their line items, amounts, and customer associations intact. |
| Sales Transactions (Invoices/Receipts) | Fully supported | Method:Field Services syncs invoices and sales receipts directly to QuickBooks. We map these transactions to the destination's invoice or payment object, preserving amounts, line items, and QuickBooks-linked customer references. |
| Time Tracking Entries | Mapping required | Time Tracking entries are generated by the Field Crew mobile app and flow into QuickBooks. Entries include hours, dates, and work order associations. We migrate these but note they may need re-linking in the destination if the Work Order ID mapping changes. |
| Custom Tables | Mapping required | Method:Field Services allows users to create entirely new tables beyond the standard schema. These custom tables are documented via the MethodAPIFieldList API call. We discover all custom tables during scoping and map them individually, as they often hold industry-specific or business-critical data. |
| Custom Fields | Mapping required | Custom fields can be added to existing tables via the Customize > Tables/Fields section. These fields are not automatically surfaced in screens — they must be manually added to relevant screens post-creation. We map all custom field definitions and values, but flag that destination-side screen setup may be needed. |
| Customer Communication History | Mapping required | Method stores email and transaction history against contact records. Communication logs and email campaign records migrate as notes or activity logs depending on the destination object's schema. |
| QuickBooks Sync Linkage | Mapping required | Method:Field Services maintains a live bidirectional sync with QuickBooks for contacts, transactions, and certain field values. During migration, we capture the QuickBooks IDs stored in Method records so the destination system can be reconciled with the existing QuickBooks company file. |
Gotchas
What to watch for in Method:Field Services migrations
Issues we've hit on past Method:Field Services migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Role-based pricing means Dispatchers cost 3× Field Crew
API daily rate limits scale with active license count
Custom fields require manual screen assignment post-creation
Work Order and Field Crew apps are separate pack dependencies
| Severity | Issue |
|---|---|
| High | Role-based pricing means Dispatchers cost 3× Field Crew |
| Medium | API daily rate limits scale with active license count |
| Medium | Custom fields require manual screen assignment post-creation |
| Medium | Work Order and Field Crew apps are separate pack dependencies |
Leaving Method:Field Services?
Where Method:Field Services customers move next
12 destinations Method:Field Services can migrate to.
How a Method:Field Services migration works
Four steps, Method:Field Services-specific
Connect
API key (per-account credentials, documented at developer.method.me) into Method:Field Services. Scopes limited to read-only on the data we move.
Map
We translate Method:Field Services-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Method:Field Services quirks before production.
Migrate
Full migration with Method:Field Services rate-limit handling. Rollback available throughout.
FAQ
Method:Field Services migration FAQ
Answers to the questions buyers ask most during Method:Field Services migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Method:Field Services migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate Method:Field Services.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Method:Field Services setup and destination — written quote back within a business day.