Online Store Migration Checklist: How to Avoid Losing Sales or SEO Rankings

Migrating your store is scarier than opening one from scratch. And with good reason.

Every URL that changes is a customer who might disappear. Every badly migrated product is a lost sale. Every forgotten redirect is organic traffic you built over months — or years — evaporating in a single afternoon.

We’ve seen it up close. Across more than 100 online stores we’ve built or migrated at Gulupa Digital, the pattern is the same: well-executed migrations lose less than 5% of traffic and recover it within weeks. Badly executed ones can lose between 30% and 70% of organic traffic. And getting it back costs more than doing it right from day one.

This checklist exists because almost nobody has written a complete one in Spanish. If you’re thinking of moving your store from Shopify, Wix, Jumpseller or any other platform to WooCommerce — or even between versions of the same platform — this is what you need to know before you touch anything.

Phase 1 — Before you move a single product (pre-migration)

80% of migration disasters happen because someone hit “migrate” without doing these nine things first. Don’t skip any of them.

1. Make a full backup of your current store

It isn’t “just in case”. It’s your life insurance. The backup must include:

• The complete database: products, variations, categories, customers, orders, coupons
• Theme files and customizations: CSS, PHP, custom functions, translations
• Images and assets: the /uploads folder or equivalent, with the folder structure intact
• Settings: payment gateways, shipping methods, taxes, currency settings

Store the backup in at least two places: your computer and the cloud. And check that you can restore it. A backup you haven’t tested isn’t a backup.

2. Audit all your current URLs

This is the step that saves the most traffic — and the one most people skip.

You need a complete list of every URL in your current store. Not just products and categories. Also:

• Corporate pages (about us, contact, policies)
• Indexed image URLs
• Blog posts and guides
• Tag and filter pages that get traffic
• Product variation URLs, if they’re indexed

Tools: generate an XML sitemap from your current platform, use Screaming Frog (the free version covers up to 500 URLs) or export the data from Google Search Console. Cross-check all three sources — there are always URLs one source reports and another doesn’t.

3. Review Search Console like a forensic analyst

Google Search Console tells you exactly which URLs generate traffic, impressions and clicks. Before migrating:

• Export the performance report with every query and page from the last 6–12 months
• Identify your top 20 pages by clicks — those are the ones you can’t break under any circumstances
• Review the indexing report: URLs currently returning 404 errors, existing redirects, excluded pages

The spreadsheet you export is your treasure map. Each row represents traffic you already have. The migration must guarantee that every one of those URLs has a working destination in the new store.

4. Prepare your staging environment (and keep it secret)

Never migrate “live” on your main domain. Set up a staging environment:

• Use a subdomain such as staging.yourstore.com or a temporary domain
• Block indexing with noindex, nofollow across the whole site
• Password-protect it with .htaccess so only your team can access it
• Set up HTTPS from day one (Let’s Encrypt is free and saves headaches later)

Staging is where you’ll break things without consequences. If staging isn’t ready, the migration doesn’t start.

5. Map the data structure: old → new

Every field in your current store must have an equivalent on your new platform. Don’t assume it “migrates itself”. Build a mapping table:

If your store has more than 100 products, this mapping gets heavy. But every field you leave unmapped is an inconsistency your customers — and Google — will notice.

6. Define your redirect plan BEFORE you move anything

This is the most important item in all of phase 1.

Every URL in your current store that changes in the new one needs a 301 redirect. It’s non-negotiable. A 301 tells Google “this has moved here permanently” and passes on most of the link’s authority.

Prepare your redirect file in the exact format:

CURRENT_URL → NEW_URL
/tienda/producto-ejemplo-1 → /producto/producto-ejemplo-1/
/tienda/categoria-ejemplo → /categoria-producto/categoria-ejemplo/
/paginas/quienes-somos → /quienes-somos/

Tools that save you hours: if you’re migrating to WordPress + WooCommerce, plugins such as Redirection or Rank Math handle 301 redirects natively. If your hosting uses Apache, .htaccess. If you use Nginx, rules in the server block.

Create this file now, even if you haven’t migrated anything yet. When you finish the migration, it will save your neck.

7. Audit your current on-page SEO and don’t make it worse

Your current store already has SEO — good, average or bad, but it has it. Before migrating, document:

• The title tags of your 20 main pages (the ones you exported from Search Console)
• Current meta descriptions
• The H1 and H2 headings of each page
• The alt text of key images
• Structured data (product schema, reviews, breadcrumbs)

