Field Service to Project Operations: Is Your Transition on Track for February 28, 2027?

What is changing, in one picture

From March 1, 2027, work order costs and revenue can no longer post straight into F&O project journals; they must travel Field Service → Project Operations → Finance.

The legacy path creates a subproject per work order and writes journals directly in F&O. The new path turns work order usage into material usage logs and time entries in Project Operations, approves them into actuals, and sends integration journal lines to Finance (Microsoft: integration overview).

Three supported ways to run the new integration

Source: Field Service integration with Project Operations overview.

What the new integration requires

Microsoft's setup guide lists these prerequisites and decisions. Every one of them is a task in your plan.

• Field Service version 8.8.142.0 or later and Project Operations version 4.162.0.0 or later.

• The legacy integration uninstalled before the new one is enabled (uninstall guide).

• Project Operations dual-write map versions installed and "manage stocked products" activated.

• The ProjInventOnHandEntity virtual entity enabled in Dataverse.

• The integration package installed from the Power Platform admin center; a recurring Power Automate flow runs under the installing user, so check that user's licensing.

• Two business decisions: whether material usage logs from Field Service are auto-approved, and whether price and cost come from Field Service (default) or Project Operations price lists.

• A mobile check: offline profiles installed by the integration override the out-of-the-box profiles, so customized offline profiles need retesting.

Progress check: where should you be today?

By the end of September 2026 you should know the deadline and have an impact assessment under way; by October 23 that assessment should be signed off.

Each stage ends in a gate. If you are more than one stage behind the date shown, treat the program as at risk and read the red-zone options later in this article.

Twelve-question self-assessment

Score each question: Green = 2, Amber = 1, Red = 0. A total of 18–24 means on track, 10–17 means at risk, and under 10 means act this week.

Haven't started yet? The issues you are probably facing

The biggest risk is not the technology; it is a compressed calendar meeting a hard cutover. If work order transactions stop reaching F&O on March 1, 2027, billing, inventory and month-end close all feel it the same week.

What happens if you do nothing: after February 28, 2027 the legacy integration is no longer available. Expect manual journal entries, delayed invoices, inventory that no longer matches the field, and a harder audit conversation about controls.

You don't have to boil the ocean

The goal before February 28 is narrow: make work order costs, revenue and inventory reach Finance correctly through the new path. Everything else can wait for a Phase 2 in spring 2027.

We call this the minimum viable transition. Ten rules keep it small:

1. Like-for-like first. Reproduce today's financial outcome through the new path; improvements come after March.

2. Pick the lightest deployment model that works. If you only need work order financials in F&O, the Field Service + Finance + Supply Chain model avoids a full Project Operations rollout.

