Which Reporter workflows are compatible?
Handover preserves report deployment, stable report URLs, product and folder organization, listing, inspection, pull, republish, context health, and MCP compatibility over canonical Handover revisions.
How should a migration be staged?
Run Reporter and Handover in parallel first. Inventory products and folders, import reports with provenance, validate files and URLs, then change the default agent destination only after team sign-off.
- Map each Reporter product to a Handover Space.
- Map Reporter folders to Handover folders inside the Space.
- Import report files and verify hashes, visibility, and authorship.
- Keep Reporter available until publishing and pull tests pass.
- Switch Gatana or other agent defaults as a separate final step.
Will old report links continue to work?
Handover publishes stable /r/{slug}/ routes and keeps Reporter-compatible aliases. A migration should still validate every important legacy link before cutover.
What should be tested before cutover?
Test human sign-in, domain auto-provisioning, service accounts, report rendering, nested assets, MCP publish and pull, search, annotations, access boundaries, and rollback procedures.
FAQ
Frequently asked questions
Does migration require an immediate Reporter shutdown?
No. Parallel operation is the recommended approach until the formal handover is complete.
Can Handover import Reporter folders automatically?
Yes. The migration and compatibility interfaces preserve product and folder placement while creating canonical Handover records.