FieldRoutes alternative · switch from FieldRoutes · leave PestRoutes
Leave FieldRoutes in a weekend
Native FieldRoutes / PestRoutes import — CSV by default, API if you have keys. No paid migrator. Dual-run until cutover. Honest about what waits: payment tokens and a full chemical archive. Leaving PestPac instead? That is a separate importer.
Onboarding opens with FieldRoutes Import ready. Re-runs never duplicate accounts. Switcher pricing — native import is free; no fake price table. Leave PestPac
What lands day-1
A FieldRoutes shop should be runnable on Monday: customers, active subscriptions, upcoming jobs, techs, and open AR. That is the bar. Everything else is named below so we do not oversell a weekend.
Customers and service locations
Names, phones, emails, and addresses so the book of business is actually yours on Monday.
Active subscriptions
Recurring programs with frequency, next service, and charge — the engine that generates tomorrow's jobs.
Upcoming jobs
Appointments land on the schedule so assigned techs see the route in the PWA.
Technician roster
Employees become one-click invites. We never silently create user accounts from a FieldRoutes export.
Open AR and invoices
Tickets and aging come across so you can explain the opening balance — not pretend it matches to the penny.
Honest about later
We would rather lose a signup than inherit a trust problem on Tuesday.
Payment tokens / saved cards
Card vault migration is not day-1. FieldRoutes' Data Declaration covers a Payments token handoff (typically <=10 business days, no fee) via FreeMe@FieldRoutes.com. Autopay does not work in RouteWorks until a Stripe customer and payment method exist. We will not pretend otherwise.
Full chemical archive
The API path imports chemical-use records tied to appointments. A complete chemical history from CSV is later — do not plan a compliance audit off a weekend report-pack.
Contracts and documents from CSV
Contracts and signed agreement files come across on the API path. A weekend report-pack does not land the document vault. Connect credentials later if you want those files.
CSV first — no API key required
Self-serve FieldRoutes exports are a right, not a favor. Pull the report-pack you already have access to: customer list, subscriptions, appointments, tickets / aging. Optional: service types, notes, employees. Preview the mapping, then commit.
If the in-app reports are thin, cite the FieldRoutes Data Declaration and email FreeMe@FieldRoutes.com.
API is the advanced path
Credentials are often support-issued. When you have them, the importer streams in dependency order and keeps a daily incremental sync for dual-run. Extra surfaces the CSV path does not claim:
- Contracts and signed agreements
- Documents
- Reviews
- Tasks
- Chemical-use records (not a full archive)
- Daily incremental sync for dual-run
A weekend, not a quarter
Friday
Claim your data
Export the reports you can already pull (customers, subscriptions, appointments, tickets). If self-serve is thin, email FreeMe@FieldRoutes.com and cite their Data Declaration.
Saturday
Preview, then commit
Create your RouteWorks company, install FieldRoutes Import, and upload the CSVs. Headers are fingerprinted fuzzily — you preview counts, coverage, and unmapped columns before anything is written.
Sunday
Invite techs, check Monday
Invite the roster. Confirm tomorrow's jobs, open AR, and active subscriptions. Dual-run FieldRoutes until the route looks right.
FAQ
Do I need FieldRoutes API credentials, or is CSV enough?+
CSV / report-pack is the default self-serve path. Most shops cannot get API keys without a FieldRoutes rep. Upload customers, subscriptions, appointments, and invoices — no key required. The API path is advanced: live incremental sync plus contracts, documents, reviews, tasks, and chemical-use records. Start on CSV; connect the API later if you want dual-run sync.
What about contracts and signed agreements?+
Contracts and document files come across on the API path. CSV day-1 is built to make the operation runnable — accounts, recurrences, schedule, and open AR. You can connect the API or re-run later; every external record is tracked in an ID map so nothing duplicates.
Can I dual-run FieldRoutes and RouteWorks?+
Yes. After an API backfill, a daily incremental sync picks up anything that changed in FieldRoutes so you can operate both systems until cutover. CSV re-uploads update in place on preserved FieldRoutes IDs (or a stable key when IDs are missing). Run both until Monday's routes look right — then turn FieldRoutes off.
Do you import PestPac?+
Not this plugin. FieldRoutes Import is FieldRoutes / PestRoutes only. PestPac has its own CSV importer and a public Leave PestPac page at /switch/pestpac. We will not claim this plugin reads PestPac files.
What about saved cards and autopay?+
Payment tokens are not a silent import. Request the FieldRoutes Payments token handoff through their Data Declaration (FreeMe@FieldRoutes.com; typically <=10 business days, no fee). Until a Stripe customer and payment method exist in RouteWorks, autopay stays off. Open AR still imports so you can collect.
What does RouteWorks cost?+
Native FieldRoutes import is free — no paid migrator. We do not publish a fake price table. Start free, bring the book, and talk to us about the ongoing platform from what actually landed. Details are on /pricing.
Switch from FieldRoutes this weekend
Start free, name the company, and land on FieldRoutes Import. Leave PestRoutes when the Monday route looks right — not when a consultant clears a backlog. See switcher pricing.