Import/Export versus Site Import/Export, replication and automated feeds
Key Takeaway
Use import and export to move data between B2C Commerce and outside systems, and use replication to copy data and code from staging to development or production. Replication doesn't run on sandboxes, so each sandbox must import the same feed files itself.
B2C Commerce has several ways to get data into and out of an instance database. Import and export move data between an instance and outside systems. Replication copies data and code from the staging instance to development or production. Sandboxes, staging, production and development instances each get new data in their own way, so you need to know which method fits which instance.
Import and export versus replication
Import and export and replication answer different questions.
| Import and export | Replication | |
|---|---|---|
| What moves | Data | Data and code |
| Where it moves | Between an instance and external systems, such as inventory, ordering, pricing or marketing systems | From one instance to another, after the data is already in a B2C Commerce database |
To transfer data between an instance and an external system, use import and export, not replication.
A store keeps its product descriptions in an outside product system. Loading a file of those descriptions into the staging instance is an import. After the descriptions are in the staging database, copying them to production is replication.