Freeze the source sample and its field definitions
Begin the product data quality review with a catalogue sample from the actual IdeaSoft account. Record selected columns, export time and any filters. A file containing only active products may not cover unpublished records or the complete inventory of historical addresses that the migration requires.
Keep an unchanged source copy and perform conversion on another version. That separation makes it possible to tell whether missing or damaged information originated in the export or the transformation. Leading zeros, long barcodes and Turkish characters can be changed by spreadsheet tools that interpret values automatically.
Check whether special product information, attributes and SEO text are actually present. Accessible product data does not imply that customers or historical orders appear in the same file. Establish the method and scope for each record type before agreeing a migration proposal.
Unchanged source
Retain the raw file with its time and filtering notes. Work on a conversion copy rather than overwriting your only reference.
Field dictionary
Explain every important column and its target equivalent. Distinguish a blank value from a field absent from the export.
Representative sample
Include simple products, variation families, inactive items and records with special information. The first few rows alone are not a sufficient acceptance sample.
Test parent, variation and image relationships
The Shopify launch checklist should demonstrate that a shopper can purchase the intended option. Source parent–variation relationships need an explicit target mapping. Similar product names are not proof that two rows belong to the same family; examine the source code relationship instead.
For an illustrative footwear product, black size38 and white size39 may have different stock and images. Select each representative option, inspect the displayed image and compare the variant placed in the basket. Check that an unavailable combination has not accidentally become purchasable during restructuring.
If image URLs depend on the old account or another provider, record that dependency. Do not close the source account before confirming that the target has accessible, correctly associated files. Media inside descriptions, size charts and download links need their own examples because they can behave differently from the main image gallery.
Relationship evidence
Keep the association between the parent code and child records. Verify expected combinations in the target storefront, not only in the import report.
Media evidence
Check selected options, product cards and description media against the correct item. Demonstrate that necessary files remain accessible after launch.
FROM READING TO A NEXT STEP
Turn your IdeaSoft export into a migration plan
Share a catalogue sample, special product fields and current connections. We can review information gaps and the functionality that must be rebuilt.
Compare prices in the file and in a real basket
From a store management perspective, the meaning of a price field matters as much as its number. Document whether the source value includes tax, its currency and the discount structure. Authorised finance and operations owners should approve the correct use of those settings for the business.
An illustrative product may have a normal price, reduced price and variation-specific difference. Compare the product card, detail page, basket and order total in the same scenario. A correct file value can produce the wrong displayed result when target-store settings interpret it differently.
Shipping dimensions, weight and selling units also affect the transaction. Treating a pack as a single piece, or using the wrong measurement in delivery pricing, is a migration defect. A representative delivery address and complete basket reveal that defect more clearly than a panel screenshot alone.
Make separate decisions for category, brand and content URLs
The site migration SEO plan defines how category and brand pages are represented in the new store. A source category name and system ID do not show that its address or content purpose has been preserved. Specify which products and explanatory information belong to the target collection.
Inventory useful brand descriptions, buying guides and campaign links. Update links embedded inside descriptions to relevant target destinations. When HTML presentation breaks, preserve the useful information while rebuilding the layout. A platform move is not a reason to replace every distinctive explanation with a short generic paragraph.
Select meaningful redirect equivalents and inspect the target pages. If source titles or descriptions are absent from the export, record the gap rather than presuming automatic transfer. Continue monitoring crawl issues and important page performance after launch. Mapping and validation reduce avoidable errors without guaranteeing unchanged organic traffic.
Accept stock, customer and order reconciliation separately
The ERP integration checklist clarifies where target inventory will be updated from. Finishing catalogue import does not establish that the stock connection is working. If source and target identify the same item differently, updates can reach the wrong record until the mapping is corrected.
Customer identity, required history and communication permissions need separate validation. Historical orders should not trigger fresh fulfilment or unintended emails. Decide where orders still being prepared will be completed; they are an operational responsibility, unlike a closed historical archive.
Include sales and product changes made after the rehearsal in the final delta transfer. Equal counts alone are insufficient: inspect representative fields and relevant totals as well. Explain legitimate scope differences in the report. Unexplained differences remain unresolved release risks rather than disappearing under a completed checkbox.
Identifier mapping
Relate the source code to the target record and, where required, the ERP identity. Do not hide missing relationships by generating unrelated replacement codes.
Record reconciliation
Compare products, customers and orders separately. Each difference needs an explanation tied to the agreed scope.
Final delta
Identify changes since the rehearsal. Keep responsibility for each recent transaction traceable throughout the cutover.
Make launch-day tasks understandable to the operating team
The migration and launch checklist brings together domain changes, test purchases, notifications and approval. Write each task as an action with expected evidence. Instead of saying “check orders”, state which representative order should produce which operational result.
Test order confirmations and tracking messages in the recipient experience. Legacy and new automation should not send the same message independently. Customer service must know where to find older orders, how to explain the target account experience and who handles exceptions. This practical handover matters after the launch team steps away.
Keep the source sample, column map, variation and image evidence, price checks, redirect report and owned exceptions in the delivery package. Those records support both release approval and the ongoing maintenance scope. The checklist is a shared acceptance language between teams, rather than a substitute for inspecting the store.
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
Can I upload the IdeaSoft Excel export directly into Shopify?
It needs to match the target format and data relationships. Convert and test representative products first. A familiar file extension does not mean the columns have equivalent meanings in both systems.
Should every available source column be exported?
Select fields according to the migration scope. Check for required special information and SEO copy before transfer, while avoiding unnecessary collection of personal data. Missing information should be an explicit decision.
Why test variation combinations individually?
Total product counts can be correct while option, stock or image associations are wrong. Checking representative combinations on a real product page and order makes those errors visible.
When can the old image links be retired?
After required media are accessible in the target and associated with the correct products. Include media embedded in descriptions so closing the source account does not silently break important information.
Who approves tax-inclusive price behaviour?
An authorised finance owner approves the commercial interpretation of source and target settings. The technical team compares file values and basket results; this checklist is not tax advice.
What belongs in the final migration handover?
Field mappings, reconciled data, variation and image evidence, a representative order, redirect tests and owners for remaining exceptions. Products appearing in the admin is not a complete acceptance condition.
LET’S DEFINE THE SCOPE
Turn your IdeaSoft export into a migration plan
Share a catalogue sample, special product fields and current connections. We can review information gaps and the functionality that must be rebuilt.
Review the source sample