With Odoo 20, the Field Service app disappears. Its functions are not lost: they join Planning, with a real-time map of technicians and travel time counted between two appointments. For heating, chimney-sweeping or maintenance companies that use Field Service today, this is a change to prepare for. Here is what changes, how to enable it, and what to plan for.
1. The problem: a schedule that forgets the road
The head of a team of technicians asks two questions several times a day: “Where are my people?” and “Who can take this emergency?” Up to Odoo 19, interventions lived in one app (project tasks), team scheduling in another, and the journey between two customers appeared nowhere. The result: days that are impossible on paper, which fall apart from the second appointment.
💡 Key takeaway
A technician schedule that does not count the road is a wrong schedule, however full it looks.
2. Enabling “Field Service” in Planning
It all starts from Planning > Configuration > Settings. In the “Operations” block (title not translated in V20), tick “Field Service”. Further options then appear:
- “Worksheets”: custom intervention forms;
- “Customer Report”: the report handed to the customer, signed on site and sent by email. It only appears if “Worksheets” or “Billing” is enabled;
- “Geolocation”: the technicians’ position during their working hours, recorded at the start and end of each slot;
- “Equipment”: the customer’s equipment and its intervention history;
- in the sales block, “Billing”: the time and materials invoiced to the customer.
Each intervention then becomes a Planning slot, in the same Gantt chart as the rest of the teams.
💡 Key takeaway
A single box enables field service; the options that follow are chosen according to your trade, not all by default.
3. The map, the journey, the emergency, the signature
The map. A new “Maps” menu offers “Live Map” (with geolocation enabled) and “By Resource”. You see who is where, without phoning.
The journey. Planning calculates a “Travel time” between two slots of the same technician. The detail matters: with a Mapbox token (General Settings, “Mapbox” setting, “Token” field), the time is estimated by road. Without a token, Odoo falls back on a straight-line estimate at an average speed of 60 km/h: useful for a rough idea, misleading in the Ardennes as in central Brussels.
The emergency. With the Helpdesk app, a ticket carries a “Plan Intervention” button: the slot is created from the ticket and takes its place in the planning.
The signature. On their phone, the technician taps “Sign Report”, the customer signs, then “Complete” closes the intervention.
💡 Key takeaway
Without a Mapbox token, travel time is a straight line at 60 km/h: configure it before trusting the planning.
⚔️ The Match: Field Service in Odoo 19 vs Planning in Odoo 20
| Criterion | Odoo 19 | Odoo 20 |
|---|---|---|
| Where an intervention lives | Field Service app, separate | Planning slot |
| Travel time | Not counted | Calculated between two slots |
| Technician position | — | “Live Map” |
| Report signed on site | Yes | Yes (“Sign Report”) |
| Habits and customisations | — | To be carried over during migration |
Based on the Odoo 20 Enterprise source code (planning_field_service, helpdesk_planning_field_service) and the official release notes, October 2026.
4. Prerequisites, limits and migration
- Odoo 20 Enterprise: field service does not exist in Community.
- A Mapbox account for realistic journeys: it is a third-party service, with its own terms of use.
- Technician geolocation touches on their privacy: inform them, limit it to working hours (which is what Odoo provides for) and document it with regard to the GDPR.
- Clean customer addresses: without reliable geographic coordinates, neither the map nor the journeys hold up.
- Migration: the Field Service app no longer exists in V20. Screens change, habits too, and everything that was added around it (Studio, reports, automations) has to be reviewed. This is tested on a copy of the database, never live.
Who is it for? All SMEs with travelling technicians: heating, chimney sweeping, maintenance, cleaning, installation. And first of all those that use Field Service today.
💡 Key takeaway
Moving to Odoo 20 is not a simple update for Field Service users: it is a small project, to be planned.
The Verdict: one screen to know who is where, journey included
Merging Field Service into Planning finally makes technician scheduling realistic. It also imposes a migration to prepare: options to choose, Mapbox token, addresses to clean up, customisations to review. An
Odoo process audit
draws up that list before it lands on you, and
Odoo training
puts the office and the technicians at ease with the new screens.
Do you use Field Service today? Ask us for your migration plan.
With Odoo 20, the Field Service app disappears. Its functions are not lost: they join Planning, with a real-time map of technicians and travel time counted between two appointments. For heating, chimney-sweeping or maintenance companies that use Field Service today, this is a change to prepare for. Here is what changes, how to enable it, and what to plan for.
1. The problem: a schedule that forgets the road
The head of a team of technicians asks two questions several times a day: “Where are my people?” and “Who can take this emergency?” Up to Odoo 19, interventions lived in one app (project tasks), team scheduling in another, and the journey between two customers appeared nowhere. The result: days that are impossible on paper, which fall apart from the second appointment.
💡 Key takeaway
A technician schedule that does not count the road is a wrong schedule, however full it looks.
2. Enabling “Field Service” in Planning
It all starts from Planning > Configuration > Settings. In the “Operations” block (title not translated in V20), tick “Field Service”. Further options then appear:
- “Worksheets”: custom intervention forms;
- “Customer Report”: the report handed to the customer, signed on site and sent by email. It only appears if “Worksheets” or “Billing” is enabled;
- “Geolocation”: the technicians’ position during their working hours, recorded at the start and end of each slot;
- “Equipment”: the customer’s equipment and its intervention history;
- in the sales block, “Billing”: the time and materials invoiced to the customer.
Each intervention then becomes a Planning slot, in the same Gantt chart as the rest of the teams.
💡 Key takeaway
A single box enables field service; the options that follow are chosen according to your trade, not all by default.
3. The map, the journey, the emergency, the signature
The map. A new “Maps” menu offers “Live Map” (with geolocation enabled) and “By Resource”. You see who is where, without phoning.
The journey. Planning calculates a “Travel time” between two slots of the same technician. The detail matters: with a Mapbox token (General Settings, “Mapbox” setting, “Token” field), the time is estimated by road. Without a token, Odoo falls back on a straight-line estimate at an average speed of 60 km/h: useful for a rough idea, misleading in the Ardennes as in central Brussels.
The emergency. With the Helpdesk app, a ticket carries a “Plan Intervention” button: the slot is created from the ticket and takes its place in the planning.
The signature. On their phone, the technician taps “Sign Report”, the customer signs, then “Complete” closes the intervention.
💡 Key takeaway
Without a Mapbox token, travel time is a straight line at 60 km/h: configure it before trusting the planning.
⚔️ The Match: Field Service in Odoo 19 vs Planning in Odoo 20
| Criterion | Odoo 19 | Odoo 20 |
|---|---|---|
| Where an intervention lives | Field Service app, separate | Planning slot |
| Travel time | Not counted | Calculated between two slots |
| Technician position | — | “Live Map” |
| Report signed on site | Yes | Yes (“Sign Report”) |
| Habits and customisations | — | To be carried over during migration |
Based on the Odoo 20 Enterprise source code (planning_field_service, helpdesk_planning_field_service) and the official release notes, October 2026.
4. Prerequisites, limits and migration
- Odoo 20 Enterprise: field service does not exist in Community.
- A Mapbox account for realistic journeys: it is a third-party service, with its own terms of use.
- Technician geolocation touches on their privacy: inform them, limit it to working hours (which is what Odoo provides for) and document it with regard to the GDPR.
- Clean customer addresses: without reliable geographic coordinates, neither the map nor the journeys hold up.
- Migration: the Field Service app no longer exists in V20. Screens change, habits too, and everything that was added around it (Studio, reports, automations) has to be reviewed. This is tested on a copy of the database, never live.
Who is it for? All SMEs with travelling technicians: heating, chimney sweeping, maintenance, cleaning, installation. And first of all those that use Field Service today.
💡 Key takeaway
Moving to Odoo 20 is not a simple update for Field Service users: it is a small project, to be planned.
The Verdict: one screen to know who is where, journey included
Merging Field Service into Planning finally makes technician scheduling realistic. It also imposes a migration to prepare: options to choose, Mapbox token, addresses to clean up, customisations to review. An
Odoo process audit
draws up that list before it lands on you, and
Odoo training
puts the office and the technicians at ease with the new screens.
Do you use Field Service today? Ask us for your migration plan.