1️⃣ Pre-Migration Assessment
✔ Review current Dataverse & Dynamics 365 storage usage
-
-
Database (DB)
-
File
-
Log
-
Environment-level usage
-
✔ Identify high-consumption apps or workloads, such as:
-
-
AI agents
-
Power Automate workflows
-
Virtual tables
-
Attachments-heavy apps
-
ERP integrations
-
✔ Document current ERP storage usage
-
-
Finance
-
Supply Chain
-
Project Operations
-
Commerce
-
HR
-
✔ Export capacity reports for baseline comparison.
2️⃣ Planning & Architecture Review
✔ Map which environments will be impacted
-
-
Production
-
Sandbox
-
Dev/Test
-
Tier-2 environments
-
✔ Review data retention policies
-
-
Logs
-
Audit history
-
Plugin trace logs
-
Dataverse logs
-
Workflow history
-
✔ Identify opportunities to archive or compress unused data
✔ Confirm storage dependencies
-
-
Dataflows
-
API integrations
-
External connections
-
Custom plugins or power automate flows that generate metadata
-
✔ Review AI-driven workloads
-
-
Determine if new AI agents will increase contextual data storage
-
Align with the future “system-of-action" app model
-
3️⃣ Licensing & Capacity Validation
✔ Validate your capacity vs. entitlements
-
-
Confirm the updated unified pool amount
-
Compare with your storage predictions
-
✔ Update internal licensing documentation
✔ Validate whether additional capacity add-ons are needed
✔ Review the latest Microsoft Licensing Guide (Dec 2025 version)
4️⃣ Environment Preparation
✔ Enable or verify Power Platform Admin Center access
✔ Set storage alerts for high consumption thresholds
✔ Clean up unused environments
✔ Apply retention policies before migration begins
5️⃣ Migration Execution
✔ Move to unified storage model (if applicable)
✔ Reconfigure ERP apps (Finance, SCM, Project Ops) to point to unified capacity
✔ Validate workloads after migration
-
-
Ensure workflows continue running
-
Validate plugins, APIs, and custom connectors
-
Monitor ingestion loads
-
✔ Test business apps in:
-
-
Production
-
Sandboxes
-
Integrated systems
-
✔ Check file storage migration paths
-
-
Attachments
-
Documents
-
Images
-
AI-generated artifacts
-
✔ Monitor logs closely for 48–72 hours post-migration
6️⃣ Post-Migration Optimization
✔ Re-evaluate storage usage with new model
✔ Optimize data tables
-
-
Remove orphaned records
-
Archive historical logs
-
Clean up attachments
-
✔ Reconfigure Power Automate flows to reduce unnecessary logs/history
✔ Update lifecycle & governance documentation
✔ Train admins & business users on:
-
-
New capacity model
-
New monitoring dashboards
-
Storage governance best practices
-
7️⃣ Ongoing Governance Checklist
✔ Monthly storage health check
✔ Quarterly environment cleanup
✔ Annual architecture review
✔ Predictive planning for AI agent workloads
✔ Monitor Power Platform release waves for new capacity rules
