4ocean sells bracelets and funds ocean cleanup. Co-founder and CEO Alex Schulze started the company on Shopify. After two years they moved to BigCommerce. Then they came back.
The public write-up is a Shopify customer story, so it is a vendor page. I could not find a matching post on 4ocean’s own site. This case study stays with what Alex said there.
If you are looking at the same route, start with the BigCommerce → Shopify playbook. Shopify’s migration guide is the generic path. 4ocean’s version is a return trip after a bad outbound move.
Why they left Shopify the first time
The business went from two people to more than 300 in two years. People told Alex they had outgrown Shopify and needed a platform for larger companies. BigCommerce was the suggestion.
He said the move off Shopify made the business plummet. The migration took a lot of time and money. Organic traffic dropped about 80%. That 80% is his line on a Shopify page, about the Shopify-to-BigCommerce move, not about the return.
What broke on BigCommerce
Everyday work became a ticket. Changing a SKU, reading a report, updating the site. Things he used to do himself now needed a hired team.
Table-stakes storefront behavior needed custom builds. Sold-out state. Swiping product photos. Enlarging a photo. He also named a “notify me when this is back in stock” button that took almost two weeks of custom work.
He said they spent tens of thousands of dollars on development that used to cost nothing, and that money was not going to cleanup operations.
Other people later pushed Adobe Commerce, WooCommerce, and Salesforce. He went back to Shopify.
How they came back
They partnered with eHouse Studio for the BigCommerce-to-Shopify move. Alex said it was easier, faster, and more streamlined than the earlier migration onto BigCommerce. Shopify says they relaunched substantially faster than the BigCommerce launch. Neither page gives a day count for the return, so I am not inventing one.
The published story is about control, not about a product CSV. Marketing could change a banner or a promotion without a vendor. Alex could open analytics on his phone instead of waiting two days for a business-intelligence hire.
Shopify’s current migration menu is CSV, a third-party app, or a partner. Catalog, customers, and some orders can move. Themes, checkout, apps, and subscriptions do not. You rebuild those. The playbook already treats storefront, checkout, and apps as manual work.
Passwords do not travel. Historical orders may import without becoming live payment records. 4ocean does not describe those gaps, so I am not filling them in.
What they gained
Shopify’s summary is tens of thousands of dollars less in operating cost, a faster relaunch than the BigCommerce one, recovered web traffic after that earlier 80% drop, and extra revenue from apps for upsells and subscriptions.
Those are the vendor’s headlines around Alex’s quotes. He did not publish a traffic chart or a P&L line.
The product they named after the return is a trash tracker that shows cleanup progress. He said that kind of project was unthinkable on BigCommerce because the team was busy rebuilding sold-out buttons.
What the vendor page skips
Shopify does not publish a failed import, a broken redirect, or a refund that could not be found. We only know they hired a partner and preferred native features over custom work.
SEO after the return is described as recovered traffic, not as a redirect map. If you do this move, the playbook still wants a URL inventory before you cut DNS.
The first migration, Shopify to BigCommerce, is the warning. The Shopify → BigCommerce playbook is that outbound route. 4ocean is the case for not taking it just because headcount jumped.
What I would copy
Write down the storefront jobs you do without a developer today. Sold-out state, image zoom, a back-in-stock alert. If the new platform turns those into tickets, the migration cost is not the importer. It is the next two years of agency hours.
Do not leave Shopify only because someone said you outgrew it. 4ocean’s first move was a scale story. The return was an operations story.
If you already sit on BigCommerce and want Shopify back, hire the partner for theme, apps, and redirects. Use Shopify’s importer for catalog and customers. Test a checkout, a refund, and a sold-out product before you point the domain.
Keep the old store readable until those three paths work. The playbook’s rollback is Shopify → BigCommerce if the return goes wrong.
The BigCommerce → Shopify playbook is the checklist I would run. Use the Shopify interview for the “we already tried the other way” call, and remember it is a vendor page.