> ## Documentation Index
> Fetch the complete documentation index at: https://algolia.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Moving to production

> What needs to be done when pushing the store to production

export const Index = () => <Tooltip tip="An Algolia index is a searchable dataset that consists of records and configuration settings. These settings define how the records are searched and ranked.">
    index
  </Tooltip>;

Before going live, make sure to follow these steps when you moving your store to production:

<Steps>
  <Step title="Change index prefix">
    Go to the Algolia configuration in Magento and change the <Index /> prefix to be unique for the production environment.
    For example `magento2_prod_`.

    <img src="https://mintcdn.com/algolia/6YAuCqOjAR64l9hZ/doc/integration/magento-2/getting-started/moving-to-production_index-prefix.png?fit=max&auto=format&n=6YAuCqOjAR64l9hZ&q=85&s=635daa540ccb0ea586e6231dd3fdd217" alt="Screenshot of the 'Credentials and Setup' section with an arrow pointing to the 'Admin API key' field." width="2678" height="1258" data-path="doc/integration/magento-2/getting-started/moving-to-production_index-prefix.png" />

    <Info>
      Each environment (testing, staging, production) must have a unique index prefix.
      If the index prefixes are the same,
      the environments overwrite each other's data and
      searching on production might return data from the staging environment.
    </Info>
  </Step>

  <Step title="Reindex data">
    After changing the index prefix,
    the indices with the new names need to be created.
    You can achieve this by [reindexing the complete catalog](/doc/integration/magento-2/how-it-works/indexing).

    After reindexing,
    your search is ready to be used in production.

    <Info>
      If you enabled the indexing queue in your new environment and want it to run automatically,
      make sure to add the cron job to that environment.
    </Info>
  </Step>
</Steps>