Forga Migration Export

By Dominik Shaim Ulrich

0+ active installationsVersion 1.0.16

Export WooCommerce catalog, customers, and orders to XML files for migration to Forga.

Description

The plugin adds one WooCommerce administration screen with three download links:

  • catalog.xml: products, variations, prices, tax rates, stock levels, weights, GTIN codes, images, and category paths used by products
  • customers.xml: registered customers and their billing and shipping addresses
  • orders.xml: orders, address snapshots, line items, shipping, payment, discounts, fees, and refunds

Drafts, private products, and products hidden from the catalog are exported too, marked as hidden, so the new store keeps them unpublished. Disabled variations are marked as hidden as well.

Files are streamed directly to the browser of a signed-in user who can manage WooCommerce. The plugin does not send data to an external service, create a publicly accessible file, require an API key, or run in the background.

Data that is not exported

  • Passwords or their hashes. Customers set a new password in the new store.
  • Custom fields and prices calculated by other plugins. These require separate mapping.
  • Categories without products. The catalog format carries category paths, not a separate category tree.

Installation

  1. Upload the ZIP through Plugins > Add New Plugin > Upload Plugin.
  2. Activate the plugin.
  3. Open WooCommerce > Migrate to Forga and download the three files.
  4. After the migration, deactivate and delete the plugin. It leaves no stored data behind.

FAQ

Who can access the exported data?

Only a signed-in user with permission to manage WooCommerce. Download links are protected by a time-limited WordPress nonce, and the export is not stored on the server.

Can it handle a large store?

XML is streamed in batches, so the entire catalog is not held in memory. Export duration depends on the amount of data and hosting performance. Keep this tab open until the file has downloaded.

Changelog

1.0.16

  • A variable product with an SKU of its own carries that SKU as its code, so the new store finds it by the SKU even when every variation has an SKU of its own. A variable product without an SKU carries no code, as before. A product an earlier transfer already created under a generated SP- code keeps that code when it is transferred again.
  • A customer who never entered billing details carries the first and last name of the account details, so the new store no longer refuses the account for a missing name. A customer with billing details keeps the billing name.

1.0.15

  • The catalog carries the address of the brand page of a product, so the new store redirects the old brand page to the page of the brand there. Only a brand taxonomy the store shows to its customers has such a page. A store with plain permalinks, which names the page by a query string, exports the brand without it.

1.0.14

  • The catalog carries the product tags, so the new store can find a product by them.

1.0.13

  • Products and variations carry their weight in kilograms, converted from the weight unit of the store, and their GTIN, UPC, EAN, or ISBN as the EAN. A variation without a weight of its own carries the weight of its product, as WooCommerce counts shipping with it. A variation without a GTIN of its own carries none, and stores on WooCommerce older than 9.2, which has no GTIN field, export without it.
  • The up-sells of a product leave as its alternative products, so the new store offers the same products instead of it. They never leave among the related products, which still carry the cross-sells. An up-sell naming a variation leaves as its product, and one naming a product that is gone from the store or not exported is left out.
  • The customers file can say that an account is switched off. WooCommerce keeps no such state for a customer, so the file of a WooCommerce store does not change; the version follows the OpenCart packages, which export it.

1.0.12

  • The catalog, customer, and order files state the version of their format, so a store that does not read it yet says so instead of importing the file differently.

1.0.11

  • The customers file can carry the products a customer saved to a wishlist. WooCommerce keeps no wishlist without an extension, so the file of a WooCommerce store does not change; the version follows the OpenCart packages, which export the wishlist.

1.0.10

  • The cross-sells of a product leave as its related products, so the new store links the same products. A cross-sell naming a variation leaves as its product, and one naming a product that is gone from the store or not exported is left out.

1.0.9

  • The catalog file can carry SEO titles and descriptions for the sources that hold them. WooCommerce itself keeps them in other plugins, so its export does not change.
  • An attribute hidden on the product page no longer leaves among the parameters the new store publishes. It leaves in the internal note of the product, where customers do not see it.

1.0.8

  • A product or variation on sale leaves at its regular price with the sale price and its days as an action price, so the new store ends the sale when WooCommerce would. A running sale used to leave as the regular price and never ended.

1.0.6

  • A picture without alt text leaves without one. It used to carry the title of its attachment, usually the name of the uploaded file, which the new store would show and read out as the description of the picture.

1.0.4

  • A variation without an SKU of its own leaves under a code of its own instead of the SKU of its product, and a product without an SKU under a generated code, so they no longer make the import refuse the whole catalog.
  • The export tries the file before the download starts. An order without items, a product with no variations, or another row the export cannot carry, is named on a page in the administration instead of in a comment at the end of an incomplete file.
  • Czech and Slovak translations load on WordPress 6.0 to 6.4 too, where version 1.0.3 stayed in English.

1.0.3

  • Drafts, private products, and products hidden from the catalog are exported marked as hidden, so the migrated store does not publish them. Disabled variations are marked as hidden too.
  • A published product carries the address of its product page, so the new store can redirect the old address to the product.
  • The version follows the OpenCart packages: all migration packages are released under one number.
  • Shipping and fee lines carry the tax rate the order was charged at instead of a ratio of rounded amounts.
  • Orders carry the WooCommerce status key, so translated status names pair with the statuses of the new store.
  • Czech translation: corrected the introduction text.
  • Slovak translation.

1.0.0

  • Initial release: export the catalog, customers, and orders.