Obtain a real export sample before approving the scope
Start the migration and launch review with a sample taken from the actual Ticimax account. Products, customers, orders and content may use different access methods. Account permissions, package conditions and existing connections must be established before an all-data migration commitment can be meaningful.
Inspect product codes, variation relationships, category fields, image URLs and update information in the sample. A feed intended for advertising or a marketplace may contain products but no customer or order history. A channel feed and a complete store inventory are different evidence sources.
When access is limited, examine support requests, available API access and controlled export options. Do not presume direct access to the entire source database. Record available fields and gaps. The sample and field mapping document should determine the migration scope rather than being collected after a fixed promise has already been made.
Accessible records
For each record type, identify the method, authorised owner and sample output. Missing fields must be visible before transfer begins.
Transfer evidence
Open a sample in the target store and demonstrate that required information is usable. Producing an export file is only an intermediate task.
Excluded history
Agree how inaccessible historical records will remain safely available or archived. An unexplained omission cannot be treated as completed work.
Map product codes and variation relationships deliberately
The product data quality checklist helps establish whether codes are genuinely unique. Distinguish the Ticimax product ID, SKU, barcode and supplier reference. If the ERP expects a different identifier from the one visible in the store, keep an explicit mapping rather than silently replacing either value.
For an illustrative fashion store, colours might be separate products while sizes belong to variations. Decide how this becomes the target product and option structure alongside customer selection, image association and inventory behaviour. Similar product titles are insufficient evidence that records can safely be merged.
Evaluate categories and brand pages against the new collection architecture. Include promotional collections, unpublished items and unavailable options in validation. Product count comparison is useful, but evidence that variants belong to the correct product and preserve their stock relationship is a stronger acceptance condition.
FROM READING TO A NEXT STEP
Map the critical connections in your Ticimax move
Share a sample export and the ERP and marketplace providers you use. We can separate transferable records from workflows that need rebuilding.
Define the inventory authority across ERP and marketplaces
Use the ERP and store integration checklist to identify the authoritative system for stock, prices and orders. A marketplace connection running through Ticimax does not automatically become a Shopify connection when the storefront launches. Recheck the connector, permissions and direction of each data flow.
For example, inventory may originate in an ERP, web orders may be sent back to that ERP, and marketplace orders may pass through another integrator. Draw these paths separately. The same sale must not create duplicate orders or decrement stock twice through independent connections.
If marketplaces remain open, define the final synchronisation point and the condition for stopping the old connection. State who acts when an update is late, which record may be safely resent and how the resulting state is reconciled. These operational decisions are part of readiness, rather than problems deferred until the first live failure.
Field ownership
Stock, price, description and order status can have different authorities. Assign the final editing responsibility for each field to one source.
Channel evidence
Distinguish web and marketplace test transactions. Verify in both source and destination that the same order has not been recorded twice.
Re-test promotions and local operating rules
The Shopify launch checklist checks payments, shipping and notifications in the target environment. An unchanged promotion name can conceal different stacking, minimum-value or product-scope behaviour. Compare rules using realistic baskets rather than screenshots of settings.
Useful illustrative cases include baskets just below and above a discount threshold, mixed-product orders, partial refunds and free-shipping conditions. A displayed instalment or delivery option does not establish that the provider account is eligible. Confirm the relevant country, account and application conditions with the responsible team.
Identify the source of order confirmations, tracking messages and marketing communication separately. Legacy automation and new applications should not both send the same notification. Test account access and the customer explanation as well. Existing communication permissions should not be treated as permission for unrelated new purposes.
Match Ticimax URLs to a meaningful new destination
A site migration SEO plan should inventory old product, category, brand and content addresses. One export may miss valuable pages. Existing sitemaps, accessible content and available search information provide complementary evidence and should be reconciled rather than treated as interchangeable lists.
Choose a useful destination for every important address. When moving a category, examine its explanation, filtering need and associated products together. If a campaign has ended, decide whether there is a relevant replacement instead of presenting the old campaign as still available. Preserve useful information without preserving a misleading offer.
Before release, test destinations, titles, internal links and access conditions. Keeping the domain does not mean URL structures and content signals remain unchanged. Use the mapping register to investigate later indexing or traffic changes. It supports risk management; it does not establish a guarantee that rankings will remain identical.
Merge the inventory
Include brand, category and important campaign pages beside products. Keep a note of the source for each address.
Select the replacement
Explain the customer need answered by the new destination. Avoid sending every old URL to the homepage.
Record the outcome
Demonstrate that the destination loads, presents the correct content and is accessible under the intended publishing rules.
Leave a clear cutover and operating handover
A store management plan clarifies where new orders will be handled and who owns exceptions. Products, stock and orders changed after the rehearsal import need a final delta transfer. Write the cutover point in terms that technical and operational teams can both apply.
The order and inventory owners should be available alongside technical support on release day. Reconcile actual target-store transactions with the operating records. If rollback becomes necessary, explain how new payments and orders will be retained. Reversing DNS alone is not a complete recovery plan for a store that has already received sales.
The handover should contain field mappings, channel connections, sample transaction evidence, redirect tests and owned exceptions. This allows a store owner to distinguish data migration from new development and ongoing operations, making the proposal and acceptance decision more concrete.
Get the checklist and discuss your scope
Your email and phone are used for this request. This does not subscribe you to a newsletter.
BEFORE YOU DECIDE
Frequently asked questions
Is a Ticimax XML export enough for the whole migration?
It depends on the feed purpose and included fields. A product feed may omit customers, orders, promotions and custom functionality. Confirm the scope using a real sample rather than the file format name.
Will the current ERP connection work in Shopify?
Verify target-platform support, account access and field mapping with the connector provider. A working source connection does not prove that a target connection is ready or commercially included.
Must marketplaces close during the move?
That depends on stock authority and integration design. If channels stay open, document when old connections stop and how recent transactions are reconciled. Do not let two independent paths process the same sale.
Can promotions be copied unchanged?
Names alone are insufficient. Test conditions, combinations and refund effects with representative baskets. Some rules may require a different application or development decision in the target platform.
How should customer and historical order transfer be accepted?
Compare agreed record ranges, counts and representative fields. Also verify that historical imports do not unintentionally create fresh fulfilment work or customer notifications.
When is the checklist complete?
When evidence for orders, stock, payments, notifications and redirects has been accepted, and remaining exceptions have owners. A domain that resolves to the new storefront is only one step in that process.
LET’S DEFINE THE SCOPE
Map the critical connections in your Ticimax move
Share a sample export and the ERP and marketplace providers you use. We can separate transferable records from workflows that need rebuilding.
Review migration scope