The new store must inherit ALL of this. If your current store is missing meta descriptions on half its products, now is the time to write them — in the new one. Don’t migrate a mess.

8. Set up your tracking tools before the switch

Google Analytics, Google Search Console, the Facebook Pixel, the TikTok Pixel, the Google Ads tag — everything must be installed and verified in staging before migrating.

Install Google Tag Manager in the new store and centralize all the pixels there. If you don’t do it now, you’ll have a data gap between the migration and the day you remember to install tracking. And that gap means you won’t be able to measure the real impact of the migration.

9. Build a communication plan for your customers

Your repeat customers suffer most from a badly communicated migration. If they land on a different site, with a different interface and without their login details, trust breaks.

Define:

• An email to customers with accounts: “Migration scheduled for [date]. Your account and orders will be available in the new store. Here’s what changes and what doesn’t.”
• A notice in the current store: a banner or pop-up announcing the migration with the date, a link to an FAQ and a “what to expect”
• A social media post: one week before and on the day of the migration
• A post-migration email: “Your account is ready in the new store. Here’s how to access it.”

If you sell through WhatsApp or have salespeople with their own client portfolios, they also need to know what’s going to happen and when.

Phase 2 — The migration (the day everything moves)

The day has come. You have a backup, a tested staging environment, a redirect file and a communication plan. Now comes execution.

10. Migrate products with variations, prices and stock intact

Not all migration tools are equal. Tools such as Cart2Cart or LitExtension automate the migration, but none of them is perfect.

What you should check after migrating, product by product or by sampling if you have hundreds:

• Is the SKU exactly the same?
• Were the variations (size, color, model) created as attributes rather than as separate products?
• Do prices include or exclude taxes according to your tax configuration?
• Is stock synchronized? A product showing 0 in stock that actually has 15 units is a lost sale.
• Were variation images assigned correctly?

If you have more than 500 products, check a random 10% sample. If the sample has errors, you’ll need to review everything.

11. Migrate categories with their hierarchy, slugs and descriptions

Categories in WooCommerce have fields that other platforms don’t handle the same way:

• Slug: it must match the previous slug. If your category was /tienda/ropa-hombre/, the slug in WooCommerce must be ropa-hombre, not ropa-para-hombre or ropa_hombre.
• Category image: WooCommerce supports category images. If your previous store had them, bring them over.
• Description: many stores have SEO text in each category description. That doesn’t migrate automatically. Copy it manually or make sure your tool does.

12. Migrate customers and their order history without breaking passwords

This is one of the most delicate points.

Passwords are stored with different hashes on each platform. If you migrate customers from Shopify to WooCommerce, the passwords will NOT work. You have two options:

1. Force a password reset: WooCommerce sends each customer an email with a link to create a new one. It’s the safest option, but also the one that creates the most friction.
2. Migrate with a plugin that preserves the hash: some premium plugins let you keep the encryption method so customers can log in without resetting their password.

Either way, communicate it clearly in your pre-migration email.

Historical orders must be migrated with their original numbering. If your order #1045 in Shopify becomes #1 in WooCommerce, your accounting and customer service turn into chaos.

13. Set up the payment gateways you need for Colombia and LATAM

If your store sells in Colombia, you need gateways that work here. WooCommerce has native or plugin-based integration with:

• PayU Latam
• Mercado Pago
• Wompi (Bancolombia)
• ePayco
• PlacetoPay
• Addi (buy now, pay later)

Set up each gateway in staging, make a test purchase for a minimal amount and check that the money reaches your account. It seems obvious, but we’ve seen stores go three days unable to take payments because the gateway wasn’t configured properly.

14. Review shipping methods, taxes and sales zones

In WooCommerce, taxes are configured by tax class and by zone. If you sell with 19% VAT in Colombia but also sell to other countries with different rates, you have to create the corresponding classes.

The same goes for shipping methods: if you used an integration with Coordinadora, Servientrega, Envía or any Colombian logistics operator, install and configure the corresponding plugin. Check that rates are calculated correctly by weight, destination and product type.

15. Install SSL and force HTTPS across the whole site

No HTTPS, no sales. Period. Browsers flag HTTP sites as “not secure” and customers abandon checkout.

If you use decent hosting, Let’s Encrypt gives you free SSL. Activate it and then force the HTTP → HTTPS redirect on every page. In WordPress, plugins such as Really Simple SSL do this in one click, but check manually that no mixed content remains (images or scripts loading over HTTP).

16. Test the checkout: make a real purchase, not a simulation

