Plan Imports
What AssurePlan expects from uploaded migration plan exports.
Supported Input Shape
AssurePlan starts from exported plan files rather than live source-system connectors. Upload a CSV or Excel file that contains migration tasks, dates, owners, dependencies, status, wave or phase context, and business or technical impact signals when available.
The importer maps common schedule and work-management column names into a structured plan version. It also reports unmapped columns and blockers before a workspace is saved.
Required Plan Signals
The strongest imports include:
- Task ID and task name
- Owner or accountable party
- Planned start and finish dates
- Dependency references
- Status or progress
- Migration wave, phase, or workstream
- Cutover window
- Business impact or affected service
- Rollback, validation, approval, or technical confirmation evidence
Save Readiness
AssurePlan should not save an import when required task identity fields are missing. Blocked imports show a concise reason and next step so the user can fix the source export and upload again.