How to switch from Jobber to another field-service app (the migration playbook)

Switching off Jobber feels like a software decision, but the part that actually goes wrong is the data move. On paper Jobber is easy to leave: an admin can export your client list to a CSV and that file imports into more or less any competitor. The trouble is everything that is not the client list — the recurring schedules, the price book, and the automations you have wired up over the years. None of that rides along in the export, and a migration that treats the CSV as “the data” is a migration that lands the crew in a half-built app during a busy week. The fix is to plan the move around what you rebuild, not around what exports.

A funnel to name before you read on: the free tools on this page come from the same team building Fieldwynn, the small-crew field-service app we steer people toward. Fieldwynn is still pre-launch and taking early-access signups, so there is no product pitch here, no Fieldwynn price, and no feature claim, just a waitlist link at the end you can take or leave. Where we point you at a tool, it earns its place by being useful to your move off Jobber whether or not you ever look at ours. Before anything else, pin the number you are trying to beat: the Jobber pricing calculator gives you your current all-in monthly bill, so you can judge later whether the switch actually paid for the work it took.

Start with what you actually own

The first job is to take inventory before you shop for software. Open Jobber and list the things you depend on every day, because each one falls into one of two buckets: data that exports as a clean file, or configuration that lives only inside Jobber and has to be re-created somewhere else.

Your client list is the clean part. An admin user exports it from the Clients area as a CSV or vCard, and Jobber includes the contact details, property addresses, tags, and any custom fields you added; if your book is large, the export arrives as several files, because each one caps at roughly 1,500 rows. That CSV is the universal hand-off format — every serious field-service tool has a client importer that reads it. Invoices and job history are a step down: they come out as flat report exports, which are fine to keep as an archive but rarely re-import into another tool as live, editable records. So your billing history stays readable, but it does not become the new app’s billing history.

Everything else — the schedule, the recurring plans, the price book, the automations — is configuration you rebuild by hand. That is the work, and naming it now is what keeps the cutover honest.

What exports clean, and what you rebuild

Here is the same split laid out as a checklist you can work down. Treat the left column as “download it” and the right column as “set aside a block of time.”

Read the table and the shape of the project is obvious: the headline migration (“export your clients”) is the smallest line on it. The rows that take real time are recurring jobs, the price book, and automations — which is exactly why the next section gives each one its own pass.

Rebuild the three things that run your week

These three are the difference between a tool you have populated and a tool that actually runs the business. Do them deliberately.

Recurring jobs. This is the asset you cannot afford to break, because the recurring book is what keeps billing after you stop touching it. Every plan on recurring billing in Jobber — the weekly mow, the monthly pool service, the quarterly pest visit — has to be re-created in the new app with the right cadence, price, and start date, then matched back to the right client from your imported list. Work from a Jobber export of your recurring jobs as a worksheet and check them off one by one; a single missed plan is a customer who silently stops getting billed. This is also the moment to prune: cancelled or dormant plans you have been carrying do not need to come across.

The price book. Your products-and-services list exports as a flat list, but the wiring — which line items attach to which service, your default quantities, your tax rules — does not. Re-enter the catalog, then rebuild those links. Migrating is a good excuse to clean it up: kill duplicate line items, refresh stale rates, and fold the result into your overhead recovery rate so the prices you load already carry their share of fixed cost instead of quietly eating margin.

Automations and templates. The reminder texts, the “on my way” messages, the review requests, the follow-up sequences — all of it is rebuilt by hand. The upside is a clean slate: most shops are running automations they set up once and never revisited, so rebuild only the ones that earn their keep and let the rest go.

Before you commit, confirm the move pays for itself

Migration is real work, so it should buy you something real — a genuinely lower all-in cost, a capability you were missing, or a pricing model that fits how you hire. It is not worth a weekend to shave a few dollars off a sticker. The complaint that most often starts this search is cost: one operator reviewing Jobber on Capterra flagged that “some of the best features are locked behind higher tiers, which can feel steep for a small business still growing” (Capterra, Oct 2025). Jobber is a well-built, widely used tool that plenty of crews are right to keep; the question is only whether it still fits yours. If tier-gating is what pushed you, the real test is whether the destination actually unlocks what you were paying up for; a lower sticker on its own settles nothing. Put your actual crew size and card volume into the all-in calculator below and compare the destination against the Jobber number you pinned earlier; if the gap is thin, the honest answer may be to stay.

If you have not settled on a destination yet, that is a separate decision from the move itself — work it through our Jobber alternatives breakdown and the broader best field-service software guide, or read a head-to-head like Jobber vs Housecall Pro. Decide where first; this playbook is about getting there cleanly.

Time the cutover

When you flip matters as much as how. Two timing levers do most of the work.

The first is your contract. Jobber’s lowest advertised rates assume an annual prepay, with month-to-month billing costing more — which means a mid-year switch can forfeit months you have already paid for. Line the cutover up with your renewal date so you are not paying two tools at once any longer than the brief overlap below requires.

The second is your calendar. Pick your slowest stretch of the year, so that if something hiccups it lands when you have the slack to fix it.

Run both tools in parallel for one cycle

Do not hard-cut. For one full billing cycle, run Jobber and the new app side by side: enter new jobs in both, send a few real invoices through the new tool, and let at least one round of recurring charges actually fire. A parallel run is how you catch the quiet failures — a recurring plan with the wrong cadence, a tax rule that did not carry, a work order that never closed out — while Jobber is still there to fall back on. Reconcile the two at the end of the cycle: the invoices, the recurring charges, and the schedule should match. Only when a complete cycle has closed clean in the new app do you cancel Jobber.

This overlap is also your data backstop. Keep the Jobber export files and a copy of your archived invoice history somewhere safe even after you cancel; you may need to reference old records long after the subscription lapses, and once the account closes that data is harder to retrieve.

Retrain the crew during the overlap

The software change your office feels is small; the change your field techs feel is the app on their phone. Whatever the new tool is, the buttons moved, the job flow is different, and the muscle memory is gone. Walk the crew through it during the parallel run, on real jobs, while there is still a familiar system to fall back on — well before the Monday you finally cancel Jobber. Have one tech run a full day in the new app and report what is awkward, fix the setup around their feedback, then roll it to everyone. A migration that nails the data and fumbles the crew still costs you a rough first week; doing the training inside the overlap is what makes the switch a non-event in the field.

The honest note on Fieldwynn

The app behind the disclosure at the top is Fieldwynn, and the band at the foot of this page is its early-access list. Because Fieldwynn is pre-launch, the honest version of this is short: there is no live product to migrate into yet, so treat the link as a way to be first in line and to carry your setup intent to launch day. Everything in this playbook works for whichever live tool you choose — the export, the rebuild, the parallel run, the retraining are vendor-neutral mechanics. If the thing pushing you off Jobber is the per-seat meter climbing with every hire — one Jobber reviewer on Capterra called “paying for extra users over the included 15 … a tough pill to swallow” (Capterra, Feb 2026) — that is worth telling us when you sign up; it is the problem Fieldwynn is being designed around, and it is also, plainly, why we would like you on the list. Weigh that the way you would weigh any pitch.

So the playbook, in one line: inventory what you own, export the client list, rebuild the recurring jobs, price book, and automations by hand, confirm the destination actually beats your Jobber bill, time the cutover to your renewal and a slow week, run both tools in parallel for a full cycle, retrain the crew inside that overlap, and cancel only once a clean cycle has closed. Do it in that order and switching off Jobber becomes a planned project with a date on it, run on your own schedule.