Migration discovery audit: know what you're moving before you move it
A migration discovery audit for Magento and Adobe Commerce stores: code, extensions, data model, integrations, SEO and risk, with a written plan. From a Magento to Shopify migration consultant in San Diego.
Most migration budgets are set before anyone has read the code. Then the project finds the undocumented ERP export, the extension that rewrites checkout, the 30,000 URLs nobody mapped, and the budget moves.
A migration discovery audit is the step that prevents that. I go through your Magento or Adobe Commerce store (code, extensions, data, integrations and search footprint) and give you a written plan: what moves cleanly, what doesn't, what it will take, and what to decide first. You can run the project with me, with your agency, or with anyone else.
I'm a Magento to Shopify migration consultant and senior Magento 2 developer in San Diego. I led Event Network's move of its museum and zoo storefronts from Magento 2 to Shopify, and have run Magento migrations for other merchants before and since.
Who it's for
- Merchants on Magento 2.4.6 or older deciding between an upgrade and a replatform before extended support ends on August 31, 2027.
- CTOs and eCommerce leads who have a migration quote and want an independent view of scope and risk.
- Agencies that have won a migration and need a senior Magento specialist to map the old system before the build starts.
What the audit covers
Code and extensions. Every custom module and third-party extension: what it does, whether the business still needs it, and how it would be replaced on the target platform (native feature, app, custom code, or drop it).
Catalog and data model. Attribute sets and EAV attributes, store-view scoped values, configurable, bundle and grouped products, and how they map to the target. On Shopify: options, variants, metafields and metaobjects, and whether any product exceeds the variant or option limits your plan supports.
Customers and orders. Customer volume, addresses, groups and consent; the password reset plan (Magento password hashes cannot be imported into Shopify); order history to import; gift cards, store credit and reward balances that need a home.
Multi-store and B2B. How your websites, stores and store views map to the target, for example Shopify Markets or separate stores, and what B2B features (company accounts, shared catalogs, custom pricing, quotes) you really use.
Integrations. ERP, POS, 3PL, marketplaces, payment gateways, tax, email and analytics: what each sends and receives, how often, and what breaks if it stops.
SEO. Indexed URLs, URL rewrites and inbound links, and the size and shape of the redirect map.
Cutover risk. What needs a freeze, what can sync as a delta at launch, and what has to be rehearsed.
What you get
- A written audit report in plain language, with the technical detail in appendices.
- A data map: Magento entities and attributes to target fields.
- An integration inventory with a plan for each one.
- A first-pass redirect inventory.
- A risk list with the decisions you need to make and when.
- A phased plan and effort estimate for the migration, or for an upgrade if that turns out to be the better answer.
Why an audit from me
I've been building Magento stores since 2012, ran a Magento agency, led 18 Magento 2 storefronts at Event Network and built the ERP and POS integrations behind them. Then I led the company's move to Shopify. I've seen the problems an audit is supposed to find from both sides: as the person who built the system and as the person who had to move it.
Questions
Do we have to hire you for the migration afterwards? No. The report is yours and written so any competent team can execute it.
Can the audit recommend staying on Magento? Yes. If an upgrade is the better investment, the report says so and plans that instead.
Do you need production access? Read access to the code repository, a recent database copy (customer data can be anonymized) and an admin account are enough. Nothing is changed.
Can you audit on behalf of our agency? Yes. I can work under your agency's name as an Adobe Commerce contractor, or alongside you with the client.
Working together
- Email the brief: your version, catalog size and integrations.
- A 30-minute call to go through it together.
- A written, fixed-scope proposal.
Start with an audit
Tell me your platform and version, roughly how big the catalog is, and what the store connects to.
Available now · full-time or contract
Need a senior Magento lead? Let’s talk.