HomeGuides
Submit Documentation FeedbackJoin Developer CommunityLog In

Importing catalog data

This topic explains options for importing catalog data between e-commerce sites.

This topic explains options for importing catalog data between e-commerce sites, including the addition of metadata in multiple languages.

Classes in this topic are in the following namespaces: 

  • Mediachase.Commerce.Catalog
  • Mediachase.Commerce.Storage

📘

Note

You should not import data directly into the catalog system database unless you have a full understanding of how it works.

Import scenarios and options

You can import catalog data using these methods.

  • Through the import/export API
  • Use the Optimizely Service API to import the catalog XML.

Catalog data from another Episerver Commerce site

If you are moving a catalog from another Episerver Commerce site to your Episerver Commerce site, a catalog import and export feature uses XML to make this task straightforward.

Catalog data from a non-Episerver Commerce site

CSV import

If moving data from a non-Episerver Commerce site to an Episerver Commerce site, you can use the catalog CSV import feature. The CSV import requires you to map fields from the non-Episerver Commerce catalog system to matching catalog metadata fields in the target Episerver Commerce site. This can be problematic because catalog system metadata fields may differ from one implementation to the next, depending on how the catalog system is configured.

Managing versions when importing

To improve performance by eliminating previous versions, see the blog post Clear version history for saved catalog content by Magnus Rahl.


What’s Next
Did this page help you?