3. Configure before you customize. Keep Field Service as the price and cost source (Microsoft's default) unless you have a clear reason not to.

4. Close, don't migrate. Drive open work orders to completion before cutover; migrate only the ones that cannot close.

5. Leave history where it is. Posted journals stay in F&O; add a source work order reference only if audit needs it.

6. Test the money, not every screen. Focus acceptance testing on the 10–15 scenarios that post to the general ledger.

7. Train by role, briefly. Technicians barely change; dispatchers, project accountants and finance get short, focused sessions.

8. Freeze new requests on work order tables until after go-live.

9. Decide in 48 hours. A weekly steering meeting and a named decision owner stop design from drifting.

10. Keep a buffer. Go live by mid-February so a two-week slip still lands before the deadline.

The end-to-end plan

A medium-complexity transition that starts on October 5, 2026 can go live on February 8, 2027 and close hypercare by February 26. Six phases run in sequence, three lanes run alongside, and five gates stop problems from travelling downstream.

The governance lane spans the whole program; licensing and environments run through Assess and Design; data migration runs from Build into Test; training runs from Test through cutover.

What each phase looks like

The holiday freeze from December 21 to January 1 is built in: no build work is planned for those two weeks, and January UAT is scheduled after year-end close.

The eight workstreams

Eight workstreams, each with one named owner, cover the whole transition. In a mid-market company several can share an owner, but none can be skipped.

The companion Excel plan maps every task to one of these workstreams, with owners, dates and status columns you can track weekly.

Timeline: October 2026 to February 2027

Starting on October 5 puts go-live on February 8, 2027, with about three weeks of buffer before Microsoft's end date.

The critical path runs through design sign-off (G2, November 13), build complete (G3, December 18) and go/no-go (G4, February 3). A slip at G2 or G3 eats the buffer first; a slip past mid-February means using the red-zone options below.

Key milestones

• G1 scope agreed: October 23, 2026

• G2 design signed off: November 13, 2026

• G3 build complete in sandbox: December 18, 2026

• Holiday freeze: December 21, 2026 to January 1, 2027

• G4 go/no-go: February 3, 2027

• Go-live: Monday, February 8, 2027 (cutover over the weekend of February 6–7)

• Hypercare closes: February 26, 2027

Estimation matrix: how long will yours take?

Most low-to-medium scopes need 8–16 working weeks to go-live; the combination of complex data and heavy customization is what pushes a program past the deadline.

Read across to your customization level and up to your data level. The "latest start" counts back from a February 12 go-live, adds the two-week holiday freeze, and leaves two weeks of buffer before February 28. The reference plan above is the medium/medium cell.

Score your data complexity

Use the highest level that two or more rows reach.

Score your customization and integration complexity

These thresholds are rules of thumb from mid-market Dynamics 365 programs, not Microsoft guidance. A two-week assessment replaces them with your real numbers.

In the red zone? Your options

If your cell in the matrix is red, the answer is not to work faster; it is to move less. These levers are listed in the order we would pull them.

1. Cut to the minimum viable transition. Keep only the flows that post money or move inventory; send reports, enhancements and cosmetic customizations to Phase 2.

2. Choose the lighter deployment model. If you do not need project managers working in Project Operations, the Field Service + Finance + Supply Chain model reduces design, licensing and training.

3. Overlap design and build. Run two-week "configure as you design" sprints so the sandbox shows decisions as they are made.

4. Shrink the cutover. Close out open work orders aggressively in January so fewer need to move.

5. Add capacity early, not late. A surge team in November can still change the outcome; one in February can only report on it.

6. Prepare a controlled interim process. Design, with your controller, a documented and time-boxed way to post work order usage to F&O if go-live slips past February 28. Treat it as insurance, not the plan.

One thing not to do: plan around an extension. Microsoft announced this deprecation on December 1, 2025, and its policy is that deprecated features keep working only until the stated removal date.

Your next 30 days

The next four weeks decide whether February is a controlled go-live or a scramble. Everything on this list can start with the team you already have.

By Oct 2, 2026

• Name an executive sponsor and a single program owner

• Score the twelve-question self-assessment with IT, service operations and finance in the room

• Check Field Service and Project Operations versions in every environment

• Protect your current test environment; do not rebuild it from scratch

By Oct 9, 2026

• Inventory every dual-write map, plugin, flow, script, integration and report that touches work orders

• Score your data and customization complexity and find your cell in the matrix

By Oct 16, 2026

• Choose a deployment model and request license quotes

• Book your delivery team through March 2027

• Book finance and dispatch testers for the last two weeks of January

By Oct 23, 2026

• Sign off the assessment, the must-do scope and the plan (gate G1)

• Load the companion Excel plan, assign an owner to every workstream and start weekly steering

Need a second pair of eyes?

Managed ERP Services is a Houston-based Dynamics 365 consultancy focused on project recovery, hypercare and managed services across Field Service, Project Operations and Finance and Operations. Our Field Service to Project Operations Readiness Assessment takes two weeks and gives you:

• A complete inventory of what the legacy integration touches today

• Your data and customization complexity score and your cell in the estimation matrix

• A recommended deployment model and license view

• A must-do versus Phase 2 scope, a dated plan and a budget range

If you are already in flight, we can review your plan against the gates in this article and tell you plainly where the risk sits.

Email start@managederpservices.com or call +1-832-449-1520 to book a 30-minute readiness call.

FAQ for IT leaders

Will Microsoft extend the February 28, 2027 date?

Plan as if it will not. The Feature deprecations page states that environments with the legacy integration can continue until February 28, 2027, and that deprecated features stop working after removal.

Do we have to buy Project Operations for every user?

Not necessarily. Microsoft supports a Field Service + Finance + Supply Chain model with Project Operations forms embedded in Field Service; the installing user needs a Project Operations license. Confirm with your licensing advisor which other users need rights, especially anyone approving time or material usage.

Can we run the old and new integrations side by side?

Not in the same environment: Microsoft's setup guide requires uninstalling the legacy integration first. Run your "parallel" in a sandbox and rehearse the cutover there.

Will our technicians need retraining?

Very little. Microsoft states technicians continue using Field Service without workflow changes. Retest offline sync, because the integration installs mobile offline profiles that override the defaults, and brief anyone whose time entries will now follow Project Operations approval.

What happens to our historical transactions?

They stay where they are. Posted journals and invoices remain in F&O; migrate only open work orders that cannot be closed before cutover.

We use the older Data Integrator templates, not dual-write. Are we affected?

Yes. Microsoft's F&O documentation says the Data Integrator templates for Field Service also end after February 28, 2027. Expect more work, because those templates sync work orders as sales orders and are incompatible with dual-write.

We run Field Service with Business Central. Does this apply to us?

This notice covers the finance and operations integration. The Business Central connector is a separate integration, so check Microsoft's Business Central documentation for its own roadmap.

How much will it cost?

It depends on your cell in the estimation matrix and the deployment model. A two-week assessment gives you a scoped budget range instead of a guess.

Sources

All Microsoft pages were opened and checked on September 28, 2026. Microsoft updates these pages often, so recheck dates and version numbers before you commit to a plan.

• Feature deprecations – Dynamics 365 Field Service (end date, install toggle, announcement date)

• Field Service integration with Project Operations overview (deployment models, end-to-end flow)

• Set up Field Service integration with Project Operations (prerequisites, versions, uninstall requirement, settings)

• Connect Field Service to finance and operations – release plan (general availability January 30, 2026)

• Integration with Field Service overview – Finance and Operations (Data Integrator templates end date)

Durations, thresholds and dates in the plan and matrix are our estimates for mid-market organizations, not Microsoft guidance.