Client Handover / Post-Go-Live Hypercare

ERPWeb Test Client — Test Odoo 16 to 19 Upgrade — Odoo 16 to Odoo 19

Back to Project Readiness Dashboard Go-Live Approval Go-Live Execution Upgrade Run Log Odoo.sh Workflow Dashboard
HANDOVER IN PROGRESS

0/7 Handover Items Closed

Required client handover or close-out blocking items are still open.

Readiness: NOT READY · Approval: APPROVALS PENDING · Execution: EXECUTION NOT COMPLETE

7Total items
0Closed
7Required open
6Close-out blockers
0Blocked
0Monitoring
0Accepted
CLOSE-OUT NOT READY

Project Close-Out / Archive

Close-out cannot be completed until the remaining blockers are resolved.

Blockers: 5 · Final report: Not Started · Archive: Active / Not Archived

Continue to project close-out / archive workflow

10. Confirm post-go-live hypercare support window

Support Window Blocks Close-Out Open

Capture the agreed support window, escalation path, ERPWeb owner, client owner, and support expectations after production go-live.

ERPWeb owner: ERPWeb Support Lead

Client owner: Client Project Owner

20. Capture final client handover notes

Handover Note Blocks Close-Out Open

Document what changed, what was upgraded, important usage notes, new processes, and any operational notes the client must know.

ERPWeb owner: ERPWeb Project Lead

Client owner: Client Project Owner

30. Document known issues and accepted workarounds

Known Issue Blocks Close-Out Open

List any known post-go-live issues, accepted risks, workarounds, responsible owners, and target follow-up dates.

ERPWeb owner: ERPWeb Functional Lead

Client owner: Client UAT Owner

40. Verify production monitoring and error checks

Monitoring Check Blocks Close-Out Open

Confirm the upgraded production system is being monitored after go-live, including logs, scheduled actions, queues, integrations, and user-reported issues.

ERPWeb owner: ERPWeb Technical Lead

Client owner: Not assigned

50. Complete first hypercare health review

Monitoring Check Open

Review the production system after users have started working and record whether any urgent support action is required.

ERPWeb owner: ERPWeb Support Lead

Client owner: Not assigned

60. Capture client acceptance after go-live

Client Acceptance Blocks Close-Out Open

Capture client confirmation that the upgraded production system is accepted, including any accepted conditions.

ERPWeb owner: ERPWeb Project Lead

Client owner: Client Decision Maker

70. Confirm upgrade project close-out readiness

Close-Out Readiness Blocks Close-Out Open

Confirm support handover is complete, known issues are documented, acceptance is captured, and the upgrade can move from hypercare to normal support.

ERPWeb owner: ERPWeb Project Lead

Client owner: Client Project Owner

ERPWeb Handover / Hypercare Rule

Do not close the upgrade project until the support window is captured, monitoring checks are recorded, known issues are documented, client acceptance is captured, and all close-out blocking items are closed or formally accepted.