Ecommerce redesign and migration in Pune
Moving between Shopify, WooCommerce and Magento, or rebuilding a store that stopped converting. Products, customers, orders and every URL carried across deliberately.
A redesign is the easiest way to lose search traffic you spent years earning. Most of the work on this page exists to stop that happening.
Already lost traffic after a redesign? That is a specific job with a specific method, and the sooner it is caught the more recoverable it is.
- Products, variants and imagesMapped field by field, with a sample checked by hand
- Customers and order historyAccounts preserved, with a password reset flow that makes sense
- Every old URL, redirectedThe single most important deliverable in any migration
- Titles, descriptions and structured dataCarried over rather than regenerated from scratch
- Analytics continuitySo you can prove what the migration did, in either direction
Does your store need a rebuild, or three fixes?
A rebuild is the expensive answer and it is not always the right one. This is roughly how we decide, and we will give you the same reasoning whether or not it wins us the bigger project.
Fix what you have
If the foundations are sound, targeted work beats a rebuild by a wide margin. Signs you are in this category:
- The platform still suits your business model
- The problem is speed, or checkout, or one bad template
- Your product data is structured sensibly
- Search traffic is healthy and you do not want to risk it
Keeping the URLs you already rank for is a real asset. Do not throw it away for a new look.
Rebuild or migrate
Sometimes the foundation is the problem, and every fix is a workaround on top of a workaround. Signs you are here:
- The platform cannot do what the business now needs
- Nobody will touch the code, including its author
- The platform is unsupported or the version is stranded
- Fix estimates keep landing near the rebuild number
Even then, the goal is a migration your customers barely notice and Google barely reacts to.
Over 500 products, most of them with colour and quantity variations, and our old site simply could not handle it. They understood how we sort by age group and theme before writing a single line of code.
Six ways a redesign quietly destroys search traffic
Every one of these is common, avoidable, and usually discovered six weeks too late. Pick one to see what goes wrong and what we do instead.
The redirect map was skipped
Old URLs return a 404 and every link, ranking and bookmark pointing at them is thrown away. This is the single biggest cause of traffic loss after a launch, and it is entirely preventable.
A sharp drop within two weeks, spread across the whole site, with 404s climbing in Search Console.
- Every old URL mapped to one specific new URL before launch
- Redirects deployed in the same release as the new site
- A fresh crawl of the old URL list on launch day to verify each one
- Discontinued products sent to their category, never to the homepage
Everything points at the homepage
A lazy shortcut that looks like a redirect map but is not. Search engines treat a mass redirect to an irrelevant page as a soft 404, so the ranking is lost anyway and nobody notices for weeks.
Redirects appear to be in place, yet rankings still fall and the pages drop out of the index.
- One to one mapping wherever a genuine equivalent exists
- Product to closest product, or to the parent category
- Only genuinely orphaned pages go anywhere generic
- Redirect chains flattened so nothing hops twice
The new design has less content
A cleaner look often means shorter category descriptions, removed FAQs and product copy trimmed to look tidy. The page that ranked did so partly because of that text.
A slow decline over a month or two on specific category and product pages rather than sitewide.
- Record what content exists on the pages that earn traffic
- Carry that content into the new templates deliberately
- Redesign the presentation rather than deleting the substance
- Compare word counts before and after on the top pages
Staging leaked, or launch stayed blocked
Two versions of the same failure. Either the staging site gets indexed and competes with the live one, or the noindex tag used to protect staging survives into production and quietly deindexes the store.
Either duplicate results in Google, or the entire site disappearing from search within days of launch.
- Staging protected by authentication, not just a robots rule
- Robots and noindex state checked as a launch gate
- A crawl immediately after launch to confirm pages are indexable
- Index coverage monitored daily for the first fortnight
Titles and descriptions regenerated
The new platform generates titles from a template, overwriting years of tuned metadata. Structured data often disappears at the same time, taking rich results with it.
Rankings hold roughly steady but click-through rate falls, so traffic drops without positions moving.
- Export all existing titles, descriptions and structured data first
- Import them rather than accepting platform defaults
- Validate product and breadcrumb markup after launch
- Spot check the highest traffic pages in a live search result
The new site is heavier
A visually richer design with larger images, more scripts and an untuned host can be slower than the site it replaced, which hurts both rankings and conversion on mobile.
Core Web Vitals worsen in Search Console and mobile conversion falls even though the site looks better.
- A performance budget agreed before design begins
- Images compressed and served in modern formats
- Third party scripts audited and justified individually
- Field data compared against the pre-launch baseline
Seven stages, and the order is not negotiable
Most migration disasters come from doing stage four before stage one. The baseline in particular cannot be recreated afterwards.
-
Baseline everything
Current rankings, traffic, revenue by page and a full crawl, recorded before anything changes. Without this you cannot prove what the migration did.
-
Audit and decide
Code, plugins, hosting, data quality and the commercial reason for moving. This is where we tell you if a rebuild is the wrong call.
-
Map the URLs
Every old address to exactly one new address, including discontinued products, old category pages and any blog you forgot about.
-
Build on staging
Design and development on a blocked staging site, with the new structure informed by which pages currently earn your traffic.
-
Migrate the data
Products, variants, images, customers and orders, with a sample verified by hand rather than assumed correct because the importer said so.
-
Launch with the redirects live
Redirects go up in the same deployment as the new site, never a day later. Then a fresh crawl to catch anything the map missed.
- 07 AFTER LAUNCH
Watch for six weeks
Index coverage, crawl errors, rankings and revenue measured against the baseline from stage one. Most migration problems are visible in week two and fixable in week three, which is the whole reason we keep watching instead of closing the project on launch day.
Already lost traffic after a redesign?
A different job with a different method, and a genuinely urgent one. Redirects put in place quickly recover far more than redirects put in place six months later.
Recovery is usually substantial and occasionally complete, but nobody can promise you get every position back. Anyone who does is guessing.
Find what was lost
Compare Search Console before and after the change, page by page. The drop is almost never uniform, and the pattern tells us the cause.
Recover the old URL list
From Search Console, analytics, old sitemaps, backups and archive services. You usually have more of it than you think.
Redirect what mattered
Priority to the pages that actually earned traffic or revenue. A redirect to a relevant page, never a blanket redirect to the homepage.
Fix what the rebuild broke
Missing titles, thin category pages, blocked robots rules, structured data that disappeared, content that quietly did not come across.
Re-submit and monitor
Clean sitemaps, index coverage watched weekly, and a realistic view of what comes back and what does not.
Migrations we do most often
Each route has its own quirks. These are the ones we have hit repeatedly, so we know where the data gets messy before we start.
Magento Shopify
The most common request we get. Usually a store on an old Magento version that nobody wants to maintain.
WooCommerce Shopify
Usually driven by maintenance fatigue. Worth checking the three-year cost before committing, because it is not always cheaper.
Shopify WooCommerce
Driven by ownership, app costs or a workflow the platform will not allow. The last reason is the strongest one.
Anything custom
When the business has outgrown every platform. The rarest route, and the one that most deserves a discovery phase first.
Same platform, rebuilt
A new theme and structure without changing platform. Lower risk, but it still needs a redirect map if URLs move.
Static or catalogue site store
An old brochure site becoming a real store. The existing pages often rank well and must be preserved, not discarded.
What you receive when a migration is done
The redirect map and the baseline comparison are the two documents that prove the job was done properly. Ask for both from anyone who migrates your store.
The complete redirect map
Every old URL and its destination, as a file you keep. If anyone questions the migration later, this is the evidence.
Before and after comparison
The baseline from stage one measured against six weeks post-launch. Honest either way, including anything that went backwards.
An archive of the old site
Database and files kept safely, so nothing is unrecoverable if you discover a page nobody remembered six months later.
Data verification notes
Which records were checked by hand, what was corrected, and anything that could not be carried across with the reason.
All accounts in your name
New platform, hosting, domain, analytics and Search Console. If the last developer held these hostage, that ends here.
Training on the new admin
Your staff have just had their daily tools changed. A walkthrough and notes make that far less painful than it usually is.
What people ask before migrating
Ask anything else on WhatsApp. If you are mid-crisis after a launch, call instead. It is time sensitive.
Will we lose our Google rankings?
A short dip in the first few weeks is normal even on a well-executed migration, because search engines need to recrawl and reprocess the whole site. What is not normal is a drop that does not recover. That comes from missing redirects, changed content or blocked pages, which is exactly what the method above is designed to prevent. We will not promise zero impact, and anyone who does has not done many migrations.
Can you migrate our order history?
Usually yes, though how completely depends on the two platforms. Orders, customers and addresses generally move. Things like store credit, loyalty points or subscription states often live inside apps rather than the platform, and those need handling separately. We check what is actually held where during the audit, so you know before the quote rather than after the launch.
How long will the store be down?
It should not be down at all. The new site is built and fully populated on staging while the old one keeps taking orders, then we switch. We schedule the switch for your quietest hours and agree a rollback plan before starting. What does need managing is the small window where an order could land on either system, which we handle with a brief pause on the old admin.
Our old developer will not give us access. Now what?
More common than you would like. Start by establishing what is registered in your business name, because the domain and the hosting account usually are even when the developer manages them. From there we can often recover control through the registrar or host directly. Where we truly cannot, we rebuild from what is publicly crawlable plus your own records. It is slower and we will be honest about that, but it is not a dead end.
Should we change our URL structure while we are at it?
Only if there is a real reason. Tidier URLs are not worth the risk on their own. A genuinely broken structure, such as category paths that no longer match how you sell, is worth fixing while everything is already moving. If we do change them, it happens once, in the same launch, with the redirects in place. Two separate URL changes across two months is twice the risk for no extra benefit.
Is a redesign a good time to start SEO?
It is the best time, because the information architecture is being decided anyway and that is the cheapest moment to get it right. Keyword research before the rebuild shapes categories, URLs and templates while changing them costs nothing. Doing it afterwards means changing URLs a second time. The SEO service page sets out what that looks like over twelve months.
Send us the URL and what is going wrong
We will look at the platform, the structure and the search data, then tell you whether this needs a rebuild or three fixes. Those are very different invoices and we will not pretend otherwise.
hello@ecommercepune.in
We will look at the site properly before replying, and tell you honestly whether this is a rebuild or a repair. If you have already lost traffic, call rather than wait, because it is time sensitive.