Go in as a real customer. Choose a product. Add it to the cart. Get all the way to the payment gateway. Actually pay a minimal amount. Receive the confirmation. Check that the order appears in the WooCommerce admin panel.

Repeat with:

• Cash on delivery
• Two different products in the same cart
• A discount code
• A guest purchase (without creating an account)
• A purchase that creates a new account

Every purchase flow that fails in staging will fail in production — but with real customers on the other side.

Phase 3 — After going live (post-migration)

Your new store is live. Now the most ignored phase of all begins — and it’s the one that decides whether the migration was a success or a silent failure.

17. Activate the 301 redirects immediately

The redirect file you prepared in item 6 must be activated the moment the new store goes live. Not “tomorrow”. Not “in a bit”. NOW.

If you used WordPress, plugins such as Redirection let you import a CSV with all the redirects at once. Activate them and randomly check at least 20 old URLs to confirm they redirect correctly to their new location — and that they return a 301 code (not 302, not 307, not 404).

18. Generate the new XML sitemap and submit it to Google Search Console

WooCommerce with Yoast SEO or Rank Math generates sitemaps automatically, including products, categories and pages. Take that sitemap and:

• Submit it to Google Search Console manually
• Request URL inspection for your 10 main pages
• Keep the previous store’s sitemap active for the first 7–10 days so Google detects the redirects

Don’t delete the old property in Search Console. As long as redirects exist and Google is crawling the old URLs, that property helps you monitor the transition.

19. Watch 404 errors like a hawk

For the first two weeks, check the Search Console indexing report and your server’s 404 error logs daily. Every 404 is a URL that Google or a customer tried to visit and couldn’t find.

Create redirects for every 404 that appears. If you have hundreds, prioritize: first those that had traffic in Search Console, then active products, then corporate pages.

Google Search Console shows 404 errors grouped by URL. Spend 15 minutes a day on it for the first two weeks. After that, once a week for a month.

20. Check tracking: GA4, conversions, pixels

Open Google Analytics 4 in real time. Browse your store. Are page views being recorded? Are the “add_to_cart”, “begin_checkout” and “purchase” events firing?

If you use Google Ads or Meta Ads, check that conversion events are being recorded correctly on each platform. A migration can break event triggers if the checkout’s CSS selectors changed. Don’t assume everything still works.

21. Measure the new store’s Core Web Vitals

One of the big advantages of migrating to WooCommerce (if it’s well configured) is speed. But “well configured” is the key part.

Run PageSpeed Insights or Lighthouse on your homepage, a category page and a product page. Compare with your previous store’s metrics. If LCP (Largest Contentful Paint) got worse, review:

• Image size and format (WebP instead of PNG/JPG)
• Caching (WP Rocket, LiteSpeed Cache or similar)
• Hosting — if you use $5-a-month shared hosting, speed will never be good
• A CDN — Cloudflare is free and speeds up the delivery of static assets

22. Make real test purchases in production (yes, again)

You did it in staging. Now do it in production. Buy a real product with real money. Pay. Receive the confirmation. Check the WooCommerce admin panel. Return the product to test the refund flow.

The checkout is the one page in your store where you can’t afford a single mistake.

23. Tell your customers the new store is ready

Send the post-migration email you planned. Post on social media. Update your store banner from “we’ll be migrating soon” to “our new store is live — and here’s what’s new”.

Include an incentive: “10% off your first purchase in the new store with the code WELCOME”. You don’t just reduce the friction of the change; you turn the migration into a re-engagement opportunity.

Why WooCommerce is the destination we recommend

It isn’t favoritism. It’s business math. After migrating more than 100 stores, the numbers are clear:

No platform fees per sale. Shopify adds a transaction fee of up to about 2%, depending on the plan, when you don’t use its own payment processor (on top of the gateway’s commission). On a store billing COP 50 million a month, a 2% fee is COP 1,000,000 that goes on platform fees alone. WooCommerce doesn’t charge a peso for selling.

Full control of SEO. Shopify gives you the basics. WooCommerce with WordPress gives you absolute control over every title, every meta description, every URL, every schema, every redirect, the robots.txt file and every canonical tag. Stores that migrate from Shopify to WooCommerce often see organic traffic improvements of between 30% and 120% after 6 months, when the migration is done thoughtfully.

Colombian gateways without detours. PayU, Wompi, ePayco, Mercado Pago, Addi. They all integrate with WooCommerce. On Shopify you need third-party apps — if they even exist for Colombia.

