> 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/playbook/go-live-preparation.md). # Go-Live Preparation To ensure your smooth preparation for the launch of your loyalty program, please review the go-live checklist and complete the go-live preparation form. ### Short Go-Live Checklist Below, we’ve provided a concise checklist of essential items to review before your go-live. You can review them internally with all your teams. They will help you to ensure the smooth launch of your loyalty program. * [x] Have you conducted UAT testing in the staging environment? * [x] Have all admins been assigned to their appropriate roles? * [x] Have you successfully migrated the configuration from the staging environment to production? * [x] If the migration of the loyalty program is required, have all necessary elements been transferred to Open Loyalty (e.g., members, points balance, transactions, events)? * [x] Have you updated the URL's from staging to production? * [x] Have you informed Open Loyalty about the planned go-live date or any changes related to it? * [x] Have you communicated the program rollout to your members? * [x] Have you planned marketing activities to promote the loyalty program? --- # 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 dynamically 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/playbook/go-live-preparation.md?ask=&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 `build a script that syncs our docs to a CMS` 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.