Skip to content
Notifications
Clear all

Complete newbie here - how long does a typical migration take?

5 Posts
5 Users
0 Reactions
118 Views
(@cloud_cost_fighter)
Honorable Member
Joined: 6 months ago
Posts: 404
Topic starter   [#22464]

The question is like asking "how long is a piece of string?" but I'll try to give you something concrete to hang your hat on.

A "typical" migration from, say, a legacy monitoring tool to Datadog, or from one ticketing system to Jira, can take anywhere from **3 months to 18+ months**. The variance isn't about the data volume; it's about the *process and people*.

Here's what actually eats the calendar:
* **Discovery & Cleanup (25% of time):** You find out your data is a mess. Duplicate users, orphaned records, inconsistent custom fields. You can't migrate garbage, so you spend weeks cleaning it.
* **The "Oh, we also use it for..." (40% of time):** The team using the tool has built five undocumented workflows and three critical reports you knew nothing about. You now have to rebuild those or change processes.
* **Testing & Dry Runs (20% of time):** You run a pilot with a small team. They find 47 edge cases. You fix. Repeat.
* **Actual Cutover Weekend (1% of time):** The final data sync and switch is often the shortest, simplest part.

Real example: We migrated from ServiceNow to Jira Service Management. The sales pitch was "3 months." Reality?
* Data cleanup & mapping: 6 weeks
* Rebuilding approval workflows they "forgot" to mention: 4 weeks
* Testing with pilot group: 3 weeks
* Staging dry-runs and rollback drills: 2 weeks
* Final cutover: 36 hours of a weekend

Total: **~4 months**, and that was considered *fast*.

The single biggest predictor of timeline isn't the tool. It's whether you have a dedicated, full-time project owner with the authority to make decisions. If this is someone's "side project," double whatever estimate you get and add budget for aspirin.


Cloud costs are not destiny.


   
Quote
(@emma78)
Reputable Member
Joined: 4 months ago
Posts: 221
 

That's a really helpful breakdown, the percentages especially. In your ServiceNow to Jira example, was the 6 weeks for cleanup something you could have scoped upfront? Or did you only find the real mess once you started?



   
ReplyQuote
(@infra_architect_6)
Reputable Member
Joined: 6 months ago
Posts: 259
 

That's the crux of it. You can *sort of* scope the data cleanup upfront with a preliminary audit, but the true depth of the mess is often only revealed during the mapping phase. The audit tells you about schema inconsistencies and orphaned records. The real time sink emerges when you try to define transformation rules and realize the business logic embedded in the old data is contradictory or based on fields that were repurposed five years ago and never documented.

In my experience, a better predictor than the initial data audit is the age and governance history of the source system. A five-year-old system with strict change controls might have a clean dataset. A ten-year-old system that's had three different admin teams and allowed free-form text fields for critical workflow data is where you discover those six-week rabbit holes.

So you can quote a cleanup buffer based on system age and perceived governance, but you must treat it as a high-variance estimate, not a fixed scope. The only way to firm it up is to actually start the detailed field-by-field mapping, which itself is a significant time investment.



   
ReplyQuote
(@ericd)
Prominent Member
Joined: 4 months ago
Posts: 776
 

That point about governance history is so true. You can almost feel it in the system, can't you? A tool that's had a steady hand on the admin side tends to migrate with fewer surprises.

But I'd add that the team's morale during that "mapping phase" rabbit hole is its own critical path item. Discovering contradictory logic week after week is draining, and you need to budget for that emotional runway, not just the technical one. People start pushing for cut corners just to be done, which creates its own problems later.

How do you all handle keeping the energy up when the true scope reveals itself?


Keep it civil, keep it real.


   
ReplyQuote
(@hannahc)
Reputable Member
Joined: 4 months ago
Posts: 282
 

> "A 'typical' migration... can take anywhere from **3 months to 18+ months**."

You've hit the nail on the head. That's the exact range I tell people when they're planning budgets and timelines. The problem is, the 3-month scenario is a fantasy unless you're migrating from a pristine system that was implemented with the sole intention of leaving it one day, which is almost never the case.

Your breakdown of what eats the calendar is spot on. I'd add one more huge time sink for sales tool migrations specifically: data *enrichment*. That's when you realize your old CRM only tracked an email address and a company name for leads, but your new fancy system needs lead scores based on industry, company size, and job role. So your 6-week cleanup phase suddenly expands because you're buying append services or trying to scrape that data together manually. It's never just moving data from point A to B, it's about making it usable and valuable in its new home. That part can easily add another 4-6 weeks.


hannah


   
ReplyQuote