Foundation · 5 min
What you need to know
Why did traffic drop after ecommerce migration?
Traffic often drops when redirects are missing, pages become blocked or noindexed, internal links change or measurement is incomplete. Compare landing-page traffic, crawl results and analytics tagging with the pre-launch baseline.
Why did rankings drop after migration?
Rankings may fall when redirects, canonicals, indexability, content or internal links no longer preserve the old page signals. Check affected queries and URLs individually instead of treating every change as one problem.
Why did conversion fall after migration?
Conversion can fall because checkout, performance, availability, pricing, traffic mix or tracking changed. Confirm measurement first, then compare funnel steps and affected customer segments with the baseline.
Why are old URLs returning 404 errors?
Old URLs return 404 errors when they were omitted from the migration map, redirect rules were not deployed, or the request pattern did not match. Add a relevant destination where one exists and retest the response.
Why are products missing after migration?
Products may be missing because they failed validation, lost publication status, were excluded by scope, or no longer meet category or inventory rules. Trace the source identifier through the import log to the live catalog.
Why are product variants incorrect?
Variants become incorrect when option values, parent-child relationships, SKUs or prices are mapped inconsistently. Compare the source combination with the destination and correct the transformation before rerunning it.
Why are product images missing?
Images go missing when asset URLs are inaccessible, files fail transfer, media relationships break or rendering uses an invalid destination. Check the asset manifest, file response, and product association.
Why can’t existing customers log in?
Existing customers may be unable to log in when password verifiers are incompatible, accounts were duplicated, identity settings changed or activation messages failed. Test one identity securely and use the approved reset path.
Why is customer order history missing?
Order history may be absent because orders were excluded, customer identities do not match, or the account view cannot read migrated records. Reconcile customer and order identifiers before changing the display layer.
Why are inventory quantities incorrect?
Inventory becomes incorrect when locations, reservations, deltas or SKU mappings are incomplete. Stop unsafe selling where necessary and reconcile available, reserved and physical quantities for each affected SKU-location pair.
Why are taxes different after migration?
Taxes differ when product categories, exemptions, locations, prices, or provider rules were configured differently. Compare the same controlled cart on both systems and have the tax owner approve the intended result.
Why are shipping rates different after migration?
Shipping rates differ when package data, zones, services, origins, or carrier credentials changed. Reprice controlled carts and trace each difference to a rule or provider response.
Why are payments failing on the new store?
Payments may fail because credentials, callback URLs, method settings, fraud controls, or order-state handling are wrong. Use gateway evidence and a controlled test to locate the failing step without repeatedly charging a customer.
Why are analytics reporting different numbers?
Analytics numbers differ when event definitions, consent, identifiers, time zones, attribution or deduplication changed. Reconcile known orders from browser events to report before comparing trends.
Why are integrations failing after migration?
Integrations fail when credentials, endpoints, permissions, schemas, identifiers or event delivery changed. Trace one failed transaction end to end, correct the contract mismatch and replay it only when safe.
Why is the new ecommerce store slower?
The new store may be slower because templates, scripts, media, cache behavior, third-party services, or infrastructure differ. Compare the same journeys under controlled conditions and optimize the measured bottleneck.
How do I perform a post-migration audit?
Audit scope and requirements, record counts and exceptions, customer journeys, financial reconciliation, integrations, SEO, analytics, security, performance and operations. Record evidence, owners, and deadlines for every unresolved item.
A quick store check
Reproduce one real issue, preserve evidence, identify its root cause, correct it safely, and reconcile every affected record or URL.
Foundation · 2 min
Frequently asked questions
Should teams manually correct symptoms first?
Only to limit immediate harm. Preserve evidence and fix the root cause, so the problem does not return or become harder to reconcile.
What belongs in a post-migration audit?
Requirements, data, customer journeys, finance, integrations, SEO, analytics, security, performance, operations and unresolved exceptions.