Guided apparel migration

A new platform.
The same product details.

TelaIQ can preview tested product-export column shapes from Shopify, Lightspeed, and Square, along with a generic CSV format. Catalog mapping, historical records, validation, and cutover are reviewed as separate parts of the migration plan.

Plan a migration

Shopify exportsLightspeed exportsSquare exportsGeneric CSV

Source exportFlat variant rowsStyle 101 · Black · MStyle 101 · Black · LStyle 101 · Ink · M

TelaIQ previewStyle × color × sizeStyle 101Black · M / LInk · M

After reviewCommit catalogIdentifiers keptStock stays preview-onlyPrices mapped to SKUs

Preview the catalog before commit

Paste a supported export, inspect the preview summary, and validate the mapping before writing catalog records.

Catalog and size matrix

Flat variant rows are grouped into TelaIQ's style × color × size structure using source identifiers.

Barcodes and prices

Supported barcode and price fields map to individual SKUs for review before operational use.

Location-stock preview

On-hand columns can be reviewed and reconciled, but the self-service importer will not post inventory. Stock changes require a governed receiving, count, or transfer workflow.

Repeatable matching

Source identifiers prevent duplicate SKU rows. Every repeat import requires preview and reconciliation.

Historical data is scoped separately

Source quality and export access determine what can be migrated beyond the catalog. The onboarding plan records the agreed fields, checks, and cutover responsibilities.

Suppliers

Vendor records, lead times, contacts, and product mappings are assessed from available exports.

PO and receiving history

Open commitments and historical documents require source-specific mapping and balance checks.

Sales history

Usable transaction history can be evaluated for reporting and demand inputs, with totals reconciled before acceptance.

Controlled cutover

How the migration works

Each gate produces reviewable evidence before the next one begins.

1Provide representative exports

Start with sample catalog data and any historical files required for the proposed scope.

2Map, preview, and reconcile

Review variant grouping, identifiers, prices, and stock totals in a non-production environment.

3Approve a controlled cutover

Document final exports, validation owners, timing, rollback, and acceptance checks before launch.

Plan the cutover around the source data.

Preview catalog changes before they are committed

Define historical scope from files that can actually be exported

Reconcile variant counts, prices, stock, and agreed financial totals

Record cutover ownership, timing, rollback, and acceptance checks

A representative source export is the starting point for every migration estimate.

Questions & answers

Catalog migration details.

Which catalog formats can TelaIQ preview?

The current importer accepts tested column shapes from Shopify, Lightspeed, and Square product exports plus a generic TelaIQ CSV format. Representative files must be previewed because export schemas vary by source and version.

Which fields are supported?

The importer can commit supported styles, colorways, sizes, SKUs, barcodes, and prices after preview. Location-stock columns are recognized for preview and reconciliation only; they are not posted by the self-service importer.

What about suppliers, purchase-order history, and past sales?

Those records are outside the self-service catalog importer. Available source files, mapping requirements, reconciliation, and any historical migration are scoped separately during onboarding.

How is cutover risk handled?

Start with representative export files, review the preview in a non-production environment, reconcile counts and prices, and agree on a cutover plan before operational use.

What does migration cost?

Migration scope and cost depend on the source data and required history. Both are confirmed in writing for each pilot.

Start with the catalog.

Review source files, required history, and product fit in a guided demo.