Technical detail before the sales call.
Use the public material below to evaluate fit, identify unsupported assumptions, and prepare a more useful migration discussion.
Start with the decision you need to make.
These resources are public summaries. Detailed runbooks and environment-specific procedures are produced during an approved assessment or engagement.
Sample readiness assessment
See how ready, review, blocked, and deferred findings are presented.
Security and deployment boundary
Review content handling, metadata, secrets, ownership, and required egress.
Governed migration workflow
Understand discovery, mapping, dry run, execution, reconciliation, and evidence.
Packaging and pricing approach
See which topology and responsibility variables affect scope and price.
What each status commits us to.
Status is capability-specific. A platform control being Supported does not make every migration connector Supported.
Available for onboarding
Implemented and suitable for pilot or production use when configuration, permissions, topology, and release gates validate.
Guided use only
Requires APQOR oversight, lab validation, explicit success criteria, and an agreed rollback plan.
Assessment or assisted scope
Framework, interface, or preflight exists, but full production automation is incomplete.
Planned
A roadmap or backlog capability. Planned work is excluded from launch scope and must not be represented as available.
Keep the first proof bounded.
The recommended pilot verifies the operating loop before expanding object volume or workload breadth.