AI Engineering
Ecommerce Engineering
Product Engineering
Product Design
Platform & Integrations
Managed EngineeringM1 → M2
platform migration, delivered in-house
2.3 → 2.4
major Magento upgrades after the move
7
custom modules for subscriptions, promotions and fulfilment
The client
Previnex is a health and wellness brand selling clinically focused supplements: protein powders, multivitamins and specialised formulas for joint, immune and muscle health. The business is built around subscriptions, so the store has to make repeat orders effortless.
The brief
Keep a subscription business running smoothly on Magento 1, then move it to Magento 2 without disrupting subscribers, and keep the new store current and fast as the brand grew.
What we did
Ran the Magento 1 store. From 2016 we looked after the original Magento 1 store: features, fixes and day-to-day engineering.
Migrated it to Magento 2. We rebuilt the store on Magento 2 Open Source in 2019, carrying over products, customers, orders and the subscription setup, and launched on the 2.3 line.
Kept it upgraded. After the move we took the store across the 2.3 to 2.4 boundary, one of the bigger jumps in Magento's history, up to 2.4.6.
Built for subscriptions. Seven custom modules handle what the brand needed beyond its extensions: adding products to existing subscriptions, canister and pouch packaging options, guest-checkout coupon limits, automated shipment updates, sample-order emails and sponsorship programmes.
Connected the growth stack. Subscriptions, reviews and loyalty, email, referrals and affiliates, checkout, shipping, custom reports and marketplace listings, all kept compatible through every upgrade.
All custom code in the Magento 2 era was written by our own engineers.
What this shows
A migration is the riskiest moment in a store's life, and subscriptions make it riskier: a broken renewal is lost revenue you don't see until next month. We moved this store across platforms and major versions while the subscription business kept running.
What we'd carry into the next migration
- Rehearse the subscription cutover. We now run a full dry run of subscription renewals on the new platform before launch day, with real (anonymised) subscriber data.
- Decide the extension stack with the upgrade path in mind. A large marketing stack is powerful, and every extension is one more thing to keep compatible. We review each one against the next two upgrades before it goes in.
Gallery
