Most Popular Reads
- Ecommerce Conversion Rate Optimization: Why This One Metric Determines Your Store’s Success
- The Complete Guide to Advertising on Facebook: Strategies That Convert
- 78 Best Ecommerce Website Design Examples & Award Winners
- How To Write Product Descriptions To Grow Sales [Samples Below]
- Ecommerce Return Policy: How to Write a Returns and Refunds Policy to 3X Sales [Examples Below]
- Why Now is the Time to Replatform your Ecommerce Website
- Best Ecommerce Platform Options
- Your Ecommerce Replatform Strategy
- What Not to Do in the Replatform Process
- A Handy Ecommerce Replatforming Checklist
- How to Put Platforms to the Test
- Don’t Forget About Data Migration Services
- Top 5 Data Migration Myths Debunked
Whether you’re a developer, marketer, entrepreneur or Fortune 500 CEO, there’s an inkling in the back of your mind that perhaps, in the near future, your job or company may be obsolete.
It’s not an unfounded fear. The rules to success for nearly all industries in today’s economy are fleeting, at best. Everything keeps changing, and the best of the best have to be able to pivot –– quickly and competently –– in order to keep up.
Of course, to keep up with the newest skill sets and execute on the most modern of campaigns, you often need money and headcount.
This need, then, positions the biggest brands of the world well, enabling them to form monopolies, of sorts –– in theory at least. Yet, that isn’t what we’re seeing take shape.
Large organization move too slowly to pivot quick enough to execute well on trends. Instead, those companies end up buying the brands that do (re: Walmart acquiring Jet.com and Unilever buying Dollar Shave Club).
What enables those up-and-comers to take on their legacy competitors (i.e. Amazon and Gillette)? Agile marketing that gets these brands to the forefront of customer conversion points in a more compelling way than traditional companies.
Successful Brands Can Focus on Marketing, Thanks to Their Technology
What allows these companies to focus on marketing is their choice of technology stack from the onset. Or, if not from the onset, these companies are quick to replatform to a better solution, so that website maintenance and bug patches are not taking priority over marketing activities. The latter leads to sales, growth and revenue. The former doesn’t have to be business as usual.
That is why you must pick the right ecommerce platform. You need to focus on marketing and growth.
After all, marketing is both expensive, competitive, and requires a lot of time. It is pay-to-play in so many channels: Adwords, Facebook, TV, radio. In the ones where it isn’t –– say, SEO –– you’re competing against a gamut of competitors and bigger brands, often with a much bigger head start.
And, each of these channels are getting more and more saturated everyday.
So why are you spending your time and money a “good enough” ecommerce solution?
Successful Ecommerce Replatforming Examples
- Carolina Panthers replatformed and redesigned their entire shop with mobile responsive design, faster page load times and streamlined checkout
- Sportbike Track Gear doubled conversions and lowered overhead while migrating 420,000 SKUs from eBay ProStores to BigCommerce
- Shabby Apple avoided more Magento instability by migrating to BigCommerce, which improved conversion rates, page load speed and decreased shopping cart abandonment
- Bulk Apothecary scrapped a $250,000 Magento project and replatfomred to BigCommerce, which increased sales, increased conversion rates and saved hosting costs
Modern ecommerce platforms are the equivalent of a marketing technology, development and IT staff –– all in one. It’s Moore’s law. Likely when you first launched your brand, ecommerce platforms were cumbersome, expensive and required hours of extra work you ended up taking on internally or that you’ve outsourced to platform experts. Today, there are ecommerce platforms out there that take all the technical heavy lifting off your hands –– allowing your team and business the time and financial resources needed to capitalize on the market with strategic and engaging campaigns.
This is how you win.
You set yourself up for success.
You think about the future.
Would you still be using a Nokia brick phone today? No. The Capt’n Crunch-size chip used in there is now the size of your fingernail –– and it stores a whole lot more.
Upward mobility requires change. Future-proofing is how you blockade against antiquation or even worse, extinction. The line is drawn in the sand. It’s time you choose your side.
Want more insights like this?
We’re on a mission to provide businesses like yours marketing and sales tips, tricks and industry leading knowledge to build the next house-hold name brand. Don’t miss a post. Sign up for our weekly newsletter.
Why Now is the Time to Replatform your Ecommerce Website
In a perfect world, a site replatforming project would be a year in planning. You would have allotted budget and defined clear goals.
In reality, replatforming isn’t something companies proactively plan. Most often, there’s some driving issue — or a number of them — forcing a company to migrate.
The team sees these issues regularly –– and have compiled a string list of the most common below.
Go ahead, check off right next to the ones that apply to your business. Check off more than one, and it’s time to replatform.
- A brand can’t afford to continue doing business with their existing ecommerce platform due to the high maintenance costs.
- Mergers & acquisition activity often creates an opportunity for companies to consolidate their operations and gain the efficiencies of moving to a new, combined ecommerce platform.
- New initiatives pop up, such as launching new brands, product lines or into new markets. With new launches, many brands will test out more cost-effective solutions in order to prove out concept. Often, the more cost-effective platforms outperform the legacy platform the main brand is using, and thus a migration is prompted.
- The old solution has grown unstable under peak traffic conditions, resulting in slow site performance and bad customer experience.
- The catalogue database can’t handle the physical number of SKUs you’ve added to the catalogue over the years.
- The platform only captures a limited number of attributes, can only associate a limited number of product related assets, has a limited call volume on APIs or, as in some cases, can’t handle certain types of content such as video.
- It takes too long to develop new features on the old platform and the backlog of projects in IT becomes unmanageable or cost prohibitive.
Technical Replatforming Documentation
- Marketing teams are at the tip of the spear in online businesses and so they are usually the ones pushing for ecommerce replatforming. Marketing is tasked with not only reaching potential customers and driving traffic to the site, but also converting at the highest rate possible. The team wants something more intuitive, allowing them to be more creative and quick in their GTM execution.
- Old ecommerce platforms can prevent marketing from converting visitors that otherwise might have converted on a newer, more featured platform. Worse still, a company’s old platform may prevent them from competing in key areas entirely. Some of the key features and capabilities that marketing are looking for include
- Improved Site Search: Directed and faceted. Marketing wants to be able to control search results for the best possible user experience.
- Personalization: Dynamic content presentation and optimization based on multiple visitor personas.
- Mobile Commerce: Specific design and funnel for mobile devices in the wake of mobile-first customer expectations.
- Social Media: Hooks for marketing on the top social sites, easy share-ability and social commerce capabilities.
- Tag Management: Re-tagging the site for efficient digital marketing, increased search functionality and better SEO based on Google’s indexing of the site map.
Any one of these requirements could be justification enough for a new platform. Most companies looking to re-platform, however, have multiple of these issues.
Take mobile commerce, for example. Mobile revenue has jumped dramatically with the combination of social media platforms and powerful mobile devices, over 50% for some retailers. Not having your ecommerce website support mobile visitors cuts out a large selling opportunity, not to mention the SEO hit you take from Google’s newest search algorithms, which reward mobile readiness and penalize sites that don’t support mobile.
Not having this one feature, which has take months of coding for an on-premise or custom solution, is reason enough to switch — not to mention the financials of having to pay for such coding work.
Best Ecommerce Platform Options
Before I begin to outline the process for a replatform, it’s important that you understand your ecommerce platform options: homegrown, onsite or on premise, and SaaS.
Below is an outline of each, including pros and cons based on your particular business needs.
This is the basic background information you’ll need for issuing a complete and structured RFP to an ecommerce technology provider, the details of which I’ll get into in a moment.
This is usually a custom LAMP or .NET-based implementation supplemented by various middleware, the origins of which you may or may not know.
Quite often, these platforms are also connected to backend systems running custom-built ERP software. In my experience, I’ve even run across the occasional IBM AS400 mainframe locked away in the deep recesses of IT. This middleware could easily be replaced by your smartphone today, but nobody dare touch it lest it breaks and brings the whole site down.
- Pros: The pros of a homegrown platform are that you have the potential for ultimate flexibility. You can customize each feature exactly the way you want, without the constraint of a template. Although in reality, real world resource constraints can mean that potential flexibility isn’t realized.
- Cons: The cons with a homegrown platform are that you are a customer of one and every feature you want to add has to be developed from the ground up. Homegrown platforms are also often expensive to maintain on a day-to-day basis.
Onsite or On Premise Technology
With onsite, sometimes called on premise, technology, the ecommerce platform is licensed from and then hosted on the client’s internal network.
The client, or business owner, is then responsible for managing all ecommerce aspects including uptime, bandwidth, CDN, PCI compliance and security. Commonly deployed onsite platforms include Websphere, Oracle Commerce and Magento Enterprise.
- Pros: The pros of this option are less obvious. There’s a perception of improved security, but I’ll let the security experts weigh in. “As online shopping continues to overpower in-store shopping, ecommerce sites are increasingly targeted by hackers as they have become a gold mine for credit card information,” said Shahar Tal, Malware and Vulnerability Research Manager at Check Point Software Technologies. “The vulnerability we uncovered [on Magento] represents a significant threat not to just one store, but to all of the retail brands that use the Magento platform for their online stores – which represents about 30% of the ecommerce market.”
- Cons: The cons of onsite deployments are that you need a small army of IT staff to run, maintain and sometimes update the platform. Also, quite often, companies customize their deployments to the point that they get off of the platform upgrade path and are then stuck on an old version of the ecommerce platform. The cost of these upgrades and maintenance, however, is likely the biggest con. A scaling ecommerce business can spend anywhere from $100,000 to $500,000 per year to ensure an onsite solution is functioning properly. Here’s a handy calculator you can use to see what your overall costs would be if you were to migrate to or stay on an on premise solution.
SaaS Ecommerce Technology
Before we hop into this realm, know that there are multiple versions of SaaS ecommerce platforms.
- Multi-tenant: customers share the same instance of the application and receive upgrades simultaneously.
- Single tenant: customers have their own instance of the application, upgrades are up to the customer
- Hybrid models: customers share the same instance with simultaneous upgrades, with open APIs for custom iterations
Multi-tenant architecture is one of the main reasons that SaaS ecommerce platforms have cost advantages over homegrown or onsite implementations. Single tenant SaaS platforms take into account the need for specific brand customizability, but it’s easy to end up off the upgrade path and expose your brand to vulnerabilities (similar to on-premise technology).
A hybrid model is the best option for brands, allowing for low total cost of ownership, simultaneous platform upgrades and open APIs for extreme customizability without falling off an upgrade path. In other words, business owners get the lower cost of the multi-tenant deployment with the custom capabilities of a single tenant deployment.
An example of a hybrid ecommerce platform would be BigCommerce, where you can have a customized version of the platform but still benefit from the Saas implementation.
The main aspect all SaaS deployments have in common is their pricing model. Business owners enter into a monthly payment agreement with associated minimums based on a percent of revenue share. Some portions of the first year’s fees are usually due up front, but not always. Pricing terms vary widely depending on the client’s circumstances; i.e. number of SKUs, monthly sales, monthly traffic and more.
- Pros: The pros of implementing a SaaS platform are primarily based on cost and ease of management. With SaaS, the vendor is developing features for multiple customers and so the expense is amortized across the entire customer base, which keeps costs down for everyone. The SaaS vendor’s roadmap is also usually driven by demand from their customers and so you’re pooling requirements across multiple segments of the industry. This leads to a robust product feature roadmap, which meets and often exceeds the requirements of most clients.
- Cons: The cons of a SaaS deployment are that you are restricted to some degree by the nature of the fact that the platform is usually multi-tenant. This means that the flexibility you might have with a homegrown or on premise platform is not necessarily there. Many SaaS providers, however, have open APIs, which allow for third-party integrators that often function similarly to if you were integrating the software on your owned and operated system. As the SaaS ecommerce industry evolves, this con is much less of concern thanks to open and malleable APIs. In fact, BigCommerce allows for 100’s of API calls per second, letting retailers sync 25,000 product inventory from an ERP in only 60 seconds.
OK, now that you know you need to switch and you know what your options are, it’s time to issue an RFP.
Your Ecommerce Replatform Strategy
First, issue an an RFP (request for proposal)
A proper Request for Proposal (RFP) process will help dramatically reduce your frustrations or concerns as you determine which SaaS provider is right for your growing business.
RFPs are used by scaling and enterprise brands looking to properly evaluate key stakeholder needs, scope and goals in large-scale projects which will affect the operation of an entire organization.
The more information you provide in the RFP process, the less room there is for confusion later on. A sloppy RFP could cost you months in wasted time, so be detailed, clear and over communicate your needs. This post will provide everything you need to do so.
Should I issue an RFP or RFQ (request for quotation)?
For ecommerce platforms, you should issue an RFP. This because of the various attributes unique to online businesses that must be accounted for. Each ecommerce platform handles these needs a bit differently. You want to see their proposal, along with a quote, not just a quote for typical services. RFPs generally require more work on both parties –– and this guide will explain your part, as the business.
How to Write an RFP
Before you start committing the rest of the organization to an ecommerce replatforming project, you should conduct an initial ROI modeling session and begin internally mapping out the RFP process. This is the first step to writing a RFP.
Sit down with finance and do an honest review of the ecommerce business. Before you can begin developing a detailed set of requirements and an RFP, you will need to have the numbers for your business locked down.
These include the usual:
- Unique Visitors
- Gross Revenue
- Average Order Value (AOV)
- Conversion rates
- Number of transactions
- Number of units per transaction
- Gross Margin
- Net Margin
If you decide to go down the SaaS platform route, you will be sharing this information with the vendor so they can calculate anticipated usage and pricing.
Forecast Revenue and Total Cost of Ownership
Next, create a three year forecasted improvement on the above metrics if you were to deploy a new platform. Allow six months post launch for site optimization. Don’t forecast any lift during those six months.
Here’s a sample walkthrough of how you might achieve this for your own business.
The numbers below are based on a last 90 day calculation. The forecast based on 57% overall ecommerce growth by 2018. Conservative numbers are used here.
Once you figure out your business forecast, look in to how much each ecommerce technology solution will cost. You can use our Total Cost of Ownership Calculator here, or take a look at the sample chart below for reference, based on a business making at least $500,000 in revenue annually.
Then, calculate your savings, and figure out the average cost for services like SEO, social media and more. Then, add in the revenue left generally seen by these services, and the upside associated with it for your business’ revenue. Again, you can use our calculator to do this automatically for you, or take a look at our sample below.
Through this analysis, you will have determined the amount of investment you can reasonably afford for your website replatforming project. This will save you time later on and help you to avoid looking too far into platforms that you simply cannot afford.
Remember to Account for Data Migration
Many ecommerce platforms will pass you off to a partner for transferring your catalog and customer data (what many people refer to as “data migration”), adding anywhere from $10,000 to $100,000 to your initial launch fee and 6 weeks to 6 months in go-to-market timing. That’s a lot of money and time –– and can significantly affect total cost of ownership. BigCommerce offers free transfer services for Enterprise customers with a 4 week GTM timeline when coming from non-custom solutions. Ask the platforms you’re considering about thedir options and account for this in your ROI model.
Investigate Built-in Functionality vs. Third-Party Apps and Integrations
A technical replatforming project is an opportunity to change and improve your efficiencies in other areas of the business. To make sure you get the most, then, out of the RFP process, take a look at all existing business processes and determine if there are better ways to achieve the same results.
I also suggest taking a look at the various third-party apps that you have undoubtedly accumulated through the years. For example, automated order notifications, product filtering and faceted search, automatic sales tax calculated at checkout, etc. Many of these can be replaced with features that now come standard on modern ecommerce platforms.
Add the savings from these projected changes into your budget.
For example, 68% of online carts are abandoned and SaaS platforms like BigCommerce now recover on average 15% of those. Be sure to calculate that revenue in your model. Here is a calculator you can use to do so.
Try to use a fact-based measurement criteria during this discovery process. I prefer projected savings, revenue or ROI. This phase of the process can be contentious since you’re talking about eliminating tools, processes and potentially people. The measurement criteria helps to keep the emotion out of the process.
A note on steering committees: I know many people recommend setting up steering committees for this process, but they’re not for everyone and they can definitely slow the replatforming process down. I prefer to have one decision maker leading the project from the client side and have them ensure that all stakeholder requirements are captured and ranked. There will, of course, be the need for stakeholder reviews, but they’re different from establishing an actual committee, specifically in the area of final decision-making. For the fastest and most effective GTM strategy, avoid committees and appoint a project head.
Scope Integration Redirects and Initiation
This is the stage of the replatforming process where you should spend significant time and effort mapping out every touch point between the ecommerce platform and all other systems at your company.
Create a list of each integration point and determine what will happen to that integration during replatforming. It’s at this crucial stage that you determine what’s in scope for the project and what is not.
Also include a review of any catalog transfers that will be necessary and make sure to include them in the RFP, including:
- customer data files
- product catalogues
- assets or content such as product images
Proper due diligence at this stage of the process will save time and money later on. Review everything 2 or 3 times to make sure that nothing has been left out.
BigCommerce, unlike other platforms, has an in-house catalog transfer team to help in the data migration of your store. Our team has more than 15 years of experience between them and have transferred catalog data from Shopify, Magento, Yahoo, Oracle, Demandware and more. Including your number of customer data files, SKUs and content assets will help the team determine catalog transfer scope of work and GTM date for your brand.
Meet with All Potential Stakeholders
Confirm that all stakeholders have been given ample opportunity to share their requirements as well as all business processes that interface with the ecommerce platform.
Stakeholders are usually from the following departments/disciplines.
What Not to Do in the Replatform Process
On a very large project I personally worked on, after numerous sessions with all necessary stakeholders, I asked one last time if we had covered every process, integration point and application that would interface with the new ecommerce platform.
Everyone nodded in acknowledgement … until one voice at the back of the room asked if we had accounted for the two guys in Turkey.
I thought he was joking.
He explained that those two guys performed a critical database conversion on the global master product data file on a nightly basis.
Don’t forget about the two guys in turkey!
But don’t go overboard, either.
I’ve seen countless million –– tens of millions of dollars actually –– wasted on high priced consulting firms more concerned about billable hours than finding the absolute best solution for the client.
Don’t fall into the trap of over engineering your solution.
I’ve also seen architecture scoped out on PowerPoint slides that look amazing but are entirely unrealistic in the real world, either because they would run too slow, cost too much or just not integrate properly.
It’s a myth that you can take the “best in breed” products in various categories and try to make them all fit together. It’s much better to get one good platform and use it to the fullest extent possible. I’d be lying if I said I’ve never seen a company scope out a behemoth of integrated apps only to spend tens of millions of dollars and never see it run properly.
True story: Recently, a company I know of spent millions of dollars (high teens) to deploy a large, well know ecommerce platform. Problem is, that by the time they got done engineering their idea of nirvana, the ecommerce platform’s role was basically relegated to that of a shopping cart!
A state of the art full-blown platform operating at maybe 20% of it’s potential. Millions of dollars wasted, an unnecessarily complicated architecture that took way too long to implement and what they ended up with could have been replaced with at most, a $3 million alternative.
This was a CIO gone wild. And this isn’t an isolated case. I’ve seen it way too often.
A Handy Ecommerce Replatforming Checklist
There are numerous ecommerce platforms available today, everything from simple carts to enterprise grade platforms that include strong search, personalization and CMS capabilities.
For our purposes, let’s say that there are about 30 different platforms to choose from. That’s far too many to engage in an RFP.
Based on your current online revenue, SKUs, ratio of traffic vs. transactions, average order value, units per order and any unique elements specific to your business such as hard goods vs. soft goods, continuity/subscription business or complex configuration capabilities, you should be able to narrow down your RFP list to 5-8 vendors.
At JCH, we use a process called the Accelerated Vendor Selection Process (AVSP). This process is based on our experience and knowledge of ecommerce platforms, and this helps us to narrow the focus of the RFP down to the key features that are most important to the client.
Our RFPs contain over 150 questions to confirm vendor capabilities and for use in vendor comparison charts.
This may seem like a lot, but let’s put it into context: a mid-tier SaaS platform contains over 280 features. That doesn’t include third party integrations, catalog transfer services, systems architecture or security compliance issues — all of which will need to be addressed in the RFP process.
How to Put Platforms to the Test
Based on the responses to your RFP, you should now have a short list of 3-5 potential vendors.
The next step is to create a detailed set of use cases to be performed by the vendor, via webex for smaller opportunities and onsite for larger deployments.
There are a couple reasons for this:
- Stakeholders get to see what a day in the life of using the platform will be like for them. Their feedback is invaluable. They get to see the different ways various vendors have chosen to execute various tasks in the platform and can see which methodologies might suit their particular requirements better. Lastly, maybe most importantly, they feel a sense of ownership in the process and an appreciation for the final vendor selection.
- The more important reason for these tests is to make the vendor demonstrate their capabilities live. It’s easy for a vendor to say that they support a feature, but when it comes time to demonstrate it, the finer details are revealed. For example, a vendor may say they support a certain feature but in reality it requires a separate customization to actually deploy it in the field.
The list of use cases that you develop will depend on the size of deployment, but for the larger ones, it is advisable to schedule about four hours. Some scenarios take 10 minutes to run through, others can take 30 minutes.
It’s very important that each vendor be given the same list and allotted time to complete their scenarios. This creates a level playing field upon which comparisons can be more easily made, especially for the stakeholders who are new to the process.
You can use this checklist and agenda for your teams and the platform you are testing. This covers the majority of common needs during a replatform.
We also allow half an hour at the beginning of the meeting for a general company sales pitch presentation, and about 20 minutes at the end for closing remarks and a final pitch. Here is what our top level agenda looks like, simplified.
Don’t Forget About Data Migration Services
Transferring your product, category and customer data is perhaps the most overlooked aspect of an ecommerce replatforming or replatforming applications, in general. Accurate data is essential to running your business.
A poor transfer could result in:
- Incorrect product mapping
- Incorrect product commendations
- Incorrect product options
- Incorrect product images
- Inaccurate customer data
- Poor syncing with ERP or POS (think Square or Netsuite)
And those are only to name a few. You’d be stuck going through each individual SKU and updating all information for product data that was transferred or migrated incorrectly. For customer data, it would just be lost forever.
I cannot stress enough how big of a deal this is. Again, I’m preaching to the choir.
So, once you’ve decided which platform, or have narrowed it down to two, you will switch to, ask immediately about migration and transfer services. And don’t let an unclear answer pass.
Many ecommerce platforms will pass you off to a partner for catalog transfer services, adding anywhere from $10,000 to $100,000 to your initial launch fee and 6 weeks to 6 months in go-to-market timing. That’s a lot of money and time –– and can significantly affect total cost of ownership.
Do not sign a contract until you have this information. If you are passed off to partner, talk to that partner immediately. Get a solid understanding of how the catalog transfer or data migration will be done and similar stores they have already transferred, ideally from the same platform you are on. Reach out to that brand, too, and ask about the service.
Better yet, choose an ecommerce platform that provides this service in-house. At BigCommerce, we have a team of dedicated experts with a combined 30+ years in ecommerce and 15+ years in catalog transfer services. In the last three years alone, they have transferred more than 20,000 online stores from 50 different ecommerce technology platforms. Our service typically take 4-8 weeks for GTM.
This comes at little to no additional cost to a brand.
Because our team has worked with so many brands, they’ve learned that every single online store is unique, and that as they’ve scaled, so has their service. To ensure catalog & customer data is transferred successfully, our catalog transfer services team implements a 3 steps quality assurance process. This process includes spot checking the data on your new BigCommerce store. Our goal is to transfer these items safely, swiftly and securely.
Top 5 Data Migration Myths Debunked
In the course of performing so many transfers, our team has spoken to a diverse group of business owners, walking them through the process of moving to a new platform. Below are the top five myths they’ve heard about catalog transfers.
1. Data Migration Myth #1: We miss out on sales while you transfer our data.
Your store won’t go offline during the transfer process. We do all the work on your new BigCommerce store backend, then give you as much time as you need to customize your settings, test your site and train your team. When you’re ready, and only when you’re ready, you can launch your new ecommerce storefront — complete with updated data already uploaded into your backend. This allows you to continue business as usual from day one.
While all of this is happening, your original store stays live on your current platform. We don’t require that it come down, and BigCommerce and our global network of partners actually advise against it. We understand that uptime is one of the most crucial factors to gaining and maintaining consumer trust, so all our work can happen with no downtime required.
2. Data Migration Myth #2: We’ll lose our design if we replatform.
Worrying about losing your beautiful, custom design? Don’t. BigCommerce’s open template files allow you to bring custom design elements to your new store, and our design partners, ensure that it happens seamlessly. Check out a full list of BigCommerce’s best designed customer sites –– and how those designs have increased conversion.
3. Data Migration Myth #3: When we move the store to a new host, we’ll lose all our traffic.
It is true that moving to a new server, even when using the same domain name, can impact search engine rankings if done improperly. The good news, though, is that people move servers all the time, and search engines like Google have best practices which mitigate the effects.
We follow those best practices to minimize all controllable risk. We properly implement 301 redirects for your product and category pages. Our goal is to move your product data with the same search ranking foundation you had built on your previous platform. That way, our SEO-friendly platform can quickly drive your traffic to new heights.
4. Data Migration Myth #4: Replatforming means we can clone our store exactly.
No, you cannot clone your store exactly. You can, however, transfer a majority of your existing data from your current ecommerce store to your new backend. In fact, we make sure that happens without opening you up to any potential issues or liabilities.
As for your store’s look and feel, you’re probably thinking about leaving your current platform because it’s lacking in some way, so why would you want to recreate those same shortfalls? The quicker you embrace the idea that it requires some change to improve your online business, the quicker you can benefit from transferring to a fully featured enterprise solution like BigCommerce. We offer a wealth of next-level features that will ensure your transition is as painless — and profitable — as possible.
For instance, with dozens of integrated payment gateways, you’ll rarely need a payment option we don’t offer. Chances are that we have an integration with the payment gateway you are using right now, and you may even find new options like Square and PayPal powered by Braintree that you like more.
In all, BigCommerce offers more than 250 one-click integrations with leading software providers like Survey Monkey, HubSpot, Alibaba and Salesforce. That makes it easy to integrate with the tools you already use.
Plus, our open and unrestricted API blows our competitors out of the water. Seamlessly connect to critical business software with a powerful API that processes updates up to 100x faster than Shopify Plus. BigCommerce can handle 100’s of API calls per second. Shopify Plus limits you to 10 per second. Performing an ERP inventory sync of 25,000 products and variants on BigCommerce would take 60 seconds, compared to 2hrs using the Shopify Plus API.
5. Data Migration Myth #5: We have great engineers. We can do it ourselves.
Even if you’re a great developer, our experience has taught us that the first time you undertake an unfamiliar task like this, it rarely goes according to plan. Anybody who has tried to renovate their own house knows how steep the learning curve can be. Wouldn’t your time be better spent growing your business and serving your customers while delegating your transfer to veteran engineers who can get it done quickly and correctly?
Your data isn’t something you want to risk, and we’ve heard our fair share of self-transfer horror stories. When you’re talking about securing and improving your financial future, you can’t afford to let your ego get in the way. Instead, trust your migration to an industry-leading team with more than 20,000 successful migrations completed.
For more information on BigCommerce’s transfer services, read our support documentation on how to move your store to BigCommerce. And know, this is only documentation. You’ll have an account manager and on-boarding consultant by your side, handling all the heavy lifting, every step of the way.
In all, figuring out which ecommerce platform is right for your business is a time consuming task. But a proper replatforming project is well worth the wait.
A modern ecommerce backend allows you to streamline processes while increasing site speed, stability and security to outperform industry standards. SaaS works the way technology should –– behind the scenes. Plus, it does so cost effectively, allowing you to invest in marketing initiatives that drive growth for your brand.
Less Development. More Marketing.
Let us future-proof your backend. You focus on building your brand.