Migrating an F&O environment from LCS to the Power Platform admin center: what the preview moves

Our earlier article covered what breaks when you move from Lifecycle Services to the Power Platform admin center. Since then Microsoft has published the tool that does the moving. "Migrate finance and operations environments from Lifecycle Services to Power Platform admin center (preview)" went up on Microsoft Learn with an ms.date of 22 September 2026, and the matching roadmap item RM573244 (published 1 October 2026) lists preview for September 2026 and general availability for December 2026. This is what the page says the migration is, and the five lines in it that decide whether you run it this quarter.

For the environment owner who has been asked "when are we off LCS?" 6 minute read.

What the migration does, in one paragraph

"The self-service environment migration feature moves management of an existing finance and operations apps environment from Microsoft Dynamics Lifecycle Services to the Microsoft Power Platform admin center. Migration is performed separately for each environment in a Lifecycle Services project. It doesn't migrate the Lifecycle Services project itself." The page is explicit about what is not happening: it "updates environment metadata across Microsoft services"; "The database isn't moved, and the environment infrastructure isn't materially changed."

So it is a change of control plane, not a move of data or servers. That is the good news. The rest of the page is about what changes once the control plane is different.

The five lines that decide the timing

1. "Migration is a one-way operation." After it, the environment's management "is read-only in Lifecycle Services, and you can't move its management back to Lifecycle Services through a customer-initiated operation."
2. Production is not recommended yet. Self-service production "might be available, but production migration isn't recommended during public preview." The page says it twice: "migrate sandbox environments first and don't use the feature for production environments."
3. Commerce is out, and the check will not catch it. Environments using Dynamics 365 Commerce are "Not supported during public preview," and the prerequisite check "doesn't currently detect Commerce usage." You have to know.
4. Cloud-hosted developer environments are not supported. The page points those at the Unified Developer Environment or the downloadable VHD instead.
5. Downtime is per AOS. "Plan for approximately 15 minutes of downtime for each Application Object Server (AOS) instance. Environments that have more AOS instances take longer." Users must be told beforehand.

Prerequisites, as a checklist

• The environment's status in Lifecycle Services is "Deployed."
• A Power Platform environment is linked ("Enable the Power Platform integration"). Dual-write is not required: "You don't have to enable dual-write to migrate an environment."
• Any Power Platform storage capacity deficit is resolved; database capacity is validated before the migration runs.
• The person starting the migration is an administrator of the linked Power Platform environment.
• The environment does not use Commerce (your check, not Microsoft's).

The page states no version requirement and no tenant or region condition.

What changes afterwards

After migration, "The Power Platform admin center is the management experience for environment lifecycle operations such as copy, backup, restore, servicing, updates, and monitoring." Application lifecycle management moves to "Azure Pipelines and Power Platform deployment capabilities." The environment consumes capacity under the Power Platform capacity model. And one line that catches people planning environment counts: "The Lifecycle Services environment slot isn't returned or made available for another environment."

Read that together with the unified admin experience overview (ms.date 10 September 2026): the operations are renamed, and one of them changes meaning. "Database refresh" becomes "Copy", and where Lifecycle Services "only copy data," the admin center's copy means "code is always copied with data." A team that refreshes a sandbox monthly should run one copy after migration as a test, before relying on it for a release.

The steps, so nobody has to guess

In Lifecycle Services: Environments, Full details, expand "Power Platform migration (Preview)", confirm the four prerequisite checks are green, select "Migrate to Power Platform Admin Center", type the environment name to confirm, "Start migration", wait for the status "Migrated", then "Open in Power Platform Admin Center". The confirmation dialog repeats the downtime warning.

Where we would draw the line

Migrate one non-Commerce sandbox now, during the preview, and leave production in Lifecycle Services until general availability, which the roadmap lists for December 2026. The sandbox migration costs you about 15 minutes per AOS and gives the team three months of operating the admin center's copy, backup and restore before production depends on it.

If an AI agent runs against that sandbox, note that the migration does not touch the database, the users or the endpoints. The agent's access survives the migration. What changes is the operation that resets it: the next refresh is a copy, and copy includes code. The runbook step "re-register the agent after a refresh" stays; the name of the operation changes.

What to do this week

1. List every F&O environment with three columns: uses Commerce, has cloud-hosted dev boxes, number of AOS instances.
2. Pick one sandbox with no Commerce and a linked Power Platform environment, and resolve its capacity deficit if the check shows one.
3. Schedule the migration outside business hours, tell the testers about the downtime, and run it.
4. Run one copy, one backup and one restore from the admin center on that sandbox before December, and write down what differed from Lifecycle Services.

Sources

• Microsoft Learn, "Migrate finance and operations environments from Lifecycle Services to Power Platform admin center (preview)", ms.date 2026-09-22: https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/lifecycle-services/migrate-lifecycle-services-environments-power-platform-admin-center
• Microsoft 365 Roadmap item RM573244, "Migrate finance and operations environments from Lifecycle Services to Power Platform admin center", published 2026-10-01, preview September 2026, GA December 2026, status "In development": https://mc.merill.net/message/RM573244
• Microsoft Learn, "Unified admin experience for finance and operations apps", ms.date 2026-09-10: https://learn.microsoft.com/en-us/power-platform/admin/unified-experience/finance-operations-apps-overview
• Microsoft Learn, "Change the environment type", ms.date 2026-01-22: https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/power-platform/environment-lifecycle-change-env-type-dv

All read 22 October 2026.