> ## Documentation Index > Fetch the complete documentation index at: https://developers.pcibooking.net/llms.txt > Use this file to discover all available pages before exploring further. # Moving Configuration to Production > What carries over from your sandbox account to your production account, what you import through the portal, and what you set up again. Your sandbox and production accounts are two separate accounts on the same system. They share nothing: not API keys, not users, not stored tokens, and not configuration. When your production account is created, it starts empty. This page lists what you can import from sandbox in one step and what you need to set up again. ## Import Sandbox Data The portal can copy three kinds of configuration from your sandbox account into your production account. 1. Log in to the [PCI Booking portal](https://users.pcibooking.net) with your **production** account. The import option is not shown when you are logged in to a sandbox account. 2. Go to **Booker Settings** > **Import sandbox data**. 3. Enter the username and password of your **sandbox** account and click **Login**. 4. Tick the items to import, then click **Continue** and confirm. | What is imported | Notes | | --------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Language settings** (custom translations) | Each selected language is copied as is. Any translation already in production for that language is replaced. Where the sandbox has no override for a label, production falls back to the default text. See [Custom Translations](/account-setup/custom-translations). | | **Stylesheet settings** | Each selected stylesheet is copied by name. A production stylesheet with the same name is overwritten. See [Stylesheets](/account-setup/stylesheets). | | **PCI Shield profile settings** (target profiles and their content filters) | Each selected profile is copied by name. A production profile with the same name is overwritten. See [Target Profiles](/account-setup/target-profiles). | If a profile references a client certificate, the certificate file is copied to your production account under the same name, but the copied profile is saved without the certificate attached. Open the profile in production and select the certificate again. See [Client Certificates](/account-setup/client-certificates). The import requires the **Can manage resources** permission on your production user. You can run it more than once, for example after changing a stylesheet in sandbox. ## Set Up Again in Production Everything not listed above must be created in the production account. Most of it is done in the portal; a few items go through our support team. | Configuration | Where | Notes | | ------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | API keys and users | Portal, [Manage Users and API Keys](/account-setup/manage-users) | Create your production API key first. Sandbox keys do not work against the production account. | | PSP credentials | Portal or API, [PSP Credentials](/account-setup/gateway-credentials) | Use your PSP's **live** credentials. Sandbox accounts route to PSP test environments, production accounts route to PSP live environments. | | Payments Library credentials (Apple Pay, Google Pay, PayPal, BankPay, UPI) | Portal or API, [Payments Library Credentials](/account-setup/payments-library-credentials) | Live credentials only: PayPal live client ID and secret, Google Pay production merchant ID, Apple Pay certificates registered for your production domain. | | Client certificates | Portal, [Client Certificates](/account-setup/client-certificates) | Certificates referenced by imported profiles are copied; any others must be uploaded again. | | Security settings (IP restrictions, callback URL whitelist, card display permissions) | Portal, [Security Settings](/account-setup/security-settings) | Add your production server IPs and production callback URLs. | | CVV store rules | Portal, [CVV Retention Policy](/capture-cards/cvv-retention-policy) | Set the account-wide default again. | | Booker settings (brand name, logo, contact and billing details) | Portal, [Booker Settings](/account-setup/booker-settings) | | | General customization and email templates | Portal, [General Customization](/account-setup/general-customization) and [Email Templates](/account-setup/email-templates) | Not part of the import. | | Card By Link templates | Portal, [Card By Link Templates](/account-setup/card-by-link-templates) | Not part of the import. | | White label email domain | Portal plus support, [White Label Email Domain](/account-setup/white-label-email) | DNS records stay valid; the setting and the verification with support are per account. | | 3DS merchant details | Support, [3DS Merchant Setup](/account-setup/3ds-merchant-setup) | Merchant details are registered per account. Ask support to register them on the production account. | | Token Replacement in Response and Tokenization on Request endpoints | Support | The dedicated endpoint, its DNS record and SSL certificate are set up per account. Tell support when you are ready to move them. See [Tokenization on Request](/capture-cards/tokenization-on-request). | | Third-party permissions | API, [Third-Party Permissions](/manage-tokens/third-party-permissions) | Associations are between production accounts and must be created again. | | Virtual card provider credentials | API, [Virtual Card Issuance](/capture-cards/virtual-cards) | Live provider credentials. | ## What Does Not Move * **Card tokens.** Tokens created in sandbox stay in sandbox. A sandbox token cannot be used with a production API key, and there is no transfer. If you have real cards in sandbox that you need in production, contact [support@pcibooking.net](mailto:support@pcibooking.net). * **Transaction history and logs.** Reports and logs are per account. * **Sandbox usage limits.** Production accounts have no monthly operation allowances. ## In Your Code The base URL does not change. Replace the sandbox API key with the production API key, and replace any sandbox-only values in your requests: PSP credential names, profile names if you renamed them, success and failure URLs pointing at test pages, and callback URLs. Then run the [Go-Live Checklist](/getting-started/testing-and-going-live#go-live-checklist). Your sandbox account stays open. Keep using it for development and for testing new features before you change production. ## Related * [Testing & Going Live](/getting-started/testing-and-going-live). Sandbox behaviour, test cards and the go-live checklist. * [Create an Account](/getting-started/create-account). How sandbox and production accounts are created. * [Authentication](/getting-started/authentication). How API keys work.