Concepts of Import Export Tool

Elastic Path objects are dependent on each other and the dependencies are complex. When moving data between Elastic Path deployments, data exported from one deployment might cause conflicts with data in the other deployment.

Before using the Import-Export tool, ensure that you understand how Elastic Path objects are related. This section describes those objects and the relations, and provides an overview of the strategies you can use to prevent import conflicts.

Supported Object Types

You can export or import the following objects using Elastic Path’s Import-Export Tool:

• Commerce Manager
  • CM Import Job
  • CMUser
  • User Roles
  • Tag Groups
  • System Configuration
• Customer
  • Customer
  • Customer Profile Attributes
• Data Policies
  • Data Policies
  • Customer Consents
• Search
  • Facets
• Product and Catalog
  • Catalog
  • Categories
  • Products
• Price and Payments
  • Amount
  • Price Lists
  • Price List Assignment
  • Payment Gateway
• Coupons and Promotions
  • Coupon Set
  • Gift Certificate
  • Promotions
  • Condition Rules
  • Saved Conditions
• Shipping and Tax
  • Shipping Region
  • Shipping Service Level
  • Tax Code
  • Tax Jurisdiction
• Store and Warehouse
  • Stores
  • Store Association
  • Cart
  • Warehouses
  • Inventory
  • Attribute Policy
  • Store Customer Attribute

Many of these objects are linked to other objects in the system. Some of those linked objects are required dependencies. During export, these dependencies are retrieved and exported automatically. For example, a product must be associated with at least one category and at least one catalog. So, when a product is exported, all its associated categories and catalogs are also exported.

Other linked objects are optional dependencies. You can specify whether you want to include optional dependencies. For example, assets, such as images, are optional dependencies, and you can choose whether you want to include them when exporting objects.