Go-Live and Handover
Go-live should be treated as an evidence-based handoff. The project team confirms that identity, product access, data flows, integrations, monitoring, backup, and support paths are ready for production use.
Prerequisites
Complete environment readiness and product configuration. The customer should identify a production owner, support owner, business acceptance owner, and change approval owner before go-live validation starts.
Handover flow
Inputs
| Input | Example |
|---|---|
| Acceptance scope | Products, modules, sites, data sources, workflows, and user groups included in go-live. |
| Test users | Administrator, operator, viewer, integration owner, and support user. |
| Validation data | Assets, documents, connectors, datasets, work orders, AI workflows, or simulation scenes. |
| Support contacts | Customer business owner, customer IT owner, DataMesh project contact, escalation window. |
| Release window | Go-live time, freeze period, rollback expectation, and communication plan. |
Validation steps
- Confirm the production URL, tenant, and environment label.
- Validate administrator login, SSO or password login, and role-based product access.
- Validate target product workflows with representative users.
- Validate connectors, imports, API keys, and scheduled jobs included in go-live.
- Confirm monitoring checks, backup expectations, and support contacts.
- Confirm open known issues and workarounds are recorded.
- Confirm rollback or pause criteria for the release window.
- Record sign-off from business owner and environment owner.
Go-live evidence
| Evidence | Purpose |
|---|---|
| Environment inventory | Shows what was deployed and which URL users should use. |
| User and role validation | Confirms the right users can perform the right tasks. |
| Product workflow validation | Confirms the deployment supports business use. |
| Integration validation | Confirms data and service identities work as planned. |
| Backup and recovery statement | Confirms recovery expectations are assigned and approved. |
| Support handoff | Confirms incident and escalation path. |
| Known issues list | Keeps remaining risks visible. |
Expected result
The deployment is ready for production when the customer can access the environment, complete agreed workflows, operate the support process, and understand the responsibilities for monitoring, backup, recovery, and release maintenance.
Production monitoring period
After go-live, define a short stabilization period. During this period, track sign-in failures, integration errors, user access requests, product workflow exceptions, performance concerns, and support response time. Close the stabilization period only after the customer owner accepts the open-issue list and operating rhythm.
Troubleshooting go-live blockers
| Symptom | Check |
|---|---|
| Users can sign in but cannot complete tasks | Product permissions, object scope, sample data, workflow state, or client version. |
| Connectors fail after handoff | Credentials, source-system availability, network route, schedule, or schema change. |
| Support ownership is unclear | Handoff record, escalation path, customer IT owner, or DataMesh contact. |
| Go-live evidence is incomplete | Acceptance scope, validation owner, missing screenshots, missing logs, or unresolved known issue. |
Related pages
- Use Operations and Maintenance for post-go-live rhythm.
- Use Authentication Troubleshooting for access issues.
- Use Backup and Recovery for recovery planning.