A retail data migration
Shopify POS→Runit
Are you replacing Shopify POS while keeping your Shopify online store? That decision affects which records move and how inventory will be managed after the change.
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.
Decide what stays connected
Are you replacing Shopify POS while keeping your Shopify online store? That decision affects which records move and how inventory will be managed after the change.
We review your catalog and location structure, then identify how products, variants, SKUs, barcodes, and customer records need to map into the proposed Runit setup.
Check the destination before committing
Runit provides data access and integration capabilities, but the required inbound method must be confirmed for your project. We review sample files, field requirements, and any vendor coordination before booking.
Gift cards deserve early attention because a standard Shopify export does not include complete card codes. Historical orders, loyalty, and store credit also need separate decisions about import or continued access.
Know the scope and price
The service is $2,999 for the confirmed data migration scope. Your plan defines the included records, supported transformations, test import, final stock snapshot, and reconciliation, alongside any dependencies for the wider Runit implementation.
Directional data plan: Shopify POS to Runit
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 | Product/variant CSV, customer CSV and inventory export by location; keep the files separate. | Vendor-confirmed receiving fields and import method, agreed with the Runit implementation owner. |
| Identifiers and existing records | Keep Shopify IDs and handles if the online store remains; contact CSV does not carry order history. | Inbound catalog method, matching behavior and quantity semantics need explicit confirmation. |
| 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. |
Shopify catalog continuity
If Shopify ecommerce stays, retain its product and variant identifiers and name the owner of future stock updates. Runit receiving fields and the authorized import procedure must be confirmed with the implementation owner before a transfer is accepted.
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.