Moving from SHOPLINE to Shopify in Hong Kong: a practical migration guide

Moving a store involves more than uploading products. Customer sign-in, outstanding orders, rewards, payment settlement and old Google links all need a home. A useful migration plan tells your team what will move, what must be rebuilt, how it will be checked and who handles business during the changeover.

This guide explains how a Hong Kong merchant can prepare a SHOPLINE-to-Shopify move, from the first export to post-launch monitoring. The aim is to reduce disruption and make omissions visible. No migration process can promise unchanged rankings, uninterrupted access for every visitor or automatic compatibility between platforms.

1. Decide what the move needs to improve

Start with the business requirement: an international storefront, a particular marketing integration, better stock coordination or a simpler customer journey. Check the current SHOPLINE configuration and the proposed Shopify setup against the same requirement. A limitation in your present subscription or integration does not establish that an entire platform lacks the capability.

List the functions staff use each day, including bundles, pre-orders, discounts, membership pricing, pickup points, returns, invoices and subscriptions. For each, identify the Shopify native feature, app or custom integration that will replace it, its owner and its recurring cost. Test the functions that justify the move before committing to a launch date.

The budget should include migration work, theme and content rebuilding, app subscriptions, payment charges, staff training and a period of overlap between platforms. Separate confirmed supplier quotes from contingencies. Our Hong Kong Shopify pricing guide explains the cost categories; a promised conversion uplift should not be treated as funding for the project.

2. Establish what your SHOPLINE store can export

SHOPLINE has different products, regional configurations and subscription entitlements. Confirm the available exports in your own Hong Kong admin rather than following a tutorial for another version. Its regional help centre documents product bulk-update exports, customer reports and order reports; these files are starting material, not Shopify-ready imports. SHOPLINE product export guidance and customer export guidance describe their respective selections.

Download an initial complete export and keep an unchanged copy with the extraction time, store timezone, selected fields, filters and covered date range. Confirm every split file arrived. Use SHOPLINE's order export guide to check the selected report scope. Separately confirm with support how to retrieve older or archived records in your store, so they are not silently omitted.

Include media, page content, translations and app-held information in the inventory. A sales report is not a backup of theme code, customer messages or a loyalty ledger. Restrict access to customer exports, use secure transfers and agree how working copies will be removed after acceptance.

Data migration map

Shopify's migration guide distinguishes product and customer CSV imports from the app/API routes needed for historical orders. An export's existence does not prove that every field has an equivalent destination.

3. Clean and rehearse before the full import

Prepare a field map linking the source product, variant, customer and order IDs to their new records. Use this mapping to identify updates and avoid importing the same record twice. Preserve the original identifiers in an appropriate field or controlled migration record so staff can trace an exception.

For products, settle how colours, sizes and other options will be represented. Check duplicate or missing SKUs, leading zeros in barcodes, prices, tax treatment, shipping weight, publication status and language variants. Do not let spreadsheet software silently convert long identifiers or telephone numbers.

Use Shopify's current sample CSV instead of copying an old template. Its product CSV documentation explains column dependencies and image handling. Keep source images accessible while Shopify ingests them, then verify the imported media and variant associations. Do not cancel the old store while the new store still relies on its image links. Multi-location quantities require the appropriate inventory CSV or inventory integration.

Rehearse with representative records: a product with several options and images, an out-of-stock variant, Chinese content, a customer with missing email, a refunded order and an unfulfilled order. Include the cases your business actually uses. Agree expected results before importing.

Import products, then customers, then historical orders that need those links. Review failures and reconcile record counts, variant counts and sample field values after each stage. For financial records, also reconcile totals by currency and period; a matching row count alone cannot show that discounts, refunds or taxes are correct.

4. Make customer access and member benefits explicit

Customer records and working customer accounts are separate checks. Shopify does not import external passwords through a customer CSV, nor does that file import order history or its Total Spent and Total Orders values. Refer to the customer CSV limitations.

For Shopify's current customer accounts, customers can sign in using a code emailed to the address associated with their profile. Plan how customers without a usable email address will receive help. If the store retains a legacy password-based setup, test its invitation and password-setting flow separately. Multipass is an identity integration, not a tool for recovering SHOPLINE passwords.

Tell customers how to sign in, where to find past orders and how rewards will work. Importing a VIP tag does not create a discount rule, restore points or establish a credit balance. Reconcile those balances and expiry dates separately, implement the replacement rules and test redemption with customer-facing accounts.

Preserve marketing choices by channel. A customer record is not evidence of permission to receive promotions; an email opt-out should not be overwritten merely because the customer appears in an order export.

5. Separate completed history from work still in progress

Decide which historical orders need to appear in Shopify and which can remain in a secure archive accessible to authorised staff. Test how imported orders appear to customers and in reports. Keep original order numbers, payment references and documents where needed for support and accounting.

Outstanding orders need an operational decision: will the old system finish them, or will the new system take responsibility? Assign each order to one system for fulfilment and refunds. Do not mark every imported record paid and fulfilled; pre-orders, partial shipments, cancellations, refunds and pending bank transfers carry different obligations.

During a rehearsal, inspect order notifications, customer emails, stock changes, fulfilment apps, marketing automations and accounting feeds. Historical imports must not accidentally trigger fresh parcels or repeated welcome messages. Control the relevant settings, document temporary changes and restore the intended live configuration before opening the store.

Recreating an order does not transfer its original payment transaction or the ability to refund it through a new gateway. Keep the old processor accessible for its remaining refunds, disputes and settlements, subject to its terms.

