Get off Magento.
Keep the business.

A complete store overhaul for the operator or technical director who is done paying Magento to stand still.

Fixed fee

Quoted after a brief discovery and AI assessment of the live store. No public rate card.

Hosting

We host it, or you host it, whichever is best for the business. The store stays supported after cutover.

Stack later

Custom we host, Shopify, or something novel. The store decides. Not a religion.

Magento used to be how serious stores got control. Then Adobe bought it. Then the specialists got scarce. Then every security bulletin became a project, and every merchandising change became a ticket. The platform did not get worse overnight. The cost of owning it did.

You do not need another Magento agency. You need the catalog, the checkout, the campaigns, and the people who sell, moved off a stack that now runs you.

The real problem

A desk of tangled cables, tickets, and a waiting store mannequin — Magento, from the operator's chair
Extensions. Patch tickets. A specialist queue. The store, waiting.

The bill is not the license

Adobe Commerce licenses start in the tens of thousands and scale with GMV. Magento Open Source is free until you add specialized hosting, OpenSearch, Redis, Varnish, PCI, and a developer who can safely touch it. Mid-market total cost often lands in the high five or six figures a year before anyone ships a merchandising idea. The license is the visible line. The tax is everything around it.

Security you cannot actually apply

SessionReaper visited an estimated 81% of Magento stores. Most owners did not patch in time, because a patch can break thirty extensions, checkout, or the ERP connector. Adobe has rated some critical issues as a thirty-day patch while working exploits appear in days. If your last upgrade took a quarter, you are already the target. That is the operator's bind: stay unpatched, or risk the register.

Adobe's calendar now owns uptime

Cloud merchants on older 2.4.x versions face hard deadlines: upgrade third-party dependencies or risk admin lock and inbound traffic suspended. That is not a roadmap item. That is a date on someone else's slide that can take the storefront offline. Technical directors are being asked to staff another forced upgrade instead of work the business asked for.

Every change is a specialist ticket

A landing page, a shipping rule, a campaign, or a new payment method waits on a scarce Magento engineer. Magento talent is expensive and thinning out. The people who run the company cannot operate their own store. That is the actual problem. Not "we need a redesign."

The store is slower than the company

Default Magento storefronts are heavy. Hyvä became a cottage industry because the theme you shipped could not sell. Meanwhile the business needs faster merchandising, a checkout customers finish, and a site the team can run on a Tuesday. Complexity stopped being a feature the day it started blocking revenue.

What we actually do

A complete overhaul. Not a theme swap. Not a lift-and-shift of the same mess onto a new logo.

Catalog, customers, orders, and the SEO that already makes you money
Checkout, payments, tax, shipping, and the integrations you already depend on
A storefront operators can merchandise without opening a ticket
Hosting with us or with you, whichever is best for the business, so the existing operation stays supported

We have run ecommerce for eleven years at Gagosian, built Magento stores for operators who needed the catalog to sell, and shipped DAR.WIN, an AI personalization platform with native Magento and Shopify integrations. We have also built Shopify apps and stores. We are not learning ecommerce on your dime.

What you get after the switch

Magento stores are built to administer a catalog. The store you get is built to move a purchase. Shoppers research, narrow, and compare on the site. Your team merchandises without opening a ticket. Orders, inventory, and money keep moving through the systems the business already runs.

On a serious Magento install, the extensions were the integration layer, the cron was the message bus, and customer groups were the price book. Those motions come with you. Discovery names which ones are in the fixed fee.

Traffic that arrives decided

The catalog can stay large. The path through it gets specific, built around how your customers already research, compare, and buy, before they call, before they reorder, and before they walk into a location.

Narrow a wide catalog by the attributes that decide the purchase: spec, size, compatibility, budget, availability, and whether this account is allowed to buy it
Compare products, options, and packages side by side, including the SKU a buyer would otherwise have to decode on a call
See scope before anyone commits: lead time, which warehouse ships, service area, and what the order costs landed
Land on a fit (the right SKU, the right account, the right ship-to), then check out, request a quote, or hand a clean order to your team

Paid search, organic, and the campaigns you already run land in that path. You get more orders and quotes from people who can buy, and fewer projects that were never a fit. Clicks stay cheap. Progress is a buyer who already knows what they want.

Built around the way you sell

The Magento stores that are hard to leave have a commercial model a generic theme will flatten. The overhaul keeps the model.

Catalogs that change by region, brand, customer group, contract, and season
Promotions, MAP, contract pricing, and partner or co-op programs, expressed as selling rules the business can run
Multi-store, multi-brand, and multi-location selling, with the order routed to the warehouse, rep, or shop that should own it
Long cycles: quotes, internal approvals, reorders, and a salesperson placing the order beside the buyer
Direct checkout where the product is simple enough to buy now: parts, accessories, replenishment, and consumables

The back office that has to come with you

A Magento store that runs a company is an integration hub. If it moves an order, a unit, or a dollar today, it is in the assessment. These are the scenarios we expect to find.

ERP and the books

Orders, customers, invoices, credit memos, shipments, and item masters in both directions. NetSuite, SAP, Dynamics 365, Business Central, Sage, Acumatica, Epicor, Infor, Odoo, or the internal system a previous agency wired up with a custom module. Multi-entity and multi-subsidiary, including the case where one brand sells and another company invoices. Inventory quantity and base price have one owner. The storefront sells. The ERP records.

Pricing, contracts, and who can buy

