An industrial manufacturer's store, modernized.
BinMaster builds level-measurement and inventory-monitoring equipment for agriculture and industry. IWD brought its Adobe Commerce store current, upgrading the platform and runtime, clearing out years of unused extensions, moving it to managed hosting, and connecting it to Microsoft Business Central.
BinMaster
BinMaster manufactures level-measurement and inventory-monitoring equipment, the bin level indicators and sensors used across agriculture and industry, and sells through its Magento store. The platform had fallen several versions behind and carried years of accumulated extensions, the kind of store our Adobe Commerce upgrade team is built to modernize.
A working store, several versions behind and weighed down.
So we brought it current.
Platform & PHP upgrade
Adobe Commerce core and the PHP runtime brought up to current, vendor-supported versions.
Extension cleanup
Years of unused, disabled, and abandoned modules audited out to shrink the maintenance surface.
Staging-first process
A faithful staging copy and a defect-priority budget keep the upgrade low-risk and cost-aware.
Managed hosting on Nexcess
A migration onto hosting purpose-built for Adobe Commerce, sequenced with the upgrade.
Business Central integration
Bi-directional sync of customers and orders, with catalog, pricing, and inventory from the ERP.
QA, UAT & hypercare
Full regression testing and post-launch hypercare around a scheduled production cutover.
Engineered,
not assembled.
Modernizing a live store means upgrading, lightening, rehosting, and integrating it, without taking the business offline. So we did it in sequence, on a faithful copy first.
A leaner stack, on solid ground.
The platform, the runtime, the hosting, and the ERP, brought current and connected, with the module footprint trimmed back to what the store actually uses.
PlatformAdobe CommerceThe Magento store, upgraded and current
ERPMicrosoft Business CentralSystem of record, synced both ways
HostingNexcessManaged hosting built for Adobe Commerce
RuntimePHP RuntimeBrought to a current, supported version
AnalyticsGoogle Analytics 4Reporting extension updated and retained
DependenciesComposer StackModule footprint audited and consolidated
Built in phases.
BinMaster wasn't a single switch. It moves from audit and planning, to the platform and runtime upgrade, to a managed-hosting migration, to the ERP integration, each phase sequenced so the live store is never the test bed.
- Phase 01Audit and plan
Inventorying the full extension and customization footprint, flagging what was disabled, unused, or abandoned, and building a staging-first upgrade plan synchronized from production so the live business is never the test bed.
- Phase 02Upgrade the platform
Upgrading the Adobe Commerce core and PHP runtime to current, supported versions on a dedicated branch, retiring dead modules and updating the rest, with full regression QA and UAT before a scheduled production cutover and hypercare.
- Phase 03Move to managed hosting
Migrating the store onto Nexcess, a managed hosting platform built for Adobe Commerce, planned and sequenced alongside the upgrade to avoid a second disruptive cutover.
- Phase 04Connect the ERP
Integrating the store with Microsoft Dynamics 365 Business Central for bi-directional customer and order sync, with products, pricing, inventory, shipments, and invoices driven from the system of record.
Modernized, not rebuilt.
The value wasn't a replatform. It was taking an existing, working store several versions behind, bringing the platform, runtime, and hosting current, trimming the dead weight, and connecting it to the ERP, all without disrupting the business that runs on it.
- Current and supported. Platform, runtime, and hosting all brought onto modern, maintained versions.
- Lighter to maintain. Unused and abandoned modules retired, so every future upgrade is cheaper.
- Connected to operations. Bi-directional Business Central sync keeps the store and the ERP working from one truth.
Current, lean,
and connected.
The work is never the point. This is what the modernization changes for how BinMaster's store runs and how it talks to the rest of the business.
Get this for your storeOn a current, supported platform
The store moved from an aging Adobe Commerce release onto the current, vendor-supported version, with the PHP runtime brought up to match, so it keeps getting security patches and modern performance instead of drifting out of support.
The work. Upgrade, migrate, integrate.
Modernizing a live store is upgrade engineering, codebase cleanup, hosting migration, and ERP integration, sequenced so the business keeps running through every step. This is the platform, infrastructure, and integration work the engagement covers. The result is owned by BinMaster.
PlatformAdobe Commerce Platform Upgrade
What it doesA major upgrade of the Adobe Commerce core, run first on a dedicated upgrade branch in a local environment and then a staging environment synchronized from production, moving the store onto the current, vendor-supported release.
Why it matteredThe store was several versions behind and aging out of support. Getting current restores access to security patches, performance work, and modern tooling.
RuntimePHP Runtime Upgrade
What it doesAn upgrade of the PHP runtime to a current, supported version, with the custom modules and retained extensions brought into compatibility and their issues resolved.
Why it matteredAn out-of-date runtime blocks the platform upgrade and loses security support. Bringing PHP current is the foundation the rest of the upgrade stands on.
CleanupExtension & Module Audit
What it doesA full audit of the installed extension and customization footprint, identifying modules that were disabled, unused, abandoned, or built against an old runtime, and retiring them from the codebase.
Why it matteredEvery dead module is a liability that breaks on upgrade and slows the build. Removing what isn't used makes the platform lighter and every future upgrade cheaper.
MaintenanceThird-Party Extension Updates
What it doesUpdates to the retained third-party extensions so they run on the upgraded platform and runtime, coordinating with the original extension vendors on compatibility where active support was in place.
Why it matteredRetained extensions have to keep working after the core upgrade. Updating them in step, with vendor support where available, avoids surprise breakage at go-live.
ProcessStaging-First Upgrade Workflow
What it doesA low-risk upgrade process: freeze and synchronize staging from production, disable staging cron jobs so no data reaches production, upgrade in isolation, and prioritize defects against an agreed budget so effort goes to customer-impacting issues first.
Why it matteredUpgrading in place risks the live business. Doing it on a faithful staging copy, with a defect-priority budget, keeps the upgrade controlled and cost-aware.
QualityQA, UAT & Hypercare
What it doesFull regression QA across core and third-party functionality, a defect list triaged with the client, user-acceptance testing, and post-launch hypercare around a scheduled production cutover.
Why it matteredA platform upgrade touches everything. Structured QA, UAT, and hypercare catch regressions before customers do and stabilize the days right after go-live.
InfrastructureManaged Hosting Migration
What it doesMigration of the store onto Nexcess, a managed hosting platform built for Magento and Adobe Commerce, planned and sequenced alongside the platform upgrade.
Why it matteredHosting tuned for the platform means better performance, support, and headroom. Migrating during the modernization avoids a second disruptive cutover later.
ERPMicrosoft Business Central Integration
What it doesAn integration connecting the Magento store to Microsoft Dynamics 365 Business Central, the ERP acting as the system of record, with mapped data flows in both directions.
Why it matteredThe store and the ERP were managed separately. Connecting them removes manual re-keying and keeps commerce and operations working from the same data.
ERPCustomer & Order Sync
What it doesBi-directional synchronization of B2B and B2C customer records and sales orders between Magento and Business Central, so accounts and orders stay aligned on both sides.
Why it matteredCustomers and orders live in both systems. Two-way sync means a change in either place is reflected in the other, without staff bridging the gap by hand.
ERPCatalog, Pricing & Inventory Sync
What it doesSynchronization of product information, pricing, inventory, taxation, and shipment and invoice data (including split shipments and invoices) from Business Central into Magento.
Why it matteredThe ERP owns catalog, price, and stock truth. Pushing it into the store keeps what customers see in line with what operations actually has.
Is your store falling behind?
Upgrade, migrate, and integrate. We bring aging Magento and Adobe Commerce stores current, lighten the codebase, move them to hosting built for the platform, and connect them to the ERP, without taking the business offline. Tell us what you're up against.