Two people mapping out a process on a whiteboard
Back to Blog
Setup & Configuration
Ahmed Abd El Dayem, Co-Founder & CTO
8 min read
Published · Updated

Migrating to FieldRoutes: Lessons from Companies Who Did It Right

A move to FieldRoutes succeeds or fails on its scheduling data. What a migration must carry across, which defaults to question, and how to cut over without losing service history.

In short

Migrating to FieldRoutes goes well when the scheduling data arrives as carefully as the customer list. Bring over each subscription's frequency, last service date, preferred days, time window and preferred technician, plus technician skills and licenses. Question every default before import, build route templates first, train technicians to check in and out, and keep the old system readable for one full service cycle.

  • Names and addresses move easily. Last service dates, frequencies and preferred technicians decide whether routes work afterwards.
  • Every time window and preferred technician set by default at import becomes a constraint on every route.
  • Skills and licenses that never reach FieldRoutes let anyone take any job.
  • Build route templates and train check-in and check-out before the first live week.
  • Keep the old system readable for one full service cycle, so the first quarterly round can be checked.

Migrating to FieldRoutes (formerly PestRoutes) is usually planned around the customer list. Names, addresses, phone numbers and balances matter, but they are the easy part. Whether the first month of routes works depends on the scheduling data: when each customer was last serviced, how often they are due, which days and times they were promised, and who may serve them.

We build PestRouting, a route planner that reads subscriptions, appointments and technicians from FieldRoutes every night and plans routes from them, so the quality of that data decides what any plan can do. The lessons below come from reading that data, from our published results and from FieldRoutes' own documentation. They describe what a migration has to get right. They are not stories about particular companies.

The fields that decide your routes after go-live

DataWhere it lives in FieldRoutesWhat goes wrong when it arrives wrong
Frequency or custom scheduleSubscription tab, Recurring Services, FrequencyVisits fall due on the wrong rhythm, or twice
Last service dateAppointment historyThe next visit has nothing to count from
Preferred daysSubscriptionVisits land on days the customer never agreed to, or stay locked to days nobody asked for
Arrival window (AM, PM, anytime or timed)Subscription and appointmentEvery unnecessary window pins a stop to part of the day
Preferred technicianSubscription, Scheduling Options, Preferred TechCustomers lose their technician, or keep one from an old territory
Skills and licensesSkills preferences and each user's Licenses tabAnyone may take termite or WDO work
Service type and its lengthService typesDays are planned too full or too empty
Notes and flagsCustomer card: red notes, office notes, flagsTechnicians arrive without the gate code or the dog warning

Keep the service history along with the customer list

Losing customer data in a software switch rarely means losing names. It means losing the history that makes the next visit correct. A quarterly customer's next service counts from the last one. Without that date, someone ends up setting due dates by hand, and the first quarter of routes shows it.

History matters for more than due dates. PestRouting, for example, works out the usual weekday of a weekly or monthly visit from the last year's visits when the subscription names no preferred day. A migration that brings over three months of history quietly loses that pattern. Before cutover, make sure you can export:

  • Every subscription with its frequency, service type, price per visit, preferred days, time window and preferred technician.
  • The appointment history with dates, technicians, service types and completion status, at least one full year, so seasonal customers arrive complete.
  • Notes, flags and documents per customer, checked after import in the technician's mobile app.
  • Read access to the old system through at least one full service cycle. For quarterly customers that is three months.

Question every default before it becomes a constraint

Migrations tend to fill empty fields with defaults: a time window applied to every subscription, a preferred technician copied from whoever served the account last, preferred days taken from the last visit. Each looks harmless on one record. Across a route book, they decide how much freedom any plan has.

In the route book behind our more production, same team result, most time windows, preferred technicians and weekday locks turned out to have been set by default. Keeping only the ones customers had asked for is what freed the routes. A migration is the cheapest moment to make that distinction, because every record passes through someone's hands anyway.

Preferred technicians deserve the most care. FieldRoutes keeps them under Scheduling Options on the subscription, and its scheduling tools, from Fill Routes to the Job Pool and Map View, filter and assign by them. Import them only where a customer relationship is real.

Key insight: A default imported once becomes a rule every future plan has to obey. Ask "did a customer ask for this?" before the import, while it costs nothing to say no.

Skills and licenses have to arrive as data

