Key Takeaways
The short version, for anyone who needs the point before the detail:
- This is a staged move, not a switch-off. Microsoft stopped new LCS projects for Finance, Supply Chain Management and Project Operations on February 16, 2026, and is shifting environment management, support and developer environments to the Power Platform admin center (PPAC). It hasn't published a shutdown date for LCS as a whole.
- Existing projects keep working for now. If you have an active LCS project, you can keep using it. Self-service migration to PPAC is in public preview, and Microsoft says to start with sandboxes, not production.
- You can't undo a migration. Once an environment moves, LCS shows it as read-only and you can't move management back.
- Daily work changes. Deploy becomes Provision, database refresh becomes Copy, and backups stay in the cloud, so you can't download a .bak or .bacpac file anymore. Packages become unified packages.
- Two environment types can't move yet. Cloud-hosted developer environments and Commerce environments aren't supported for migration.
Each of those points is covered below, starting with where Microsoft's plan stands today.
Introduction
This guide is for the people who own Dynamics 365 Finance and Supply Chain Management environments: IT leads, F&O administrators, and the partners who run deployments and support on their behalf. If you spend your days in Lifecycle Services (LCS), that work is moving to the Power Platform admin center, and Microsoft says so directly: . It's happening in stages, and a few of those stages are already behind us.
The table below is the timeline Microsoft has published, with a note on what each step means for your team.
| When | What happened | What it means for you |
|---|---|---|
| May 1, 2025 | . Unlinked environments were switched on automatically | Your environments are already linked to a Power Platform environment, which migration needs |
| October 15, 2025 | The Translation Service reached end of support and was removed from LCS | Use the Dynamics translation connector |
| January 2026 | Code freeze in LCS | Groundwork for the project freeze |
| February 16, 2026 | for Finance, Supply Chain Management or Project Operations | New customers start in PPAC. Existing customers keep their active projects |
| September 2026 | Self-service environment migration opened in public preview for existing LCS customers | You can start moving sandboxes |
| Staged, no dates | The LCS Support page is being retired in favor of PPAC Help + Support | Support tickets move to PPAC |
Microsoft hasn't announced a shutdown date for LCS as a whole, and none of its pages describe an extension. Commerce projects, AX 2012 upgrade projects, on-premises implementations and tenant-to-tenant migrations are still created in LCS. The migration feature is still in preview and Microsoft's page says it may change, so check it again before you lock in a schedule.
Those dates set the pace, but the part you'll feel first is the change in how everyday tasks work, so that's where we'll go next.
Changes to Daily F&O Administration You Can Expect
Most of the renaming is cosmetic. Six of the changes aren't, and each one lands on a different person: the developer who restores databases, the build engineer who owns the pipelines, the support lead, and whoever hands out admin roles. Here is what each of them will notice.
Backups never leave the cloud. If your developers restore a .bak or .bacpac file on their own machines, that routine ends in PPAC. The way to get a development copy is to Copy an environment into a unified developer environment. Microsoft's tutorial says the source has to be an LCS environment with Power Platform Integration set up, and the source and target have to be in the same region.
Code always comes along with the data. A Copy in Power Platform copies code with data. If you used to refresh data into an environment that held newer code, the copy will bring its own code version with it.
Deployments use unified packages. You build them with the Power Platform CLI or Azure DevOps tasks. After you migrate, you deploy code with Azure Pipelines and Power Platform deployment capabilities, and build agents become Microsoft-hosted agents in Azure DevOps. Your pipeline definitions will need a review.
Support tickets move in three stages. First, the LCS Support page gets a banner with a redirect link. Next, every entry point redirects to PPAC Help + Support. Last, the Support issues tile is removed and the page is blocked. , and Microsoft gives no calendar dates. Submitting active issues to Microsoft Support from LCS is already disabled.
Roles change. To use support in PPAC you need the Service Support Administrator or Helpdesk Administrator role, and partners need delegated admin permissions. The Project Owner role becomes the Power Platform administrator role. You'll also see a temporary Lifecycle Services User role when you enter PPAC from LCS, and Microsoft says it will eventually be removed.
Monitoring moves to Application Insights. Some LCS activity queries were switched off in September 2024, and the Health Metrics tab is in maintenance mode with no further support.
Proactive quality update scheduling works the same way for unified and LCS environments, so that part of your routine stays as it is.
Knowing what will feel different is one thing. The next question is where each task you do in LCS now lives.
Where Each LCS Task Moves in the Power Platform Admin Center
If you've ever asked "where did that go?" about an LCS task, Microsoft's has the answer. There are two groups. The environment tasks mostly keep their purpose and change their names:
| In LCS | In the Power Platform admin center |
|---|---|
| Deploy | Provision |
| Database refresh | Copy (code is always copied with data) |
| Database export | Backup, which stays in the cloud and is never downloaded as a .bak or .bacpac file |
| Point-in-time restore | Restore |
| Reset, Convert to production | Reset and Convert to production (Reset isn't implemented yet where the Provisioning App is installed) |
| Deallocate or delete | Delete |
| Cloud-hosted developer VMs | Unified developer environments |
Everything that wasn't rebuilt in PPAC has a replacement somewhere else, and several of them are other Microsoft tools you may not be using yet:
| In LCS | Replacement |
|---|---|
| Methodology, project settings and users | Dynamics Implementation portal or Azure DevOps |
| Organization users | Microsoft 365 admin center |
| Translation service | Dynamics translation connector |
| Asset library | Packages stored in Azure DevOps and imported to Dataverse. Database backups aren't available offline |
| Solution management | Microsoft Marketplace |
| Build environments | Microsoft-hosted agents in Azure DevOps |
| Alert service | A support ticket |
| Business process modeler | Business process catalog |
| Task recorder files | Saved locally |
| Support requests | PPAC Help + Support |
| Monitoring | Application Insights for finance and operations apps |
A few terms change along the way. A software deployable package is now a unified package, and maintenance mode is now admin mode, so expect both in the new documentation.
With every task mapped to a new home, the practical question is what the move will cost your team.
Capacity, License and Downtime Costs of Moving to PPAC
None of these costs shows up as a price on a list. They're capacity, licenses, downtime and rework, and each comes straight from Microsoft's documentation. The table puts them side by side so you can see which ones need a decision from someone outside the IT team.
| What you do | What it costs you |
|---|---|
| Run an environment in PPAC | At least 1 GB of operations capacity and 1 GB of Dataverse database capacity for each additional environment. Migrated environments count under the Power Platform capacity model |
| Create or install a finance and operations app in PPAC | A license |
| Migrate an environment | About 15 minutes of downtime per AOS instance |
| Finish a migration | You can't reverse it, and the LCS environment slot isn't given back |
| Retire a cloud-hosted developer VM | You can't migrate it, so you rebuild it as a unified developer environment |
| Switch to unified packages | Rework on your build and deployment pipelines |
| Rely on local backups | That ends. Backups stay in the cloud |
Capacity is the line to check first, because it's the one most likely to need a budget conversation. The rest is effort your own team can plan for.
Once the costs are agreed, you can look at the migration itself.
Step by Step: Migrating an F&O Sandbox from LCS to PPAC
Microsoft's is marked prerelease documentation, so treat the steps as a snapshot. Three rules shape how you use them.
- Do sandboxes first. During the preview, Microsoft recommends migrating sandboxes first and not using the feature for production.
- It's one-way. After migration, LCS shows the environment as read-only. Migration is per environment, and it doesn't move the LCS project itself.
- Expect a short outage. Microsoft says about 15 minutes of downtime per AOS instance.
Self-service sandboxes are supported. For self-service production, the action may appear, but Microsoft doesn't recommend it in preview. Cloud-hosted developer environments aren't supported, so use a unified developer environment or a downloadable VHD. Commerce isn't supported either, and the prerequisite check won't catch Commerce usage, so check it yourself.
Before you start, make sure the environment shows Deployed, it's linked to a Power Platform environment, you have enough storage capacity, and you're an administrator of the linked Power Platform environment. Have your unified developer environments and Azure Pipelines ready first. Then work through the migration itself:
- In LCS, open the project, go to Environments and select Full details for the sandbox.
- Expand Power Platform migration (Preview).
- Check that all four prerequisite checks are green.
- Select Migrate to Power Platform Admin Center and read the downtime and one-way warning.
- Type the environment name exactly and select Start migration.
- When Migration status reads Migrated, select Open in Power Platform Admin Center.
The LCS environment slot isn't returned, so migrating doesn't free a slot for a new LCS environment.
The steps are short, but Microsoft's documentation doesn't answer everything you'll want to know before running them.
Gaps in Microsoft's LCS-to-PPAC Documentation
A migration plan is only as good as the documentation behind it, and a few gaps remain as of mid-October 2026. None of them blocks you from starting, but each is worth a note in your plan.
- Tools without a named replacement. Microsoft doesn't name a replacement for issue search, hotfix requests or code upgrade. Its 2022 deprecation list shows hotfix requests, Visio-based business process modeler management and work items in LCS storage as deprecated with nothing to replace them.
- Developer environments. Cloud-hosted VMs don't migrate. Unified developer environments replace them, so you're rebuilding your developer setup, not moving it.
- Commerce runs on its own track. Commerce projects are still created in LCS. A Commerce scale unit deployment route through PPAC entered public preview in May 2026, and Microsoft's release plan listed general availability for September 2026. Check its current status before you plan around it.
- Offline copies. Backups aren't available offline. If you relied on downloading them, or on the asset library to store them, you'll need another process.
- Pages that disagree. One Microsoft page still says PPAC doesn't manage finance and operations apps. The newer pages show the unified experience, so go by the page with the latest update date.
- Where changes get announced. Release plans stop being published in September 2026, and new capabilities are tracked in Microsoft's AI at Work roadmap. Add it to the sources you watch.
Those gaps are the reason the order of work matters, which brings us to the plan.
Your LCS Migration Action Plan for This Month
Order matters more than speed here, because the expensive mistakes come from moving an environment before its replacements are ready. This is the sequence we'd work through, starting with the inventory.
- List every environment by type: self-service sandbox, production, cloud-hosted developer VM, and anything that touches Commerce. Mark which ones Microsoft supports for migration.
- Confirm the Power Platform link. Each environment you plan to move has to be linked to a Power Platform environment, and you have to be an administrator of that linked environment.
- Check your capacity. You need at least 1 GB of operations capacity and 1 GB of Dataverse database capacity for each additional environment. Fix any shortfall first.
- Build the replacements before you migrate. Set up unified developer environments and Azure Pipelines that produce unified packages.
- Give people the right roles. That means Power Platform administrator for whoever manages environments, Service Support Administrator or Helpdesk Administrator for support contacts, and delegated admin access for partners.
- Migrate your least critical sandbox first. Validate it, then run a copy in PPAC, then move the rest of your sandboxes.
- Leave production for last. Microsoft advises against using the feature on production during preview. Pick a window after the feature leaves preview and your sandbox runs have gone cleanly, and agree what happens if something goes wrong, since you can't reverse the move.
- Start raising support tickets in PPAC Help + Support now, and update the runbooks that still tell people to use LCS.
- Rename the steps in your runbooks to Provision, Copy and Backup, and write down that backups are cloud-only.
If you work with a partner or an ISV, ask each one which LCS features they depend on and get their migration plan in writing.
A plan like this fails in predictable places, so here are the mistakes to steer clear of while you follow it.
Mistakes to Avoid When Migrating F&O Environments
Most of the trouble teams run into comes from doing the right steps in the wrong order, or from carrying an LCS habit into PPAC. These are the six we'd watch for, and each one connects back to a step above.
Migrating before the pipelines exist. Once an environment is in PPAC, LCS shows it as read-only. If your unified packages and developer environments aren't ready, you'll have nowhere to deploy.
Trusting the prerequisite check on Commerce. The check doesn't detect Commerce usage, and Commerce environments aren't supported for migration. Confirm it yourself before you start.
Treating production like a sandbox. Run your sandbox migration, copy and deployment routine twice before you touch production. The first run finds the surprises, and the second shows whether you fixed them.
Holding on to .bak and .bacpac habits. Backups stay in the cloud, so line up a replacement (Copy to a unified developer environment) before you cut over.
Splitting support across two places. Tickets raised in LCS and PPAC end up in different histories while the stages roll out. Pick PPAC Help + Support for new tickets now and tell the team.
Planning around a free LCS slot. The slot isn't returned when you migrate, so don't count on it for a new LCS environment.
If you've got those covered, the questions below are the ones we hear most often from teams at this stage.
Frequently Asked Questions
Is Lifecycle Services being retired?
Microsoft is replacing it with the Power Platform admin center in stages. New LCS projects for Finance, Supply Chain Management and Project Operations have been frozen since February 16, 2026, the Support page is being retired, and the Translation Service has been removed. Microsoft hasn't published a shutdown date for LCS as a whole, and Commerce, on-premises, AX 2012 upgrade and tenant-to-tenant projects still use it.
Do I have to migrate my existing environments now?
No. Microsoft says customers with active LCS projects can keep using them. Self-service migration is in public preview for existing customers, and Microsoft recommends starting with sandboxes. Get ready now so you control the timing.
Can I migrate production?
The action may appear for self-service production environments, but during public preview Microsoft recommends against using it for production.
Can I undo a migration?
No. After you migrate, LCS shows the environment's management as read-only and you can't move management back.
Where do I raise support tickets now?
In the Power Platform admin center, under Help + Support. You need the Service Support Administrator or Helpdesk Administrator role, and partners use delegated admin permissions.
Which tool replaces cloud-hosted developer environments?
Unified developer environments. Microsoft says they replace the cloud-hosted developer VMs that were deployed through Lifecycle Services, and cloud-hosted environments can't be migrated.
Does migration affect Commerce?
Commerce environments aren't supported for migration, and Commerce projects are still created in LCS. Commerce scale unit deployment through PPAC has its own release plan, so check where it stands for your version.
If your situation isn't covered here, that's where a second pair of eyes helps.
Get a Free Implementation Assessment
Moving your environments is mostly a sequencing problem: sandboxes, developer environments, pipelines, capacity, roles and support. Folio3 Dynamics is a Microsoft Dynamics 365 partner with 20+ years of experience and 200+ certified professionals. We can review your LCS projects, set the migration order, and build the developer environments and pipelines you'll need.