Let me say the quiet part out loud: your SAP Business One partner's go-live date is not a forecast. It's a sales tool. I've been on both sides of this table — I've given the optimistic date, and I've inherited the wreckage of someone else's. In fifteen years, I have never seen a B1 project go live on its original date. Not once.
Before the partners reading this get mad: I'm not saying anyone's lying to be malicious. I'm saying the incentives make honesty nearly impossible, and you should plan accordingly.
Why the Date Is Fiction
Reason 1: Discovery finds the org chart, not the work. Every B1 project starts with discovery workshops. The partner maps your processes. What they can't map: the spreadsheet that Linda in accounting has maintained for nine years that does something nobody can explain but everything depends on. Every company has three to five of these shadow systems. They surface in month three of a two-month project, and each one adds two weeks.
I watched a manufacturing client discover — in week 10 of a 12-week project — that their entire outside-processing workflow lived in one planner's head and a whiteboard. Not in any system. Not documented anywhere. Two weeks of workshops just to extract what the whiteboard meant.
Reason 2: Data migration is where estimates go to die. Partners estimate data migration based on record counts. "50,000 items, 20,000 business partners — that's two weeks." But record count isn't the problem. Data QUALITY is the problem. Your item master has 14 variations of the same vendor name. Your customer records have addresses from 2011. Your open A/R includes invoices that were paid but never reconciled.
The rule I give every client: take the partner's data migration estimate and triple it. I've never seen that be wrong in the pessimistic direction. The migration isn't a technical task — it's an archaeological dig through a decade of "we'll clean it up later."
Reason 3: Testing gets crushed. When discovery runs long and migration runs longer, the phase that compresses is user acceptance testing. The partner says "we can do UAT in one week instead of three if everyone's focused." Everyone nods. Then go-live week arrives and the warehouse team discovers the pick-and-pack flow doesn't match how they actually work, because they never tested it. Now you're customizing in production, which is the ERP equivalent of doing surgery on yourself.
How to Plan Around the Fiction
Since the date is fiction, stop planning like it's fact.
Insist on a phased go-live. Financials and purchasing first. Sales and inventory second. Production and MRP third. Each phase is a real go-live with a real date you can actually hit. The psychological difference is enormous: three wins versus one long anxious march toward a moving target. And if phase one slips two weeks, phases two and three are unaffected — unlike a big-bang where everything slips together.
Put data migration first, not last. The conventional project plan does migration near the end, after configuration. This is backwards. Start cleansing data in week one, in parallel with everything else. Data cleanup is the longest pole in the tent and the least dependent on configuration decisions. A client who starts data work on day one finishes on time. A client who starts in month three discovers the tent has no poles.
Define go-live as "core live," not "perfect live." Write down — in the contract — the exact list of processes that must work on day one. Everything else is phase two. The projects that "go live late" are usually projects where the definition of done kept growing. Freeze the scope, ship the core, iterate. Your business survived on the old system this long; it can survive six more weeks for the nice-to-haves.
Add 30% and tell no one. When the partner says 16 weeks, plan internally for 21. Don't tell the partner — they'll just relax into it. Tell your team. The companies that plan for slippage absorb it. The companies that plan for the fiction have a crisis.
The Uncomfortable Truth About Who's Responsible
Here's the part partners won't tell you: most delays are the client's fault, not the partner's. The partner can't migrate data you won't cleanse. They can't configure the process you won't define. They can't test with users you won't free up. Every "the partner is late" story I've investigated had a chapter where the client took three weeks to answer a two-day question.
So the real go-live strategy is internal: assign someone with actual authority to make decisions fast. Not a committee. One person who can say "yes, that's how we do returns" in the meeting instead of "let me check with the team and get back to you" for the eleventh time. Decision latency kills more go-lives than bad software.
The date is a lie. Plan for the truth, and you'll be the rare company that goes live boring — on a Tuesday, without drama, while everyone else is still "two weeks away."
David Strausser, Dead Brands LLC / Quaint Business Solutions
Want help with your ERP? Book a call — I'll tell you what your go-live will actually take before you sign anything.
Deadbrands.co merch: for everyone who's ever been "two weeks from go-live" for six months.
