If your web store runs on Sage eBusiness Manager, or on middleware built in its era, you already suspect what this article confirms: the road ends. This is a plain accounting of what happened, what it means operationally, and the realistic paths forward, including the questions we would ask any vendor, ourselves included, before signing a replacement.
What actually happened
As of May 2023, Sage removed eBusiness Manager from sale. Existing installations did not stop working that day, and that is exactly what makes the situation easy to ignore: nothing broke. But three clocks started ticking.
The compatibility clock. eBM assumes an old web stack. Every server migration, PHP deprecation, TLS policy change, and browser update is now a small gamble with no vendor on the other side of the table.
The security clock. A web-facing system that no longer receives meaningful updates accumulates risk quietly. Card data and customer PII flow through these stores. The compliance conversation gets harder every year the stack stands still.
The people clock. The pool of people who can confidently work on eBM and its era of middleware shrinks every year. The day something breaks, your fix depends on finding one of them, on their schedule.
The same logic applies if you are not on eBM itself but on a connector built for a platform you want to leave, for example an aging Magento store wired to Sage through middleware whose vendor has moved on. The connector, not the storefront, is usually the thing keeping you stuck.
The four realistic options
Option 1: stay and freeze. Cheapest this quarter, and a legitimate choice if a web store is genuinely marginal to your business. Be honest about what it means: no new capability ever, a growing security surface, and a migration that still happens someday, on the worst possible schedule instead of yours. If you choose this, at least verify your backups and document the system while people who understand it are still reachable.
Option 2: replatform the storefront and keep hand-keying. Move the web store to a modern platform and let staff retype web orders into Sage. This is more common than anyone admits, and it works right up until volume makes it the most expensive data-entry position you have ever funded, with duplicate and typo risk on every order. Reasonable as a bridge; corrosive as a destination.
Option 3: buy a connector subscription. There are subscription connectors that link Sage 100 to modern storefronts. For some shops they fit. Evaluate them on the same questions listed below, and pay attention to three structural realities: monthly pricing compounds forever, some require the storefront’s premium tiers to unlock B2B behavior, and when the subscription ends, so does the integration. You are renting the bridge your revenue drives across.
Option 4: own the integration layer. Have the connector and storefront integration built as something you own, running on your own infrastructure, with the vendor relationship structured as delivery plus optional care rather than perpetual rent. This is the shape we build (ForgeSync Enterprise), so weigh our bias accordingly, and then judge the shape on its merits: it is the only option where the asset survives the vendor.
The questions to ask ANY replacement, including us
The demo will look good. All demos look good. These questions separate the ones that survive year two.
“What stops the same order booking into Sage twice?” Networks hiccup at the worst moments. If the answer is not something like a stamped order key verified by reading it back out of Sage, with retries that check before they book, you will eventually double-book an order and a deposit, and you will find out from an angry customer.
“What happens to an order that cannot book, say a credit hold?” The wrong answer is that it fails, or worse, books wrong. The right answer is that it waits visibly, with the reason in plain language and a retry, where your staff can see it.
“Show me the day the sync server dies.” Orders should queue safely, nothing should be lost, and someone other than your customers should notice. Ask who gets alerted when the system goes silent, not just when it throws errors. Silence is the failure mode that hurts.
“What do you install on my ERP server, and what access does it need?” The answer should be short: minimal software, a least-privilege user, no inbound holes in your firewall as the default. If they need a sysadmin SQL account, keep asking why until the answer embarrasses someone.
“Who else runs on the same system as my data?” Multi-tenant platforms pool customers on shared infrastructure. That is not automatically wrong, but you should know, and your IT policy might.
“What happens if you disappear?” Every vendor should have a non-evasive answer. If the honest answer is that the integration stops working when the subscription stops, price that risk into the monthly fee, because it is real.
“What does leaving look like?” Ask for the offboarding procedure before you sign, in writing. A vendor with a documented exit is a vendor confident you will not want to use it.
The migration itself is smaller than you fear
The instinct that keeps stranded shops stranded is the belief that moving means retyping the business into a new system. It does not. Your catalog, customers, pricing, and history live in Sage, and Sage is what a competent integration syncs from. A store you already operate can be matched to Sage item by item with a review list for anything ambiguous. A well-run cutover proves the new path with a test order booked into Sage and read back, runs both paths in parallel, and flips with a rollback available, so cutover day is a decision, not an event.
Where to start, regardless of vendor
Ten minutes with your IT contact answers most of the qualification for any option on this page: which Sage 100 edition and version you run, whether a concurrent license seat is spare, who can provision a read-only SQL login and how long change control takes, and who owns your store’s DNS. Gather those answers first and every vendor conversation, including one with us, gets shorter and more honest.
If you want that conversation, we will tell you within one call whether your setup fits what we build, and say so plainly if it does not.