Skip to content
Besh Bilişim Technology Services
bilgi@beshbilisim.com
İsmet Kaptan, 1372 Sk. No:15, İzmir
Besh Bilişim Besh Bilişim Besh Bilişim
  • Home
  • Services
    • Website Design

      We design fast, secure, mobile-friendly and SEO-ready corporate websites so your brand looks professional on every screen.

    • Besh CMS

      Manage your pages, blog and media from a single panel with minimal coding knowledge and update your site whenever you like.

    • Mobile Applications

      We build fast, user-focused mobile apps for both iOS and Android from a single React Native codebase. Get a quote for your mobile project.

    • Automation Software

      We build software that automates processes such as invoicing, delivery notes and stock tracking, and saves you time.

    • Accounting Software

      Track and manage invoices, accounts, stock, cash and bank transactions easily from a single program. Explore Besh Bilişim accounting software.

    • E-Commerce

      Sell your products online and track orders in one place; we build tailor-made, SEO-friendly e-commerce platforms.

    • SEO Services

      We help your website become more visible on Google and win more visitors and potential customers. Get in touch for our SEO services.

    • Web Software

      We build fast, scalable corporate web applications and portals with Next.js, React, TypeScript and .NET. Get a quote for your project.

    • Support and Maintenance

      Installation, training, maintenance and 24/7 technical support keep your systems running without interruption.

    • Custom Software Development

      Where off-the-shelf programs fall short, we build custom software designed around your business. Tell us what you need and get a quote.

  • Designs
  • Blog
  • About
  • Contact
EN
EN
Contact Us
November 11, 2026 Besh Bilişim Web Development

10 Questions to Ask Before Changing Your E-Commerce Platform

Short answer: 10 questions, and the first two are about SEO

Before changing your e-commerce platform, answer ten questions: why are you changing, which pages bring traffic, how will URLs be redirected, which data will move, what happens to customer accounts, will integrations be rewritten, do the new platform's limits bind you, what is the total cost, when will the switch happen and is there a rollback plan. Most of these are not technical; they are about lost orders and lost search traffic.

Search traffic is the most serious risk of a platform change. Google's site move documentation recommends, for moves where URLs change, server-side (301 or 308) redirects from old URLs to new ones, avoiding chained redirects, and keeping redirects in place generally for at least a year; the same document says permanent redirects such as 301 do not cause a loss of PageRank. So even when URLs change, traffic loss is not inevitable, but the redirect map has to be complete.

# Question Written answer
1 Why are we changing, and what will we measure? Goal and metric
2 Which pages bring traffic and revenue? List of top-traffic pages
3 Will URLs change? Old URL → new URL map
4 Which data will move? List of product, customer, order and content data
5 What happens to customer accounts and passwords? Migration and communication plan
6 Which integrations will be rewritten? List of ERP, accounting, courier and payment links
7 Do the new platform's limits bind us? Feature and plan check
8 What is the 5-year total cost? Cost table
9 When will the switch happen? Date and calendar constraint
10 Is there a rollback and monitoring plan? Check and rollback steps

1. Why are we changing, and what will we measure?

What problem will the platform change solve?

"The old system is slow" or "the new platform is modern" is not a goal. Write the problem you are solving in measurable terms: page speed, an action the admin team cannot perform, commission or license cost, an integration limit. Without a written goal you cannot measure success after the switch. For the question of a ready-made package versus custom software, see our off-the-shelf vs custom software decision matrix.

2. Which pages bring traffic and revenue?

Before the switch, list the pages that get the most clicks in Search Console and the pages that bring the most revenue in your analytics tool. Google's site move documentation recommends monitoring the traffic of both the old and new URLs through Search Console and analytics after the move; without a baseline you cannot measure a drop. For medium-sized sites, according to the documentation, it can take a few weeks or more for Google to start showing the new URLs, and rankings may fluctuate in the meantime.

3. Will URLs change?

How do you prepare a redirect map?

Most platforms have their own URL pattern. Shopify's Magento migration guide says Shopify uses a flat pattern, /products/<name> for products and /collections/<name> for collections, and that every indexed URL on the old site must be redirected with a 301 to its counterpart there. Listing every old URL and matching each to a new one is the first step we recommend. These steps from the same guide hold regardless of platform: validate the mapping (the guide says a redirect to a page that does not exist is worse than no redirect), upload the redirects in bulk, and test at least 20-30 of them by hand, starting with the highest-traffic pages.

Even when the URL pattern is not in your hands, keeping the last part of the address (the product name at the end of the old URL) the same makes mapping easier; this is a suggestion and depends on the platform. Do not turn a redirect into a chain (A → B → C): the old URL should go straight to the final URL.

4. Which data will move?

Shopify's migration page lists the kinds of data that can be moved: products, customers, historical orders, gift cards and store credits, blogs and pages, with CSV, migration app or API options for each. The same page notes that a migration is a good moment to purge old, low-performing content. Our suggestion: write down each data type you will move and the method, rather than "move everything", and ask how much of the order history you really need in the new system. The Shopify examples in this guide are documented examples only; other platforms' constraints may differ.

5. What happens to customer accounts and passwords?

Shopify's customer list page says passwords are encrypted outside Shopify and so cannot be migrated from another store with a CSV; after the customers are imported they must be invited to create new passwords. On other platforms, whether password hashes can be transferred varies by product; ask in the quote. Moving customer data to a new system and perhaps a new service provider is also processing of personal data: KVKK Article 12 requires the data controller to take the necessary technical and administrative measures to prevent unlawful processing of and access to personal data, and makes the controller jointly responsible with the other person if the data is processed on its behalf. This article is not legal advice; show the migration contract to your legal counsel.

6. Which integrations will be rewritten?

