Skip to content

01AI and integrations · module

Shoptet e-shop migration

Migrates products, orders and customers from Shoptet to Draivix without duplicates

  • Product
  • Product category
  • Sales order
  • Company
  • Contact
  • Import run
11
capabilities
6
record types
3
automations
5
integrations and AI tools

02What the module does

Less routine. More value.

The Shoptet integration transfers your e-shop’s products, categories, orders and customers into Draivix. Repeated runs update existing records instead of creating duplicates, so you can run Shoptet and Draivix in parallel during the transition. Data flows one way, from Shoptet into Draivix.

  • Migration starts with the store archiveThe migration starts by downloading the store archive via administrator access to Shoptet. The password is read from a protected file or entered manually.
  • A transfer you can monitorThe archive is transferred into Draivix as a tracked import run in the ETL module, which manages data transfers. You can see what was loaded and where any error occurred.
  • Catalog imported from the feedProducts and categories are loaded from the XML product feed—your e-shop’s data file—so you don’t have to re-enter your catalog in Draivix manually.
  • Orders loaded from the exportOrders are loaded from the XML order export. Your sales orders are then available in Draivix, ready for follow-up processing.
  • Customers from a CSV fileYou load customers via a manual run from a CSV file—a standard spreadsheet export—transferring your customer database without manual retyping.
  • Records are matched automaticallyOn every run, the system looks for an existing record by its Shoptet identifier, product code (SKU), order number, company registration number and email. It updates matches and creates new records as needed.
  • Repeated runs without duplicatesRepeated runs update existing records instead of creating new ones. That lets you run Shoptet and Draivix side by side during the transition without duplicate products or customers.
  • Accurate order status mappingOrder statuses are converted using your configured lists of completed and canceled statuses, so each order in Draivix reflects how it finished in the e-shop.
  • Parallel run with daily updatesOnce enabled by an administrator, Draivix pulls product and order changes every day. Synchronization is disabled by default, and data flows strictly from Shoptet to Draivix.
  • Archive as your store’s storefrontA verified archive can be published as a storefront in the Website module, making your store presentation available directly in Draivix.
  • Per-record error loggingSynchronization errors are logged against each individual record. You can see exactly what needs fixing without hunting through the entire transfer.

03How it works

How it works step by step.

  1. How the migration works

    The migration starts by downloading the store archive via administrator access to Shoptet; the password is read from a protected file or entered manually. The archive is then transferred into Draivix through the ETL module. Every transfer is a tracked import run with a status, so you can see what was loaded and where any error occurred.

    Read in detail

    A verified archive can be published as a storefront in the Website module. Products, categories, companies, contacts and sales orders receive a Shoptet identifier so the system recognizes them on subsequent runs.

  2. Ongoing synchronization

    While running both systems in parallel, Draivix can pull daily changes from Shoptet feeds: products from the XML product feed and orders from the XML order export. The daily job runs at 3:41, but does nothing until an administrator enables synchronization; it is disabled by default. Customers are loaded only via a manual run from a CSV file.

    Read in detail

    Order statuses are mapped according to configured lists of completed and canceled statuses. The default currency is CZK. The order feed URL is stored as a secret value.

  3. Duplicate-free matching

    On every run, the system looks up an existing record by its Shoptet identifier, product code (SKU), order number, company registration number and email. If found, the record is updated; otherwise, a new one is created. Repeated imports never create duplicate products or customers.

    Read in detail

    Imported orders trigger standard events, so your workflows in the Automation module respond to them—for example, by flagging a customer’s first order.

  4. Good to know

    Data flows only from Shoptet into Draivix. As long as synchronization is enabled, the next run will overwrite edits made to mapped fields in Draivix. Errors are logged separately on each record. The transfer stops after the first pipeline stage in which records fail; records already written remain in place, and a transfer from Shoptet cannot be rolled back automatically.

04What runs automatically

Automations that save time.

  1. Nightly sync of Shoptet changes

    The daily ShoptetSync job at 3:41 loads products and orders if synchronization is enabled. By default, it is disabled and the job does nothing.

  2. Every transfer has its own log

    Each transfer creates a tracked import run with a status. You can see what was loaded and where any error occurred, taking the guesswork out of migration progress.

  3. Workflows respond to imports too

    When an order is imported, it triggers a standard event. Your workflows in the Automation module respond to it—for example, by flagging a customer’s first order.

External integrations

  • Products from the Shoptet feedDraivix reads products and categories from Shoptet’s XML product feed. Data flows one way, from Shoptet to Draivix, leaving your e-shop untouched.
  • Orders from the Shoptet exportDraivix reads sales orders from Shoptet’s XML order export. The order feed URL is stored as a secret value, and the default currency is CZK.
  • Customers from the Shoptet exportYou load customers from Shoptet’s CSV customer export via a manual run. This part is not synchronized daily; you run it whenever you need it.
  • Archive from Shoptet administrationDraivix downloads the store archive via administrator access to the Shoptet admin panel. The password is read from a protected file or entered manually.

What the AI agent handles

  • Check import status in chat

    On request, the AI assistant shows the status of an import run using the general ETL tool. You can check migration progress right from chat without opening the overview.

A person approves whenever money, a customer, or an exception is involved.

05Frequently asked questions

How do I migrate my e-shop from Shoptet to Draivix?

The store archive is downloaded via administrator access and transferred through the ETL module as a tracked import run. Products and orders can then be pulled daily from Shoptet feeds.

Will repeated imports create duplicates?

No. Records are matched by their Shoptet identifier, SKU, order number, company registration number and email, and repeated runs update them.

Does Draivix write changes back to Shoptet?

No. Data flows only from Shoptet to Draivix, and while synchronization is enabled, subsequent runs overwrite changes made to mapped fields in Draivix.

Are customers imported too?

Yes, from a CSV file via a manual run. Daily synchronization loads only products and orders.

Let’s start together

Tell us how your business works.

We will show you what a system that takes over part of that work could look like.

Book a consultation