← All case studies Magento → Shopify

POLYWOOD left a custom Magento build that took most of the engineering time

A vendor case study of POLYWOOD moving from Magento to Shopify.

A Shopify case study, so the numbers are the vendor’s. It credits Benjamin Spiegel, POLYWOOD’s Chief Digital Officer.

POLYWOOD makes furniture to order, with about 150,000 product variations.

Why they left

Maintaining a custom Magento build took over 80% of engineering time. Spiegel says Shopify apps covered about 75% of the custom features.

What the page reports

  • Conversion up 22%
  • Average order value up 12%
  • Total cost of ownership down by six figures

No time period or dollar amount is given. An expected organic traffic dip after the URL change did not happen.

What it leaves out

No migration timeline, redirect map, import logs, or details on lost data. We can’t tell how they kept search traffic or which part took longest.

If you plan the same move

This part is my advice, not something POLYWOOD reported. It comes from the Magento → Shopify playbook.

Check the maintenance load in your own store. If most of your engineering time goes to maintenance, list each custom feature and see whether an existing Shopify app already does it.

Then:

  • Export the Magento URL rewrite table. Shopify needs a redirect for every path you drop, and you want them in place before DNS moves.
  • Pilot configurable products first. A variant row fails to import when an option is missing, and 150,000 variations means a lot of rows.
  • Place one paid order through every live connector on a preview store.
  • Keep the Magento admin readable until finance signs off on historical orders.