Odoo 20 merged Field Service into Planning — and it's the right call

If you upgraded to Odoo 20 and went looking for Field Service in the apps list, it’s not missing. It’s been moved. Field Service is now a feature toggle inside the Planning module — one checkbox in settings flips on interventions, time & materials invoicing, and worksheets. Leave it off and the Planning menu stays clean.

This is the right call. More on why in a minute. First, the practical bit.

Where the toggle lives

After upgrade, Field Service no longer appears as a standalone app. It comes pre-bundled with Planning. To switch it on:

1. Open Planning.
2. Go to Configuration > Settings.
3. Under the Field Service section, tick On-site Interventions.
4. Save.

The Field Service menu items (Interventions, Worksheets, Equipment) appear inside Planning once the toggle is on. The old top-level “Field Service” menu is gone.

What you actually get

With the toggle on, Planning becomes the dispatch board for on-site work. The pieces that used to live in the standalone Field Service module are all there:

• Interventions — the work orders themselves, with planned and actual times, assigned worker, and customer site.
• Time & materials invoicing — log hours and parts on the intervention, push to a sales order, invoice in the same flow as before.
• Worksheets — the checklist or report a technician fills in on site. Studio-built worksheet templates carry across.
• Equipment — customer assets, with intervention history attached.

The functionality is the same. The data model is the same. What changed is where it sits in the menu, and the fact that you’re now scheduling field work and shift work from one calendar instead of two.

Migration from 18 or 19

If you’re upgrading an existing Field Service install, the standard upgrade carries records over:

• Existing interventions are preserved with their dates, customers, worksheets, and links to sale orders.
• Worksheet templates built in Studio survive the upgrade. Worth opening one after the upgrade to confirm fields render — Studio templates from older versions occasionally need a refresh.
• Timesheets logged against interventions stay attached.
• Custom modules that depended on industry_fsm will need their manifests updated to depend on planning instead. The old technical module is gone.

If you have customizations on top of Field Service — and most real installs do — get them tested in a staging upgrade before touching production. The merge itself is clean; bespoke code on top is where 19 → 20 upgrades historically bite.

Why this is the right direction

Most ERPs add modules to look feature-rich. Odoo has done plenty of that over the years too — every release brought new apps, and the apps list got harder to read. A small operations team running Odoo 18 today is staring at sixty-plus apps and trying to work out which seven they actually need.

Odoo 20 is the first release in a while where the headline change makes the system smaller, not bigger. Field Service into Planning is the visible example. There are quieter ones — features promoted from separate apps into core, settings consolidated, menus pruned. The pattern suggests someone at Odoo is finally optimising for “what does this look like to a small business” instead of “how many checkboxes can we list on the marketing page.”

That’s harder to ship than another module. Removing things annoys the people who built them and the people who already learned the old layout. But for the customer who logs in tomorrow morning, fewer surfaces to navigate is the actual product improvement.

If you’re on 18 or 19 and Field Service is something you use, the upgrade gives you the same tool with a better home. If you’ve never enabled it, the toggle is one click away the day you need it.