1. Freeze a known-good mobile build first
Keep a source-control checkpoint or complete project backup plus one known-good Android/iOS build. Dependency-manager changes can expose plugin conflicts that were previously hidden by the existing resolver state.
2. Inventory SDKs that currently bring EDM4U
List ads, analytics, monetization, authentication, push-notification and other native SDKs. Unity specifically notes that if an SDK installed EDM4U for you, keep EDM4U installed until that SDK moves to EDM.
3. Install Unity EDM through Package Manager
Unity's migration instructions say to open Package Manager, search the Unity Registry for External Dependency Manager, and install the official package.
4. Choose the active dependency manager
If EDM4U already exists in the project, Unity says the Editor prompts you to choose which dependency manager is active. Nothing is deleted automatically, and you can switch through Assets → External Dependency Manager.
5. Do not rewrite working XML declarations just for the migration
Unity says EDM uses the same XML dependency specification as EDM4U. Preserve existing declarations first; troubleshoot actual conflicts instead of rewriting every SDK dependency preemptively.
6. Remove EDM4U only when its ownership is clear
If you installed EDM4U directly, remove it after the new package has been verified. If a third-party SDK supplies it, wait until that SDK officially moves to EDM so an SDK update does not put the old resolver back into the project.
7. Re-resolve Android and iOS dependencies
Inspect the resolved Gradle/AAR path on Android and CocoaPods or Swift Package dependencies on iOS. The purpose of the manager is native dependency resolution, so a clean Editor console alone is not enough evidence.
8. Build the real target platforms
Create representative Android and iOS builds, launch them on target devices, then verify the SDK features that depend on native libraries: ads, analytics, auth, IAP, notifications or any project-specific integration.
EDM4U migration FAQ
When is EDM4U archived?
Google says October 26, 2026. The repository remains accessible but becomes read-only and unsupported.
What replaces EDM4U?
Unity's official External Dependency Manager package, distributed through UPM.
Do I need to rewrite dependency XML?
Unity says no migration rewrite is required for the XML dependency format: the official EDM package supports the existing specification.
Can I remove EDM4U immediately?
Only if you installed it yourself and the project/SDK stack is ready. Unity explicitly advises keeping it when an SDK still brings EDM4U until that SDK migrates.
Use the migration as a reason to clean obvious Unity handoff problems too.
The free asset preflight checks common prefab, material, texture and model problems before another variable is introduced into the project.
Official sources
Unity EDM announcement → · Google EDM4U archive notice → · Unity EDM package docs →