Product DocsMenu

Coveo Platform 7.0 >
Administrator Help > Connectors > Sitecore Connector > Migrating from the Legacy Connector

Migrating from the Legacy to the New Sitecore Connector

If you have been indexing Sitecore content before September 2012, you are probably using what is now referred to as the Sitecore legacy connector (see Sitecore Legacy Connector). You may want to take advantage of the improvements with the new connector (see Advantages Over the Legacy Connector).

Note: If you want to index Sitecore 7 content, consider to rather use Coveo for Sitecore (see Coveo for Sitecore).

The main setup difference between the new and the legacy connectors is that the mapping file of the legacy connector contains mapping and connector configuration while the new connector uses separate mapping and configuration files. The new connector also uses a different web service plugin. You can install both web services on the Sitecore server to use the two connectors concurrently while you configure and validate the source created with the new connector.

To migrate from the legacy to the new connector

  1. Migrate the mapping content:

    1. Review the content and format of your legacy mapping file (see Defining a Sitecore Mapping File for the Legacy Connector).

    2. Review the format of the mapping and configuration files of the new connector (see Creating and Using a Sitecore Mapping File and Creating and Using a Sitecore Configuration File).

    3. Split the legacy mapping file content into a mapping and a configuration file.

    Note: The mapping file of the new Sitecore connector does not allow to index metadata of referenced items like the mapping file of the legacy connector did.

    Example: In the Nicam demo site (default demo website installed with Sitecore), a camera contains a field called Accessories. These accessories are built from different templates: Lenses, Flash, or Other Accessories.

    A mapping of the form <Accessories>%[Accessories.Title]</Accessories> to get the Title of referenced accessories is not possible with the new mapping file.

  2. Plan your deployment on a production Coveo server: 

    1. Create a new collection that is not yet part of the scope of search interfaces available to end-users (see Configuring the Scope of a .NET Search Interface).

    2. Create a test search hub with a search interface where you will see search results from the new source (see Creating a Search Hub With the .NET Interface Editor and Creating a Search Interface With the .NET Interface Editor).

  3. Follow the deployment steps to create a source in the new collection using the new connector (see Sitecore Connector Deployment Overview).

  4. Using the test search hub, validate that the source correctly indexes Sitecore items and contains the fields needed to produce rich search results, facets, search box query suggestions, etc.

  5. Put the new source and search interface in production:

  6. Consider removing the legacy stuff:

    1. Delete the legacy source (see Applying an Action to a Collection or a Source).

    2. If applicable, delete the original unused search interface.

    3. On the Sitecore server, uninstall the legacy web service plugin.

People who viewed this topic also viewed