6. Prepare redirects around the URLs customers actually use

Build the old URL list from the sitemap, a crawl, analytics landing pages, Search Console and important advertising or external links. Include products, categories, articles, policies, images where relevant and every language version. Record each old URL, its intended replacement and the result of the redirect test.

For example, an old /categories/summer-sale path might lead to /collections/summer-sale. Use the closest equivalent destination. A discontinued product may have a suitable successor; if there is no replacement, an honest unavailable page or 404/410 may be more appropriate than sending every visitor to the home page.

Shopify redirects have constraints: active pages and reserved paths cannot simply be overridden, query-string URLs may behave differently, and market subfolders need individual consideration. Check the current Shopify redirect rules against your URL list before launch. A successfully uploaded redirect CSV is not evidence that each old link works.

Test important URLs end to end: permanent redirect, no loop or unnecessary chain, correct final page and working language links. Keep useful titles, content, canonical tags and internal links aligned with the new pages. Remove launch-only indexing blocks from the production storefront when it opens.

Google advises expecting ranking fluctuations and retaining redirects for at least a year, ideally longer for links still used. Submit the new sitemap and monitor indexing. Its site move guidance does not promise a fixed processing time or unchanged traffic. A same-domain platform move does not need Search Console's Change of Address tool; assess that tool if the domain or subdomain also changes.

7. Verify Hong Kong checkout and fulfilment as complete journeys

Build a test list from the payment methods customers use today. PayMe, FPS, card payments and wallets each need confirmation for the specific Shopify provider, merchant account, currency and integration. Check account approval, refunds, settlement timing, processing fees and any applicable Shopify third-party transaction fee. Shopify documents its third-party provider model; installing an app alone does not activate a payment method.

A manual FPS or PayMe instruction is a different operating process from a provider that automatically confirms payment. Test success, cancellation, failure and delayed confirmation. Staff must know when it is safe to fulfil, how duplicate notifications are handled and how to investigate an amount that does not match the order.

For SF Express or another carrier, check the actual connector and service agreement. Test Hong Kong address entry, pickup locations, fees, label creation, tracking updates, cancellation and returns. Include mobile checkout in both languages and international destinations if those are part of the launch. Provider test mode is useful, but a controlled real transaction and refund may also be needed before business acceptance.

8. Plan the final handover and its fallback

Build the Shopify store alongside the operating SHOPLINE store, with access and indexing controlled during preparation. This reduces disruption but does not remove the need to coordinate the last orders and stock changes.

Use a rehearsal to estimate the final import window. Then agree a named launch lead, an order cut-off time, customer messaging and stop conditions. The following sequence is a planning example, not a promise of a particular duration:

1. Before the changeover, save the DNS zone, relevant configuration and a recoverable data export. Confirm access to the registrar, DNS host, both platforms and payment providers. Check who handles business email.
2. Freeze catalogue and configuration changes. Pause old checkout or use another tested order-control process, and confirm what happens to existing carts, unpaid orders and payments already in flight. Pause or redirect relevant campaigns.
3. Extract the final changes since the rehearsal, including updates to older orders and customer records. A filter for newly created records alone will miss some changes. Reconcile outstanding orders, available stock and member balances, then import and check the final batch.
4. Connect the domain using Shopify's current instructions and the values shown for the store. Preserve email-related MX and TXT records. Check A, AAAA, CNAME and any Cloudflare or certificate settings; connecting a domain does not require transferring its registration.
5. Verify the primary domain, HTTPS, redirects, account access, checkout, order receipt and fulfilment handoff from the public storefront. Open Shopify checkout only after the agreed acceptance checks pass. Keep checking the old platform for late payments and orders during propagation.
6. If a stop condition occurs, the launch lead decides whether to keep sales paused, repair the issue or return to the previous route. First account for orders and payments accepted by either store. Reverting DNS does not reverse transactions or instantly clear every cache.

Shopify's manual domain connection guide says the domain can take up to 48 hours to become fully live. TLS troubleshooting guidance also allows up to 48 hours for certificate issuance. Choose a low-traffic window with room for troubleshooting; do not promise a ten-minute switch or assume that lowering TTL guarantees one.

9. Agree the launch checklist and monitor afterwards

Use a shared checklist with an owner and evidence for each result:

• Data: agreed import totals, sampled fields, exception list, accessible media and reconciled stock and member balances.
• Customers: tested sign-in, account communications, order visibility and reward redemption.
• Operations: ownership of open orders, successful payment and refund tests, shipping labels and working support access.
• Search: priority URL tests, language links, canonicals, sitemap and production indexing settings.
• Measurement: consent-aware analytics and pixels, purchase event checks and protection against counting the same order twice.
• Recovery: retained exports, old platform access, recorded DNS settings and a decision maker for launch issues.

After launch, review payment failures, late old-store payments, fulfilment queues, stock differences, broken links and customer support reports daily at first. Compare search and sales against a recorded baseline, allowing for campaigns, seasonality and measurement changes. Track Search Console indexing and landing-page traffic over subsequent weeks rather than judging the move from one day's ranking.

Cancel the old platform only after the agreed data, support, payment and retention needs have been met. Some obligations will outlast the storefront change.

Get help assessing the move

Navy FAB's Shopify migration service covers consultation, migration and development, testing, staff training and support. For an assessment, prepare your store URL, approximate product and customer counts, historical order period, app list, outstanding rewards and preferred launch window. These make it possible to agree a concrete scope, exceptions, responsibilities and acceptance criteria before work begins.