Why Integrations Blow Up Onboarding Timelines (and How to Keep Go-Live on Track)

Ask any implementation lead what pushed their last go-live date back, and there's a good chance the answer involves an integration. The product itself was ready. The users were trained. But the connection to the customer's CRM, ERP, billing system or data warehouse wasn't.

Integrations are often where onboarding plans meet reality. Here's why they cause so much trouble, and how to stop them from holding your whole launch hostage.

Why integrations are so unpredictable

They depend on people you don't control. An integration usually needs time from the customer's IT team, a third-party vendor or both. Those teams have their own priorities, and your project may not be at the top of the list.

Access takes longer than the work. Credentials, API keys, firewall rules, security reviews and test environments can take longer to arrange than the integration itself.

The data is messier than expected. Fields that "should" match don't. Records are duplicated. Formats differ between systems. These issues often only surface once real data starts flowing.

Scope is fuzzy. "Integrate with our CRM" can mean a simple one-way sync or a complex two-way flow with custom logic. If that isn't clarified early, estimates are guesses.

They're often promised casually. A quick "yes, we integrate with that" during the sales process can turn into a significant project nobody planned for.

The real problem: everything waits for everything

The biggest risk isn't that integrations are hard. It's that many onboarding plans tie go-live to all of them being finished. One slow integration then delays the entire launch, even if the customer could already be getting value from the rest of the product.

Separate what's critical from what's nice to have

The most useful step is simple: sort integrations into two groups.

Day-one-critical integrations. The customer genuinely can't go live without these. For example, if the product is useless without customer records from their CRM, that sync is critical.

Everything else. Integrations that add convenience, automation or reporting, but that the customer can live without for a few weeks. These are valuable, but they shouldn't decide the launch date.

Then take all integrations off the main rollout. Every integration, critical or not, runs on its own parallel track, ideally starting at Discovery alongside the main plan, and each one is scoped and quoted on its own rather than folded into the standard rollout. The difference is what go-live waits for: only the day-one-critical integrations have to be finished before launch. The rest keep moving on their own timeline and can land after go-live.

This one change does a lot. Go-live becomes predictable again, and the customer starts getting value sooner, while the remaining integrations keep moving.

Other ways to keep go-live on track

• Ask about integrations early. Raise them during the sales handoff, not at kickoff. Find out which systems are involved, who owns them, and what was promised.
• Clarify scope in plain language. For each integration, agree what data moves, in which direction, how often, and what "done" looks like.
• Start access requests on day one. Treat credentials, environments and security reviews as tasks with owners and dates, not afterthoughts.
• Test with real data early. A small sample of real records will reveal data issues far sooner than a perfect test set.
• Name an owner on the customer side. Someone with the authority to get IT time and make decisions.
• Plan workarounds. If a non-critical integration is late, a temporary manual process can often bridge the gap.
• Communicate honestly. If something is slipping, tell the customer early, explain the impact and offer options.

Set expectations from the start

Customers are usually fine with integrations arriving in stages, as long as they know that up front. What frustrates them is believing everything will be live on launch day and then discovering otherwise. Make the two tracks visible in the plan from the very first conversation.

From experience

Across 15+ years in implementation and delivery roles at SAP, Ericsson and HP, Alex Bitang worked on projects where connections between systems were central to success. One lesson stood out: launches stayed on track when teams were clear early about which integrations truly had to be ready on day one, and let the rest follow on their own schedule.