The commercial logic Magento buried in customer groups, catalog price rules, and cart price rules. Shared catalogs, tier prices, contract pricing, MAP, and date-bound promotions. Company accounts with buyers, approvers, and admins, each with their own catalog, payment methods, and credit limit. Negotiable quotes that start as a conversation and end as an order. Requisition lists, quick order by SKU, and CSV upload for the purchaser who already knows the part number. Punchout (cXML or OCI) when a customer buys from inside their own procurement system.

Warehouse and inventory

Multi-source inventory: the website, the shop, the 3PL, and the drop-ship vendor as separate stock. Available-to-promise, reservations so two carts cannot sell the last unit, safety stock, backorders, and preorders. Kits and bundles that decrement the components, not a phantom parent SKU. Lot, batch, serial, and expiry when the product requires them. Pick, pack, and ship status back on the order the customer is watching, plus receiving, ASNs, and the RMA that puts a return on the right shelf. WMS and warehouse platforms such as Extensiv, ShipStation, ShipBob, SkuVault, Fishbowl, Cin7, Deposco, Manhattan, Körber, NetSuite WMS, and SAP EWM, or the flat file the warehouse already trusts.

Shipping and fulfillment

Live carrier rates and the table-rate logic Magento stores accumulate over years. UPS, FedEx, USPS, DHL, freight and LTL for anything that does not fit a parcel, customer collect accounts, free-shipping thresholds, and methods that exist only for one account. Residential versus commercial, signature, hazmat, and destinations you will not ship to. Split shipments and partial fulfillment when one warehouse cannot fill the whole order. Ship-from-store, click-and-collect, and local delivery when the unit is already in a shop. International duties, landed cost, DDP and DDU, and restricted SKUs. Labels and tracking tied to the shipment, and the customer email that fires when the carrier scans the carton.

Payments, tax, and finance

The tenders already on the checkout: cards, wallets, PayPal, Buy Now Pay Later, and B2B terms such as net-30, purchase orders, and company credit. Stored methods, partial capture, and a split tender on one order (store credit or a gift card alongside a card), which finance already reconciles. Store credit, gift cards, and reward points as real liabilities, including partial redemption. Tax finance can defend: Avalara, Vertex, or TaxJar, with reseller exemptions, VAT, and GST. Refunds and credit memos. Payouts and invoices into QuickBooks, Xero, Sage Intacct, or the ERP, so month-end is a close. Multi-currency settlement where you already take it.

Catalog, search, and the pages that rank

Configurable, bundle, grouped, and custom-option products, with the attribute sets merchandisers already know. A PIM such as Akeneo, Salsify, Pimcore, or inRiver, when the PIM is the source and the store is a channel. Multi-website, multi-store, multi-language, and multi-currency storefronts that share one catalog and differ where they must. Search that was bolted on because native Magento search could not carry the catalog: Algolia, Klevu, Searchspring, OpenSearch. Facets, synonyms, and merchandising rules that pin a campaign. URL rewrites and redirects so the URLs that already rank still resolve. Landing pages and campaign content the marketing team can publish.

CRM, marketing, and service

Salesforce or HubSpot receives the account with the order attached, so sales works the customer they already have. Klaviyo, Dotdigital, Attentive, or Mailchimp on real catalog and order events: abandoned checkout, replenishment, and the segment that used to be a Magento customer group. Gorgias or Zendesk with the order sitting in the ticket. Reviews and loyalty where they are already part of how you convert, with the points balance finance already tracks.

Channels, fraud, and the long tail

Amazon, eBay, Walmart, Google, and Meta when those channels already share the catalog and the inventory, so a unit cannot sell twice. Subscriptions and replenishment on a cadence, including the custom recurring profile a module invented years ago. Fraud review with Signifyd, Riskified, or Kount before capture, on the same orders finance reconciles. POS and in-store stock when the shop and the site sell the same shelf. Custom order statuses, holds, address validation, and the one integration operations runs every Monday. That last one is usually where the real cutover risk sits.

After launch, someone still owns it

We host the store, or you host it, whichever is best for the business. When we host, patches, uptime, and the next integration are our work. Your team runs campaigns, pricing, and the catalog either way. The next promotion, the next warehouse, and the next carrier are changes to a live store.

The site is allowed to get sharper after go-live: clearer paths where buyers stall, tighter rules where the wrong order keeps getting through, and merchandising drawn from how this catalog actually sells. You can call the people who already know it.

How it works

A short discovery. A fixed fee. A cutover that does not pause the register. Then we host it, or you host it, whichever is best for the business.

Laptop scanning an abstract storefront wireframe during assessment — The transition plan

Hands assembling an architectural model of a shop — The transition plan

Sales do not pause while we rebuild

Now

Magento store

Taking orders. Still the business.

Meanwhile

Overhaul in parallel

Assess, quote a fixed fee, rebuild.

Then

Cutover, then hosting

Catalog, URLs, checkout, and the team move. The register never goes dark.

Stack is a decision, not a religion

After that assessment, we recommend one of three paths. We do not sell a platform. We get you off Magento and keep the business running.

A hallway opening onto three rooms: a workshop, a bright shop, and an unusual geometric space — Custom we host
We rebuild the store and operate it for a monthly price. You get off Magento and off the specialist market.

Who this is for

The owner or operator who is tired of Magento being the most expensive employee.

The technical director who cannot staff another upgrade, another patch weekend, another "quick" extension conflict.

Magento 1 leftovers. Magento Open Source 2. Adobe Commerce Cloud. If the store is the business, and Magento is now the drag, this is the conversation.

Start with the store

Send the URL and who you are. We will tell you whether a fixed-fee overhaul is honest, and which stack we would actually put under it.

Get off Magento.
Keep the business.