Ownership of the code and data. Your WooCommerce store is yours. You choose the hosting. The database is yours. The files are yours. If WooCommerce disappeared tomorrow, your store would keep working. With Shopify or Wix, if the platform goes, so does your store.

Real scalability. You start with $30-a-month hosting. When your store grows to 10,000 visits a day, you move to a VPS or dedicated server without changing platform. No artificial limits on products, variations or bandwidth. And when you need support and maintenance so growth doesn’t break your operation, you have someone to back you up.

Real mistakes we’ve seen (and that you won’t make)

These aren’t theory. They’re migrations that came to Gulupa Digital after someone else got them wrong.

Mistake 1: “We migrated without redirects. We lost 65% of our traffic.” A fashion store in Medellín with 3 years of SEO built up. They migrated from Jumpseller to WooCommerce without redirects. Google took 8 months to index the new URLs. Organic sales fell by half during that period.

Mistake 2: “The products migrated without SKUs. The warehouse didn’t know what to ship.” A spare-parts store with 2,000 products. The automated migration tool assigned new SKUs. For two weeks, every order required someone in the warehouse to find the product “by eye” using its name and photo.

Mistake 3: “The checkout worked in staging but not in production.” The classic. In staging they paid with the Mercado Pago sandbox. In production, the real credentials hadn’t been configured. Three days unable to take payments.

Mistake 4: “Nobody told the customers.” A B2B store that migrated silently on a Friday. On Monday, corporate customers were calling to ask why they couldn’t log in. The passwords hadn’t migrated and nobody had sent them the reset email.

Mistake 5: “They migrated the products. Not the images.” Yes, it happens. The migration tool moved the product records but not the physical image files. The store was left with 800 products without photos. Rebuilding that took weeks.

Every one of these mistakes is avoided with the items in this checklist. It isn’t theory. It’s surgery.

Frequently asked questions

How long does it take to migrate an online store without losing rankings?

It depends on the size. A store with 100–300 products and an experienced agency takes between 2 and 4 weeks: 1–2 weeks of preparation (backup, URL audit, staging, mapping, redirects), 2–3 days of actual migration and 2 weeks of post-migration monitoring. Stores with more than 1,000 products or custom integrations (ERP, POS, logistics) can take 4 to 8 weeks. What you can’t do is migrate in 48 hours without preparation — that guarantees lost traffic and sales.

Will I lose my organic traffic if I migrate from Shopify to WooCommerce?

No, if the 301 redirects are done properly, titles and meta descriptions are preserved, the new sitemap is submitted to Search Console and you monitor 404 errors for at least two weeks. Traffic loss in well-executed migrations is under 5% and recovers within 4–8 weeks. In many cases, traffic even improves because WooCommerce allows more granular SEO than Shopify.

What happens to my customers and their passwords when I migrate?

Passwords don’t transfer automatically because each platform uses different encryption methods. Standard practice is to force a password reset: WooCommerce sends each customer an email with a link to create a new one. To reduce friction, announce it before the migration and offer an incentive (a discount, free shipping) for creating the new password and completing the first purchase.

Can I migrate a store myself, or do I need an agency?

If you have fewer than 50 products, intermediate technical knowledge and time to follow this checklist to the letter, you can do it. If you have more than 100 products, ERP or logistics integrations, significant organic traffic (>5,000 visits/month) or your store is your main source of income, paying for a professional migration costs less than losing sales to a botched one. A professional migration in Colombia costs between COP 2,500,000 and COP 8,000,000, depending on volume and complexity.

Which platform is best for migrating a store in Colombia?

WooCommerce on WordPress offers the best balance of control, cost and scalability for the Colombian market. The reasons: no per-sale platform fees, direct integration with Colombian gateways (PayU, Wompi, ePayco, Mercado Pago, Addi), full control of SEO, compatibility with national logistics operators and complete ownership of your data and code. Shopify is a valid alternative if you prioritize simplicity over control and are willing to pay monthly fees plus transaction fees.

If your store already brings in revenue and migrating it is keeping you up at night, you don’t have to do it alone.

At Gulupa Digital we’ve built and migrated more than 100 online stores. We know exactly what can go wrong — and how to prevent it before it happens. From fashion stores in Medellín to B2B ecommerce with complex logistics integration.

We don’t do magic migrations. We do surgical migrations: with a checklist, staging, redirects, post-migration monitoring and zero surprises for your customers.

Does your store need a migration that won’t cost you sales or rankings? Book a free call and we’ll show you exactly how this checklist would apply to your case.