PMG Digital Made for Humans

Three Questions to Ask Before Moving to a New Ecommerce Platform

3 MINUTE READ | January 17, 2012

Three Questions to Ask Before Moving to a New Ecommerce Platform

Author's headshot

Christopher Davis

Christopher Davis has written this article. More details coming soon.

Over the past year, PMG has helped several clients migrate from one ecommerce platform to another. This happens all the time: a business starts small, and, as they grow, they find themselves outpacing their platform. It’s time to move, but moving is disruptive, work intensive, and generally a pain.

A migration comes with many challenges on the SEO front, so here’s three questions to ask of your new platform choices.

Legacy, in this case, means URIs from the old platform and site. The ideal situation is that every old URI can be mapped to its corresponding new URI through a 301 redirect.

Some questions to ask of your new platform’s handling of legacy URIs:

  • Does it have a built in way to map old URIs to new?

  • Does that functionality do pattern matching? Or will you have to write rules for each individual old URI?

  • How does the redirect functionality work? Does it slow down the site?

Demandware, for instance, includes a full featured mapping system to handle legacy URIs. Other, self-hosted platforms (ala Magento) give you full access to the server, making URI rewriting a piece of cake.

That brings up the next point:

Platforms as a service (PaaS), like MagentoGo or Demandware, give you less access to the server level things by default. It’s a trade off: you get the stability and security of a fully managed platform, leaving you to do the real work – selling stuff. On the other hand, this means some things (like URI rewriting) have to be done through the platform itself.

If the platform is deficient in some way, you’re stuck with it. If you lack a feature in an open source platform like Magento, you can add it – either by forking the project completely or adding a plugin. In the same way, if you choose to build your own platform, you can add whateve features you desire.

So how much access will you have to the underlying software? How will that effect your ability to be agile and move forward as time goes on?

To get the most out of that old platform you did a lot of work: new s, meta descriptions, product names & descriptions, customer reviews, customer accounts, everything!

You want to make sure your new platform has an easy way for you to migrate all that data. You’re already changing a lot of stuff, so make sure your new platform can pull in the old data easily. Sometimes this is as easy as an SQL dump, other times it means scraping the current website and feeding the data to an API on the new.

Is there way to push data into the new platform easily? How much access do you have on that front (see point 2)?

Stay in touch

Bringing news to you

Subscribe to our newsletter

By clicking and subscribing, you agree to our Terms of Service and Privacy Policy

The moral here is not to fall in love with a platform too quickly. Ask the tough questions up front and weed out the bad ones.

Related Content

thumbnail image

AlliPMG CultureCampaigns & Client WorkCompany NewsDigital MarketingData & Technology

PMG Innovation Challenge Inspires New Alli Technology Solutions

4 MINUTES READ | November 2, 2021

thumbnail image

Applying Function Options to Domain Entities in Go

11 MINUTES READ | October 21, 2019

thumbnail image

My Experience Teaching Through Jupyter Notebooks

4 MINUTES READ | September 21, 2019

thumbnail image

Working with an Automation Mindset

5 MINUTES READ | August 22, 2019

thumbnail image

3 Tips for Showing Value in the Tech You Build

5 MINUTES READ | April 24, 2019

thumbnail image

Testing React

13 MINUTES READ | March 12, 2019

thumbnail image

A Beginner’s Experience with Terraform

4 MINUTES READ | December 20, 2018