> For the complete documentation index, see [llms.txt](https://help.openloyalty.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.openloyalty.io/implementation-guide/data-and-go-live/go-live-checklist.md).

# Go-live Checklist

The go-live checklist and a cutover plan for launching a programme on Open Loyalty: readiness, the order of steps on the day, checks after the switch, and a fallback.

Go-live is when production configuration, migrated data and live channels come together. This page is the readiness checklist and cutover plan. Tell Open Loyalty your planned go-live date — and any change to it — early.

## Readiness

### Programme and configuration

* [ ] Every campaign, reward, tier, challenge and message is signed off on staging — see [Testing & UAT](https://help.openloyalty.io/implementation-guide/data-and-go-live/testing-and-uat.md).
* [ ] Production configuration is in place and reviewed against staging — see [Configuration migration](https://help.openloyalty.io/implementation-guide/data-and-go-live/configuration-migration.md).
* [ ] Campaigns that must not fire before or during the cutover are inactive.
* [ ] Coupon code pools and reward stock are loaded on production.

### Access and integration

* [ ] Admins have their own accounts with the right roles on production.
* [ ] Each integration has its own production API key, stored in a secrets manager.
* [ ] The integration's environment settings point to production: API URL, tenant code, API keys, and IDs looked up on production.
* [ ] Webhook subscriptions point to production endpoints with production HMAC secrets.
* [ ] Logging, alerting and retry queues are live for the integration layer and the webhook endpoint.

### Data

* [ ] The migration has been rehearsed, timed and reconciled on staging — see [Data migration](https://help.openloyalty.io/implementation-guide/data-and-go-live/data-migration.md).
* [ ] The final migration window and its freeze on the old system are agreed.

### Capacity

* [ ] Expected launch traffic is covered by the production limits, or a limits increase has been confirmed through Open Loyalty support.

### People and communication

* [ ] Open Loyalty knows the go-live date.
* [ ] Customer service knows the programme rules, the FAQ and how to escalate — including the helpdesk.
* [ ] Member communication and marketing are ready to send after the switch is confirmed.
* [ ] A go/no-go meeting is scheduled with named owners for each area.

## Cutover plan

{% stepper %}
{% step %}

### Freeze

Stop changes on the old system (or put its earning into a holding state) so balances don't move during the migration.
{% endstep %}

{% step %}

### Migrate

Run the final migration on production and reconcile counts and balances per wallet. Don't continue until the numbers match.
{% endstep %}

{% step %}

### Activate

Activate the campaigns, rewards and challenges that were held back.
{% endstep %}

{% step %}

### Switch the channels

Point the website, app, e-commerce platform and stores at the production integration. Switch webhooks on if they were held back.
{% endstep %}

{% step %}

### Smoke test

With production test members: register, earn from a purchase and a custom event, see the balance, redeem a reward, receive the webhook in CRM. Remove or deactivate the test members afterwards.
{% endstep %}

{% step %}

### Announce

Send the member communication and start marketing only after the smoke test passes.
{% endstep %}
{% endstepper %}

## Fallback

Decide before the day what happens if a step fails:

* **Before channels switch:** stop, keep the old system running, fix and reschedule.
* **After channels switch:** if earning is broken, keep the channels queuing events in the integration layer (they can be replayed thanks to stable document numbers and event IDs) rather than dropping them; fix forward.

## After the switch

Watch closely for the first days — see [After go-live](https://help.openloyalty.io/implementation-guide/data-and-go-live/after-go-live.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.openloyalty.io/implementation-guide/data-and-go-live/go-live-checklist.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
