We brought BinMaster's Adobe Commerce store current.
BinMaster builds level-measurement and inventory-monitoring equipment for agriculture and industry. IWD upgraded its Adobe Commerce platform and PHP runtime to supported versions, cleared out years of unused extensions, moved the store onto managed hosting, and connected it to Microsoft Business Central.
BinMaster
BinMaster manufactures bin level indicators, sensors, and inventory-monitoring equipment for agriculture and industry. The company sells through its Magento store at binmaster.com. The platform had fallen several versions behind and carried years of accumulated extensions. Security patches had stopped arriving, and every change to a working store felt like a risk. It is exactly the kind of store our Adobe Commerce upgrade team is built to modernize.
The store still worked, but it sat several versions behind and carried dead weight.
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.
The store kept selling
while we modernized it.
Upgrading, lightening, rehosting, and integrating a live store without taking the business offline. We did it in sequence, on a faithful copy first.
Every layer of the stack is now current and supported.
Platform, runtime, hosting, and ERP all brought current and connected. The module footprint is 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
The modernization ran in four phases.
BinMaster wasn't a single switch. Audit and planning, then the platform and runtime upgrade, then managed-hosting migration, then ERP integration. Each phase sequenced so the live store is never the test bed.
- Phase 01Audit and plan
Every extension and customization inventoried, dead weight flagged, and a staging-first upgrade plan built from a production copy so the live business is never the test bed.
- Phase 02Upgrade the platform
Adobe Commerce core and PHP runtime brought to current, supported versions. Dead modules retired, the rest updated, with full regression QA and UAT before a scheduled production cutover.
- Phase 03Move to managed hosting
The store migrated onto Nexcess, managed hosting built for Adobe Commerce, sequenced alongside the upgrade to avoid a second disruptive cutover.
- Phase 04Connect the ERP
The store connected to Microsoft Dynamics 365 Business Central for bi-directional customer and order sync, with products, pricing, inventory, shipments, and invoices from the system of record.
We modernized the store instead of rebuilding it.
The value wasn't a replatform. It was taking a working store several versions behind and bringing the platform, runtime, and hosting current. Trimming the dead weight. 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.
The store runs current,
lean, and connected.
This is what the modernization changes for the team that runs BinMaster's store. Starting with what they no longer have to worry about.
Get this for your storeOn a current, supported platform
The store runs on a current, vendor-supported Adobe Commerce release with the PHP runtime to match. Security patches arrive on schedule, and nobody is watching a support clock run out.
The work covers upgrade, migration, and integration.
Every build below is owned by BinMaster. Platform, infrastructure, and integration work, sequenced so the business keeps running through every step.
PlatformAdobe Commerce Platform Upgrade
What it doesThe Adobe Commerce core brought up to the current, vendor-supported release, validated on a staging environment synchronized from production before going live.
Why it matteredThe store was several versions behind and aging out of support. Getting current restores access to security patches, performance improvements, and modern tooling.
RuntimePHP Runtime Upgrade
What it doesThe PHP runtime brought to a current, supported version, with custom modules and retained extensions updated for compatibility.
Why it matteredAn outdated runtime blocks the platform upgrade and loses security support. PHP is the foundation the rest of the upgrade stands on.
CleanupExtension & Module Audit
What it doesA full audit of every installed extension and customization, identifying modules that were disabled, unused, abandoned, or incompatible, and retiring them from the codebase.
Why it matteredEvery dead module is a liability that breaks on upgrade and slows the build. Removing what the store doesn't use makes every future upgrade cheaper.
MaintenanceThird-Party Extension Updates
What it doesRetained third-party extensions updated for the new platform and runtime, coordinating with extension vendors on compatibility where active support existed.
Why it matteredRetained extensions have to keep working after the core upgrade. Updating them in step avoids surprise breakage at go-live.
ProcessStaging-First Upgrade Workflow
What it doesStaging synchronized from production, cron jobs disabled so no data bleeds back, the upgrade validated in isolation, and defects triaged against an agreed budget so effort targets customer-facing issues first.
Why it matteredUpgrading in place risks the live business. 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 triaged defect list, user-acceptance testing, and post-launch hypercare around a scheduled production cutover.
Why it matteredA platform upgrade touches everything. Structured QA and hypercare catch regressions before customers do and stabilize the days after go-live.
InfrastructureManaged Hosting Migration
What it doesThe store migrated onto Nexcess, managed hosting built for Magento and Adobe Commerce, sequenced alongside the platform upgrade.
Why it matteredHosting tuned for the platform means better performance, faster support, and real headroom. Migrating during the modernization avoids a second disruptive cutover later.
ERPMicrosoft Business Central Integration
What it doesThe Magento store connected to Microsoft Dynamics 365 Business Central 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 on the same data.
ERPCustomer & Order Sync
What it doesBi-directional sync of B2B and B2C customer records and sales orders between Magento and Business Central, keeping accounts and orders aligned on both sides.
Why it matteredCustomers and orders live in both systems. Two-way sync means a change in either place shows up in the other, without staff bridging the gap by hand.
ERPCatalog, Pricing & Inventory Sync
What it doesProduct catalog, pricing, inventory, tax rates, shipments, and invoices (including splits) pushed from Business Central into Magento.
Why it matteredThe ERP owns catalog, price, and stock truth. Keeping the store in line with what operations actually has means customers see accurate data.
Is your store falling behind?
Every release you skip widens the security gap and raises the cost of the next upgrade. We bring aging Magento and Adobe Commerce stores current without taking the business offline. Tell us what you're up against.