The Myth of the BIP - Part 2
January 17, 2021
The Myth of the Big Important Partner - Part 2

If you are in the middle of a struggling ERP implementation you may recognize the symptoms of the Big Important Partner Myth and how it is affecting your project.
If you are in the process of changing or selecting a partner for a new ERP implementation then an understanding of the partner related ERP project issues may save you time and money.
And maybe an ulcer, job or company.
Having worked in a wide variety of business models in the ERP implementation world for over thirty years my observations are grounded in actual experience along with the corresponding battle scars and lots of great stories, from the sleepy consultant to the “fairy dust” project plan.It turns out that I learned several critical ERP implementation lessons on my first job fresh out of college, I was just not smart enough at the time to understand them.
First and foremost is the “nobody ever got fired for hiring IBM” thinking of ERP implementations. In the “olden days” it was taken as gospel that many IT projects would go to an IBM solution because they were considered the gold standard in the industry. Therefore, by selecting IBM, decision makers sought to insulate themselves and their paychecks against potential criticism by making the “safe choice”.
Today you see companies hiring ERP implementation partners for the same reason. Big Important Partners give them the sense of comfort that they are in good hands.
If you are in the process of changing or selecting a partner for a new ERP implementation then an understanding of the partner related ERP project issues may save you time and money.
And maybe an ulcer, job or company.
Having worked in a wide variety of business models in the ERP implementation world for over thirty years my observations are grounded in actual experience along with the corresponding battle scars and lots of great stories, from the sleepy consultant to the “fairy dust” project plan.It turns out that I learned several critical ERP implementation lessons on my first job fresh out of college, I was just not smart enough at the time to understand them.
First and foremost is the “nobody ever got fired for hiring IBM” thinking of ERP implementations. In the “olden days” it was taken as gospel that many IT projects would go to an IBM solution because they were considered the gold standard in the industry. Therefore, by selecting IBM, decision makers sought to insulate themselves and their paychecks against potential criticism by making the “safe choice”.
Today you see companies hiring ERP implementation partners for the same reason. Big Important Partners give them the sense of comfort that they are in good hands.

I started my career working for a big partner, a real big partner: PriceWaterhouse. At the time Price Waterhouse was not yet PWC and part of the admired “Big Eight” group of accounting firms.Interestingly, a saying I was soon to learn was that in the Big Eightthe “good leave, the bad leave and the mediocre prosper”.
The other lesson I learned was that while experienced partners and senior managers sold projects on the promise of size, references and an endless experienced resources pool. I was being sent out as a seasoned consulting resource with only the briefest opportunity to get up to speed on software that I had never seen before.
In the ERP space, I have seen this play out over and over on failed or mediocre ERP implementations that are over budget, over time and not delivering on promised functionality.
Having been exposed to multiple business models in the industry I have come to see that there are fundamental issues and drivers behind the behavior of the Big Important partner firms that put them fundamentally at odds with their customer base and will forever hamper their ability to deliver excellent projects.
These include:
Over the next few posts we will look at this one issue at a time.
The other lesson I learned was that while experienced partners and senior managers sold projects on the promise of size, references and an endless experienced resources pool. I was being sent out as a seasoned consulting resource with only the briefest opportunity to get up to speed on software that I had never seen before.
In the ERP space, I have seen this play out over and over on failed or mediocre ERP implementations that are over budget, over time and not delivering on promised functionality.
Having been exposed to multiple business models in the industry I have come to see that there are fundamental issues and drivers behind the behavior of the Big Important partner firms that put them fundamentally at odds with their customer base and will forever hamper their ability to deliver excellent projects.
These include:
- Net new pressure
- Overhead and Scarce Resources
- Resource baiting and switching
- Mergers and Acquisitions and VC money
Over the next few posts we will look at this one issue at a time.
HandsFree ERP is dedicated to supporting clients with their ERP initiatives, enabling companies to seamlessly connect users with their ERP partners. By utilizing skilled professionals, streamlined processes, and cutting-edge tools, HandsFree ERP significantly boosts the success rates of ERP projects.

By Peter Joeckel
•
September 11, 2025
Most organizations think data migration is about moving records from A to B. They're wrong. It's about transforming business information into operational truth. Get it wrong, and you're just digitizing your problems at enterprise scale. If you’re a distributor or manufacturer, your business runs on inventory. Simple as that. Everything else, sales, purchasing, operations, revolves around making sure your inventory data is accurate. And yet, so many companies struggle with messy, outdated, or outright incorrect data, setting themselves up for major headaches when it comes time to implement or upgrade an ERP system. For manufacturers and distributors, inventory is the heart of the business. Everything revolves around managing it effectively. In ERP terms, this involves three core processes: 1. Procure-to-Pay – Bringing inventory in from suppliers. 2. Manufacturing or Handling – Transforming or repackaging inventory. 3. Order-to-Cash – Shipping inventory out to customers. At the heart of the problem are three core data sets: customers, suppliers, and inventory . Clean and accurate data here isn’t optional. It’s essential. Let me paint you a picture of what poor data quality really costs: - Financial processes failing because customer master data is inconsistent - Supply chain grinding to a halt because item masters don't match across systems - Month-end closing taking weeks because nobody trusts the numbers - Compliance risks because audit trails are incomplete or incorrect I've seen implementations declare success after migrating millions of records, only to discover they've built a perfect system running on garbage data. The result? Unreliable reporting, broken processes, and users creating shadow systems to track "real" data. Here's what your implementation partner isn't telling you: Data quality issues compound over time. Every day you operate with poor data, you're creating new problems that will need to be fixed later. It's like trying to build a skyscraper on quicksand - no matter how perfect your architecture, IT IS GOING TO SINK. The hard truth: No amount of system optimization can fix bad data. You're either managing data quality now, or you're managing data problems forever. And in D365 F&O, forever gets expensive very quickly. Bills of Materials: The Science That Trips Everyone Up For manufacturers, one of the biggest trouble spots is the Bill of Materials (BOM) . Think of the BOM as a recipe: it defines exactly how components come together to make a finished product, like a “little red wagon.” Each part must be accounted for, structured correctly, and contain only inventory items. Here’s where things go wrong: Many BOMs have too many levels or include non-inventory items like labor and overhead. Legacy systems often force companies to create Frankenstein part numbers that are confusing and error-prone. Process manufacturers with “recipes” face additional complexity because ingredient quality can fluctuate, affecting output consistency. Moving this messy data into a modern ERP without cleaning it first can turn your new system into a nightmare rather than an improvement. Routing: Where Art Meets Science Beyond the BOM, there’s routing , the step-by-step instructions for manufacturing a product. Routing data is critical for understanding capacity, scheduling, and cost management. Capturing work center setup times, labor, material, and overhead costs is key. Most companies simply don’t have this data organized, which means ERP projects often start off on the wrong foot. Planning Ahead: The Key to ERP Success Waiting until the ERP project is live to clean and organize your data is a recipe for disaster. By then, your best engineers and data experts are fully occupied, leaving little time to fix deep-rooted issues. Forward-thinking manufacturers and distributors start data workshops well before the ERP implementation . These workshops: Identify issues in customer, supplier, and inventory data Clean and structure BOMs and routings properly Establish proper part numbering and chart of accounts setups Doing this ahead of time dramatically increases the chances of a smooth, successful ERP deployment—regardless of which system you choose. Bottom line: messy data doesn’t just slow you down, it can completely derail your ERP implementation. Start early, clean it up, and structure it correctly. Your future self (and your new ERP system) will thank you.