Each of the ERP, accounting, e-invoice, courier, payment and marketplace connections will either be rewritten when the platform changes or be replaced by the new platform's ready-made connection. List them one by one and name an owner for each. For the ERP side, our connecting a dealer portal to your ERP article lists the official APIs and license questions; for how to check the stock and order flow before a campaign period, see our Black Friday infrastructure checklist.

7. Do the new platform's limits bind us?

Platform limits are among the most expensive surprises after a switch. Example: Shopify's B2B features by plan page shows that on Basic, Grow and Advanced plans at most three active catalogs can be assigned to B2B markets, and that assigning a catalog directly to a company or location is available only on Plus. If you have many dealer groups or price lists, that limit changes your design. Run the same check for every candidate platform: number of product variants, multilingual and multi-currency selling, B2B pricing, custom fields, admin permissions and API limits.

8. What is the 5-year total cost?

Monthly subscription, transaction commission, app or plugin fees, theme and development cost, the migration project and post-migration support are separate items. Write them all into a five-year table; for a blank table and a calculation method, you can adapt the method in our ERP pricing: 5-year total cost article to e-commerce items. Comparing only the first year's bill hides the yearly commission and subscription difference.

9. When will the switch happen?

Google writes that any significant change to a site can cause ranking fluctuations while it recrawls and reindexes. So do not place the switch right before a busy selling period (a campaign, a holiday, a season); that is our opinion, not a sourced rule. Write the switch with a calendar constraint: "complete by this date, with no further changes until the campaign period".

10. Is there a rollback and monitoring plan?

Write a checklist for before going live and monitor the first weeks afterwards: Google's documentation asks you to resolve noindex tags, robots.txt blocks and crawl errors, submit the new sitemap, and update external and profile links. Write the rollback plan too: if a critical problem appears on the new platform, how and how quickly do you return to the old site, and what happens to the redirects?

SEO loss checklist

Stage Check Source
Before Complete list of old URLs (crawl + Search Console) Shopify guide, Google
Before List of top-traffic pages and baseline values Google (monitoring)
Before Old URL → new URL map, with no chains Google
Before Internal links updated to the new URLs Google
Before Titles and descriptions carried over to the new pages Our suggestion
During Server-side 301/308 redirects Google
During Remove noindex and robots.txt blocks (they may be left over from a test site) Google
After Submit the new sitemap Google
After Test at least 20-30 redirects by hand Shopify guide
After Monitor both URL sets in Search Console and analytics Google
After Keep redirects for at least a year Google

If your change covers only the platform and paths, Google's "change of address" tool is not needed: it is used only when moving from one domain or subdomain to another, and not for HTTP to HTTPS, www to non-www, or path changes within the same domain.

If you are also considering custom development as a platform option, see our custom software development page and our e-commerce service page.

Frequently asked questions

Will search traffic drop when we change platforms?

It does not have to. Google's documentation says permanent redirects do not cause a loss of PageRank; but a drop can happen if the redirect map is incomplete or a noindex left over from a test site is live. Even when done right, rankings may fluctuate for a while during recrawling.

How long should redirects be kept?

According to Google, as long as possible, generally at least a year; that period lets Google recrawl and reassign links on other sites that point to your old URLs.

Are customer passwords migrated to the new platform?

It depends on the platform. According to Shopify's documentation, passwords cannot be migrated with a CSV and customers must be invited to create new ones. For another platform, ask the vendor.

When is the best time to change platforms?

There is no sourced rule, but given the ranking fluctuation after the switch and the heavy error load in the first weeks, it makes sense not to place it right before a busy selling period (our suggestion). Plan the switch for after a campaign period and leave at least a few weeks of monitoring.

If you would like to go through your platform decision together, get in touch.

Sources: Site Moves and Migrations (Google Search Central, 20 August 2026), Redirects and Google Search (Google Search Central, 14 April 2026), Magento to Shopify Migration: The Complete Guide (Shopify), Migrate to Shopify (Shopify Help Center), Importing and exporting customer lists (Shopify Help Center), Shopify B2B features by plan (Shopify Help Center), Law No. 6698 on the Protection of Personal Data, Article 12 (Ministry of Justice)

Cover photo: Rifki Kurniawan / Unsplash

Platform Migration301 RedirectsSEO MigrationE-Commerce InfrastructureChecklistE-CommerceData Migration
All posts
Latest posts
  • Is the 11.11 Discount Real? Understanding the "Raise First, Discount Later" Strategy
    November 11, 2026
  • B2B Site for Wholesalers: Dealer Pricing, Credit Limits and Promotion Rules
    November 11, 2026
  • Connecting a Dealer Portal to Your ERP: Logo, Netsis, Mikro and Canias Methods
    November 11, 2026
  • ERP Pricing: How to Calculate the 5-Year Total Cost
    November 11, 2026
  • Claude Fable 5.2 Is Out: What Changed From Fable 5.1
    November 10, 2026
Categories
  • Software Development 8
  • Web Development 5
  • AI and Security 3
  • SEO and Digital Marketing 2
  • E-Commerce 1
Tags
ERPSMEsE-CommerceSoftware SelectionAIB2BDealer PortalDeveloper ToolsTotal Cost of OwnershipAI AgentsAstroChecklistContractCustom SoftwareData MigrationDigital MarketingIntegrationIzmirLLMSecurity
Besh Bilişim
  • Fb.
  • Ig.
  • In.

Besh Bilişim - Izmir Office İsmet Kaptan, 1372 Sk. No:15, İzmir

Email

bilgi@beshbilisim.com

Phone

+90 553 443 30 00
Newsletter

© 2026 Created by Besh Bilişim Teknolojileri

BESH

We use cookies to offer you a better experience and to analyze site traffic. Analytics cookies only work with your consent. Cookie and privacy information