Going to production

This is for:

In this article

When pushing your changes to production, you must ensure that you migrate your entire organization, including your Coveo settings.

This page gives you the leading practices to migrate your development environment to a production environment, which is the last step of the Coveo for Salesforce integration.

You must ensure that:

You install the same version (see Identifying your Coveo for Salesforce version).

When your versions differ, you should upgrade Coveo for Salesforce to the same version (see Upgrading the Coveo for Salesforce application).
Your selected users can access your Coveo components (see Grant users access to your Coveo Lightning components or Grant users access to your Coveo Classic components).
You created a dedicated Salesforce crawling user.
Your change sets are working (see Change Sets Best Practices).
Your components are deployed and accessible to the appropriate users (see Deploying Components to Production and Grant users access to your Coveo Lightning components or Grant users access to your Coveo Classic components).
Your sandbox and production Salesforce organizations are respectively linked to your sandbox and production Coveo organizations (see Link to an existing organization).
You transfer your Coveo content:
- Your query pipelines (see Manage query pipelines)
- Your pipeline extensions (see Add or edit an indexing pipeline extension)
- Your sources (see Add or edit a source and Manage source mappings)
- Your custom components (see Adding JavaScript to the Coveo for Salesforce Lightning components with custom code)
- Your security identities (see Manage security identities)
Your Community configuration is the same as in your Sandbox (see Deploying Communities).