> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/writebackextreme/getting-started/moving-to-production.md). # Moving to production When reaching the end of the testing phase there could be a desire to copy the whole setup (including tableau workbooks) from your test environment to the production environment. When doing this there are a few things to keep in mind. ### Copy of the repository database The repository database is the heart of WriteBack and contains all the setup you did in the management console. * The repository database on your test environment needs to be cloned manually. * You need to do a fresh installation on the new production server. * Connect to the cloned database on step 3 of the installation to use that as the repository database * When you have configured SSO in your test environment you need to redo that in the production environment since the URL will be different. It is good practice to create a new app in your IDP for the production environment ### Workbook replication When you already have your workbooks configured you probably want to point them to the new WriteBackExtreme production environment. You can use our Trex replacer tool for that. * Download your workbook * Download the new .trex file from the management console of the production environment * Download our [trex replacer tool](https://appsfortableau.infotopics.com/apps/toolbox/) * Load the workbook and your new .trex file into the tool and let it replace the URL’s --- # 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://docs.infotopics.com/writebackextreme/getting-started/moving-to-production.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 `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.