> 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/go-live-preparation.md). # Go-Live Preparation ### 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.openloyalty.io/go-live-preparation.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.