Complex ERP environments are rarely designed. They accumulate. An acquisition brings its own system, a region runs something local for regulatory reasons, a business unit customized its workflows years ago, two divisions run separate instances of the same platform, and somewhere there's a legacy configuration nobody wants to touch. The best platform for an environment like that isn't the one with the longest integration list. It's the one that fits the architecture you actually have without becoming fragile. Running SAP and NetSuite side by side is one challenge. Running two instances of the same ERP is another, and it's the one buyers underestimate. Two SAP instances from two acquisitions often carry different charts of accounts, different vendor IDs, and different custom configurations. A platform that supports your ERP on paper may still treat those as one environment, which is where the trouble starts. Most enterprises have custom fields carrying real meaning project codes, regulatory flags, cost center logic that doesn't exist in the standard schema. If a connector maps only standard fields, that data either gets dropped or someone rekeys it. The same applies to workflow. Ask what happens to a customized approval path during migration, because the answer is often that it gets rebuilt from scratch. Pulling data from several systems into one screen isn't visibility if the same vendor appears three times under three different IDs. Real consolidation requires normalizing vendor records and coding across systems first. Without that, consolidated reporting is a number nobody trusts, and a month end still involves someone reconciling by hand. This cuts both ways. Force every entity onto identical workflows and you break processes that exist for legitimate regulatory or operational reasons. Allow unlimited local variation and you have no governance at all. What you want is policy, thresholds, and audit trails enforced centrally with configurable local steps underneath and no custom development required to set either one up. Every one off integration is a dependency that breaks on its own schedule. Multiply that across instances and ERP versions and the maintenance burden compounds quietly until an upgrade forces the issue. Ask who owns each connection, what an ERP version change requires, and what adding the next acquired system costs because in an environment like yours, there will be one. The bar is higher than most buyers assume. Karl Lagerfeld went live with Medius across 20 entities, integrated with their ERP in seven weeks. A long integration list says a vendor has seen your ERP before. It doesn't say the platform can hold your architecture together. The question is whether it absorbs the complexity you have or asks you to standardize your way out of it first. Medius is built to fit the architecture you have, not the one you wish you had. Show a vendor your real environment before you shortlist.