A retail data migration
Runit→Shopify POS
A specialty retail catalog needs more than a list of product names. We review how Runit style and variant records will become Shopify products and options, with a clear match for each SKU and barcode.
Plan this migration Data migration: $2,999. Scope confirmed before booking.The records we review.
- Products & variants
- Style, size, and color relationships
- SKUs & barcodes
- Identifiers used across your stores
- Customers
- Supported fields and matching decisions
- Opening inventory
- Quantities mapped to each location
- Existing destination records
- Products and customers already in your next system
The decisions
we make first.
Source access
Review representative exports and the available extraction method.
History & balances
Assess sales history, gift cards, loyalty, and credits separately.
Test & acceptance
Agree the records and checks before the final transfer.
Keep the detail behind every style
A specialty retail catalog needs more than a list of product names. We review how Runit style and variant records will become Shopify products and options, with a clear match for each SKU and barcode.
If your ecommerce store already uses Shopify, we first check the existing catalog. Matching the correct products helps prevent a second set of records from being created for the same merchandise.
Review customers and location stock separately
Your plan maps opening quantities to the agreed Shopify locations and identifies the customer fields that can transfer. It also addresses conflicting identifiers and duplicate customer details.
Historical receipts, gift cards, store credit, and loyalty require individual review. A customer contact import alone does not recreate purchase history.
Confirm the move before booking
We inspect representative Runit exports and confirm access before accepting the project. The $2,999 flat fee covers the agreed data migration, including preparation, a test import, the planned production transfer, and reconciliation.
Directional data plan: Runit to Shopify POS
This is a planning matrix for assessment, not evidence of a completed transfer. The included fields and receiving method are confirmed from authorized samples before booking.
| Dataset | Source evidence | Receiving decision and acceptance |
|---|---|---|
| Products and variants | Account-authorized reports or a vendor-approved data extract; inspect actual style and SKU fields. | Current Shopify product CSV or eligible migration app; customer CSV and inventory workflow are separate. |
| Identifiers and existing records | API documentation is supplied by request; required fields and access are not verified by the public overview. | Inspect existing products before selecting create/update behavior; history requires another method. |
| Customer contacts | Obtain a separate customer sample with source IDs and duplicate candidates. | Confirm supported fields and match rules; reconcile created, matched and rejected profiles. Contacts do not establish transferred balances. |
| Opening inventory | Identify each source store, quantity state and export time. | Map each store to the receiving location and compare each included variant/location pair after the test. |
| History and liabilities | List required receipts, gift cards, credit, loyalty and open orders separately. | Approve a specific native method, usable archive or exclusion for each. Do not infer support from the catalog import. |
Runit styles into Shopify products
Agree which Runit style becomes a Shopify product and which sellable size/color records become its variants. Inspect a complete style export and map the outlet stock separately from product creation. Do not infer that a Runit report includes every required field.
Acceptance before production
Choose a full style with several variants, an unusual barcode, an existing customer and stock in two locations where relevant. Record expected grouping, identifiers and quantities before loading it. Compare the returned destination records with the source crosswalk, resolve rejected rows and have the retailer approve exceptions.
Agree the final snapshot, trading changes and recovery action before the production transfer. Hardware, staff training and ongoing ecommerce or accounting connections have separate implementation owners. Correction responsibilities and support duration belong in the written scope.
Official references
Your systems. Your next chapter.
From the first export to the final review.
Tell us where your data is today, and where you’d like to go. We’ll help you understand the next step.
Check my migration Retail data migration for $2,999. Scope confirmed before booking.