Skip to content

Migrate a Legacy Yepsta Product Catalog

The legacy migration workflow moves an exported product catalog from my.yepsta.com into the current Product Manager.

At a customer-friendly level, the package contains catalog information, categories, products, optional migration warnings and included category or product images. Yepsta can map the supplied product and category identities, import featured images and bring in supported gallery images.

Do not rename files or restructure the ZIP after export.

  • Export a current product and stock copy from the destination business.
  • Confirm the destination locations and category conventions.
  • Remove obvious duplicate SKUs or barcodes in the legacy catalog before export where possible.
  • Start with a controlled business window when product and stock edits can pause.

Open Catalog & Inventory → Products, open Import, then choose Import from my.yepsta.com.

Migrate the legacy catalog
  1. Choose the Legacy ZIP exported from my.yepsta.com.
  2. Select Skip existing when destination records must remain unchanged, or Update existing when the reviewed legacy values should update matched records.
  3. Select Validate Legacy ZIP.
  4. Open the import job and review categories, products, warnings, image results and opening-stock effects.
  5. Do not continue if matching, tax, price, location or stock results are unclear.
  6. Commit the reviewed job once.
  7. Wait for Completed, Completed with errors or Failed before deciding the next step.

Yepsta creates or updates the supported category and product records, imports available images and records supported opening-stock movements. A warning or failed row does not mean the successful rows were undone.

  1. Review the job summary and every warning or error.
  2. Open a sample from each category and check name, SKU, barcode, pricing, HSN, GST and active state.
  3. Check featured and gallery images for a representative set.
  4. Review tracked stock by location and its Ledger.
  5. Test one product in POS and one active product in the public store.
  6. Import corrected exceptions separately rather than rerunning an already successful package.

An owner can use Rollback Legacy Import on an eligible completed or failed legacy job that has not already been rolled back. Use it promptly after confirming the migration was wrong, then review the reported rollback result. Records that now participate in later catalog activity may not all be removable safely.

Last reviewed: