Adobe Commerce 2.4.6 left regular support on 11 August 2026 and its extended support ends 31 August 2027. For a B2B merchant that deadline lands on a store where price is not a number in a product table. Contract pricing, credit limits, payment terms, and salable stock live in the ERP, and Adobe Commerce holds a copy that has to stay correct through cutover week. The objects at risk are company accounts, sub-user roles, shared catalogs, requisition lists, and open negotiable quotes, and each has a counterpart record in SAP, Business Central, NetSuite, or Infor that keeps changing while the migration runs.
What decides this migration
| Criterion | Ask before signing | What a weak answer sounds like |
|---|---|---|
| ERP ownership boundary | Which system owns base price, contract price, salable stock, credit limit, tax class, and payment terms, field by field? | "Both systems stay in sync", with no single writer named per field |
| Company and buyer hierarchy | How do the company entity, admin, sub-users, roles, and payment-on-account balances move, and what maps to the ERP customer number? | Scope lists customers and orders but never names the company entity |
| Contract pricing model | Shared catalogs, catalog price rules, or ERP-pushed tier prices, and how many customer groups does that produce? | Pricing is "handled by the integration", with no group count and no reindex window |
| Quote and requisition continuity | What happens to negotiable quotes open on cutover night, and are their price snapshots preserved? | Open quotes get "recreated after launch" by the sales team |
| Sync architecture and retries | Which middleware, which queue, and is order create idempotent when a message is redelivered? | Nightly file drops described as real-time integration |
| Cutover and rollback | Who is staffed, when does the ERP order poller switch stores, and what triggers rollback? | Rollback is "restore from backup", with no decision owner and no time bound |
Which agencies fit this migration
- Wagento, first, because it is the only agency of the eight that publishes a position on the question this guide turns on. On its own site, Wagento states "Your ERP is the source of truth" and reports 6 ERP platforms integrated and 40+ certified developers. The six platforms are not named on the pages read, so confirm the incumbent system is one of them
- scandiweb, second, for multi-market B2B re-platforms with a PIM and an ERP both in scope. Its Macron case names Pimcore PIM and SAP ERP behind an Adobe Commerce B2B build serving more than 150 countries, with order creation time cut by 40%. scandiweb publishes this site
- magic42, third, on named systems: its integration pages name Sage, SAP Business One, Microsoft Dynamics 365 Business Central, Epicor, Kerridge, Khaos Control, OGL, Prima Solutions, and RetailSystem, and its Adobe Commerce page names Stone Computers for a B2B portal with PunchOut
- ParadoxLabs, for B2B checkout with stored payment profiles and payment on account, where 2.4.x patch upgrades surface breakage first, on its own payment modules and published patch timings
- PushON, for cutover staffing on both sides of the integration, since its migration page lists integration implementation across ERP, PIM, and fulfillment systems as a stage
- Bemeir, for a US distributor weighing Adobe Commerce B2B against a BigCommerce B2B build, on the partnership spread its site states
- Customer Paradigm, for a free code audit of which Commerce B2B features are in use before the edition is fixed; the August edition placed it on a downgrade sentence its page no longer carries
- MageComp, for rebuilding a B2B extension, such as a tier price importer or a quote add-on, rather than repurchasing it when the vendor no longer ships a 2.4.x release
The sequence that keeps the ERP authoritative
An ERP-connected migration breaks at the seams between four systems, not inside any one of them: the ERP, the PIM, the Adobe Commerce B2B module, and the middleware between them. Start with ownership, field by field. Base price, contract price, salable quantity, credit limit, tax class, payment terms, and customer number each get exactly one writer. Adobe Commerce expresses contract pricing through shared catalogs, and every shared catalog creates a customer group; the price index holds a row per product, website, and group, so 40,000 SKUs across 3 websites and 60 shared catalogs is 7.2 million rows on a full reindex. Move catalog_product_price to Update by Schedule, load tier prices through the async bulk REST endpoints, and count the groups before anyone agrees a reindex window.
Company data is the second seam. The frequent failure is mapping the ERP customer number to the individual customer instead of the company, after which invoices attach to a buyer rather than the payer and credit checks clear against the wrong entity. Legacy stores that ran one shared login per account hide this until sub-users are created. The third seam is delivery guarantees: queue consumers deliver at least once, so a non-idempotent order create produces duplicate ERP orders on retry. Idempotency keys on every message, a dead letter queue a human reads, and one writer for salable quantity keep MSI reservations from drifting against ERP stock.
- Freeze catalog and price maintenance in the legacy admin, with a written freeze time
- Full load of companies, buyers, roles, contract prices, and stock, then a reconciliation report per object using counts and totals, not spot checks
- Dual run read-only, with the ERP still polling only the legacy store
- Delta sync of quotes, credit balances, and stock
- Switch the ERP order poller to the new store before DNS, so no window exists in which both stores are pollable
- Carry the sequence tables across so order increment IDs continue, since an ERP keyed on order number rejects a restart at 1
Questions
Does Magento Open Source support company accounts and shared catalogs?
No. Those ship with the Adobe Commerce B2B package. Merchants staying on Open Source reach them through third-party extensions or custom entities, and contract pricing is then modeled with customer groups and catalog price rules.
What happens to open quotes at cutover?
Negotiable quotes carry a price snapshot and an expiry date, so re-pricing them on import creates quotes the buyer never agreed to. Freeze quote creation several days ahead, migrate quotes in Submitted and Updated states with snapshots intact, then move requisition lists by SKU once the catalog load finishes.
How long does a B2B migration with ERP integration take?
Integration count drives it, not catalog size, because every object in scope needs its own mapping, fixtures, and reconciliation report. No agency here publishes a B2B migration timeline; scandiweb's migration services page states 8 to 16 weeks for a typical migration, and reconciliation between systems usually sets the launch date.