Licenses are easy to forget in a migration because the office knows who holds what. The system does not. FieldRoutes stores licenses per technician with their states and linked skills, and a skill only affects scheduling while Utilize in Scheduling is on.

In one of our published audits, skills had never been entered in FieldRoutes, so the first replan let anyone take any job until they were added. In an audit that costs nothing. On a live route it sends an unlicensed technician to a termite job. Skill tags in FieldRoutes covers how to set them up so they hold.

Build route templates before the first live week

FieldRoutes builds each day from route templates: start and end times in 24-hour format, the length of each spot, a standard duration, a buffer for initial appointments, and blocked times for lunch or meetings. Set them up per team before go-live, along with your territories, rather than on the first Monday.

If you plan to add an outside planner that writes routes back, build the templates with that in mind. PestRouting writes only onto routes that allow API scheduling, and the route group it creates missing routes in needs spots of equal length, each 15 minutes or less. FieldRoutes' own auto scheduler also has to be off for routes an outside planner books, or the two book against each other.

Train technicians on check-in and check-out first

The FieldRoutes Mobile app shows technicians their routes, by default from one day back to three days ahead, with service history, notes and flags for every stop. It also logs arrival and departure when technicians check in and out.

Those two taps matter more than any other habit after a migration. They are where actual service times come from, and every later plan, report and audit depends on them. In the same published audit, logged check-ins were too short to trust, so standard lengths had to stand in for them.

Payments and accounting have their own dates

Two financial details deserve a line of their own in the cutover plan. The QuickBooks Online integration always starts on the first of a month and cannot be moved once that date has passed, as our FieldRoutes and QuickBooks guide explains. And if the migration comes with an acquisition, card tokens in FieldRoutes Payments move to the new owner's merchant account only through a new application and a token transfer, as FieldRoutes describes in its tips for acquiring companies.

A cutover sequence that protects the first cycle

  1. Freeze subscription changes in the old system a few days before the export.
  2. Export subscriptions, appointment history, notes and documents, and keep the files.
  3. Clean before import: duplicate customers, missing service addresses, inactive subscriptions and defaults nobody asked for.
  4. Import, then check a sample of customers of each frequency against the old system: next due date, preferred days, time window and technician.
  5. Set up route templates, skills and licenses, with Utilize in Scheduling on where licenses matter.
  6. Train technicians on check-in and check-out before the first live day, then train the office on scheduling.
  7. Go live at the start of a month and keep the old system readable through the first full service cycle.

Frequently asked questions

How do I switch pest control software without losing my customer data?

Export more than the customer list. Bring every subscription with its frequency, preferred days, time window and preferred technician, at least a year of appointment history, and all notes and documents. Check a sample after import against the old system, and keep the old system readable for one full service cycle.

What should we clean up before migrating to FieldRoutes?

Clean duplicate customers, missing or wrong service addresses and inactive subscriptions first. Then review the defaults: time windows, preferred technicians and preferred days that no customer asked for. Finally, make sure technician skills and licenses are entered in FieldRoutes, where the scheduling tools can use them.

How does FieldRoutes support technician dispatching and mobile field operations?

Dispatchers schedule onto route templates with tools such as Fill Routes, the Job Pool, Map View and Optimize. Technicians work from the FieldRoutes Mobile app, where they see their routes, check in and out, read notes and service history, log products used and update billing information.

When can we use a route planner after migrating to FieldRoutes?

PestRouting can plan as soon as subscriptions, technicians and routes are in FieldRoutes and the connection is set up. Its free audit replans a past month as it actually ran, so it needs one full month of routes run in FieldRoutes first.

How long should we keep the old system after migrating?

Keep it readable through at least one full service cycle, which is three months for quarterly customers. That lets the office check every recurring customer's first visit in FieldRoutes against the history it came from.

Once your first full month has run in FieldRoutes, a free route audit replans it and shows what the new setup leaves on the table.

Ran into a word you would define differently? The glossary says how we use every term on this page.

Share:
Ahmed Abd El Dayem

Written by

Ahmed Abd El DayemCo-Founder & CTO, PestRouting

Responsible for product, engineering and data security at PestRouting, including the route planner and the FieldRoutes integration.

Ahmed on LinkedIn

Liked this? Get the same analysis on your routes.

30 minutes. We listen first. Then you decide if a real audit makes sense. No pitch, no pressure.

Related articles

View all articles