Ask buyers how long their helpdesk migration took and few give a complete start-to-finish timeline. The clearest timing accounts concern whole contact centers rather than a ticket desk: one retailer faced a 90-day deadline after its outsourcer gave notice, and another described a contact-center project that began in one calendar year and finished the next. Neither is a precise, comparable implementation duration. What buyers describe instead is what set the date around the desk. Two things stand out in helpdesk moves. The outsourcer can set the clock: where a third party runs support, its notice period or its contract can decide when the desk has to move. And in several accounts the ticket desk went live while the phone system was still in testing or kept apart, and the AI was still planned or in development, in one plan a year or more out; these are separate milestones, not necessarily parts of one migration. This page draws on helpdesk moves at mid-size and larger companies; moves between ecommerce-native helpdesks are not covered. The companion reads are why brands switch helpdesk platforms and what CS-platform buyers wish they'd known, where the ratings live.
What a helpdesk migration spends its time on
The suite around it sets the order
In these interviews a helpdesk is often moved as part of a larger CRM, ERP or suite change, and the desk's date follows that program. One retailer's service team sat in one vendor's CRM while the company consolidated onto another's: the interface to its sales and customer service team was “today Salesforce and tomorrow will be Microsoft.” Its reason, months on: “Salesforce is expensive, and we're consolidating our costs with Microsoft.” The new desk was under way that spring and, by the autumn, “It just launched, so it's too early to give a satisfaction.” A multi-country retailer bought a suite whose service module is “going to be implemented sometime next year”, after a business case that went “back and forth several times just to make sure that the costs are right.” As with CRM implementations, the most customized system often goes last, and a support system full of warranties and returns is the example there.
Named in this context: Salesforce Service Cloud · Microsoft Dynamics 365 · Genesys
The contract end sets the date
Several moves are timed to the end of the current contract rather than to a build plan. A consumer products brand puts its next helpdesk move at “probably 15 months or so away”, and says its timing is set “as we end our contract with them in spring of 2028.” A national retailer is weighing its desk move inside a wider CRM evaluation over the coming months. The same clock runs the other way after a move: a team that has struggled with its new desk is held to it by a three-year contract; what these contracts cost is on what buyers actually pay for a customer service platform. As with BI tools, the contract sets the window.
Named in this context: Gladly · Salesforce Service Cloud · Oracle
The outsourcer can set the clock
Where a third party runs the agents, its contract can decide when the desk moves. A specialty retailer had 90 days to stand up its own call center when the third party running it gave notice, a story told below. A national retailer weighing a move off its desk says its outsourcer's contract had just renewed: “So we are locked in on those.” A consumer products brand bought its AI agent through its outsourcer's partner rather than through its helpdesk, and was “building for a couple of months now, but we are still a little bit away from actually deploying that bot,” while its desk move waits for the contract end. Three companies describe this, one with a deadline attached, so it is a thing that can happen rather than a measure of how often it does.
Named in this context: Salesforce Service Cloud · Gladly · Oracle
The phone and the AI may follow their own schedules
In several accounts the ticket desk reached go-live while the phone system was still in testing or ran on a separate schedule, and the AI was earlier still: planned, in development or proving hard to add. A regional retail chain switched its desk on while its phone system was still in testing, and expected a year or more of preparation before AI, a story told below. Another retailer plans to bring voice into its desk: “Yes, we want to launch a test early next year.” A team that kept its old phone system beside a new desk says “We're still integrating, so it's early.” And adding a vendor's AI to a desk already live is described as “a lengthy process and update for us.” The two companies that moved desk and phone together were standing up whole contact centers, so none of this shows that phone and AI have to come afterwards. As with ESP migrations, the channels land on their own dates; whether you need an AI agent at all is on do you need an AI chatbot for ecommerce.
Named in this context: Zendesk · NICE · Genesys · Intercom · Five9
A rushed first build creates rework
Several buyers describe problems with how their desk was first configured. One team, built on the vendor's tight timeline, could not properly use its desk for about a year and paid for a reset; that story is on top complaints about helpdesk platforms. A team that inherited its configuration says “making changes is a lot harder than doing the right thing the first time.” A team half a year into a new desk had built custom tooling on top of it to make it work, and is held to it by a three-year contract. These show that correcting an early setup can take real effort, not that it cannot be changed. As with CDPs, live is not the same as usable.
Named in this context: Zendesk · Kustomer · Gladly
The reports come months later
Reporting is the part teams describe getting to last. At a consumer hardware brand, months after the switch, the work had been moving support onto the desk: “It's been very operational so far.” Only then did the team start on the numbers, a story told below. Weak reporting is a standing complaint about these platforms, on top complaints about helpdesk platforms; as with CRM implementations, the dashboards come after go-live.
Named in this context: Kustomer · Zendesk
How long does a helpdesk migration take?
These interviews do not establish a typical duration, and few buyers report a complete timeline for replacing the ticket desk itself. One specialty retailer had 90 days' notice to stand up its own call center when its outsourcer left; the buyer describes the center as running but gives no completed build time. Another company described a contact-center project that began in one year and finished the next, without enough detail to calculate the elapsed time. The rest are milestones against dates: a desk live in the month it was planned, by one account; a desk switched on with the phone system still in testing; and one under way in the spring that had just launched by the autumn. These measure different work to different endpoints, so they should not be combined into a typical range. The longer clocks sit around the desk: a next move timed to a contract end more than a year out, AI planned a year or more after the switch-on, and a desk that took about a year to become properly usable. This page draws on moves at mid-size and larger companies, so it says nothing about how fast moves between ecommerce-native helpdesks go.
Should the phone system and AI move with the helpdesk?
In several accounts they did not move together, though much of the evidence is about plans. One retail chain switched its desk on with the phone system still in testing and expected a year or more of preparation before AI; another plans to bring voice into its desk as a test the following year; another describes adding its vendor's AI to a live desk as a lengthy process; and one kept its old phone system beside a new desk. The two companies that did desk and phone together were standing up whole contact centers. This rests on eight companies, half of them describing plans rather than finished work, so it shows these projects can run on separate schedules, not that phone and AI have to come after the desk.
When is a helpdesk migration finished?
Not necessarily at ticket-desk go-live. Depending on the scope, the reports the team relies on, the phone integration and any AI can still be unfinished at that point, or be run as separate projects, and in these interviews they came at different times. One consumer hardware brand's team was only starting on its reports months after switching, a story told below. One team built on a tight timeline could not properly use its desk for about a year, a story told on top complaints about helpdesk platforms. Where phone and AI work was planned, it came after the desk or was still to come; a company that does not plan to add AI has not left its migration unfinished for that reason.
Do helpdesk migrations stay on schedule?
These interviews give too few plan-versus-outcome comparisons to answer. One desk went live in the month it was planned by one account, though a later interview with the same person dates it later; one call center was stood up against a 90-day notice, with no finish date given; one desk went live on the vendor's timeline but took about a year to become usable; and one company's support move was pushed back a year inside a wider move off its CRM. Two of those comparisons are qualified, and four cases cannot show how often helpdesk migrations finish early, on time or late.
Want a review of your own stack?
Get my review →The stories behind the timelines
The counter-current: the moves that went quickly
The quick ones here share a shape: a single desk, a hard date, or a program owner driving it. A specialty retailer running its own call center after an outsourcer's 90-day notice, though no completion date was given; a desk live in its planned month by one account; and one launched within about half a year of being under way. None was a whole migration with the phone and the AI included, and none establishes a helpdesk move finishing early against its plan. They say nothing about which vendor is faster, and moves between ecommerce-native helpdesks are not covered here, so none of this says helpdesk moves are fast or slow in general.
What this means for your helpdesk plan
In these interviews the length of a helpdesk migration is set by the program around the desk — the suite, the contract, the outsourcer — and by the phone, AI and reporting work that comes after it, more than by the desk itself. Our recommendations, not practices buyers describe: if an outsourcer runs your agents, put its notice period and contract dates on the migration plan; if the CRM or ERP is moving too, decide where support sits in that sequence and date the desk from it; date the phone cutover and the AI launch, where they are in scope, as their own milestones rather than as part of the desk go-live; and define and test the essential ticket workflows, integrations, permissions and reports before go-live while leaving room to improve the setup after launch, since correcting a rushed one proved costly in these accounts. For why teams move or stay, see why brands switch helpdesk platforms.
Common questions
How long does a helpdesk migration take?
These interviews do not establish a typical duration, and few buyers give a complete start-to-finish timeline. The clearest timing accounts concern whole contact centers, and neither is a measured build: one specialty retailer faced a 90-day deadline to stand up its own call center when the third party running it gave notice, with no completion date given, and another company's contact center began in one calendar year and finished the next. Desk go-lives are described against dates and programs rather than in months: one went live in the month it planned, by one account, and another, under way in the spring, had just launched by the autumn.
What sets the date of a helpdesk migration?
Buyers point to the program around the desk more than the desk itself: a CRM, ERP or suite consolidation that decides when support moves, a contract end, and for some companies the outsourcer that runs the agents. Too few buyers compared the outcome with a plan to say how often helpdesk migrations slip.
Should the phone system and AI move with the helpdesk?
In several accounts they did not move together. The ticket desk went live while the phone system was still in testing or kept separate, and the AI was still planned or in development: one retail chain switched on its desk with its phone system in testing and expected a year or more of preparation before AI. That shows separate schedules, not a required order. The two companies that did desk and phone together were standing up whole contact centers. Dating the phone cutover and the AI launch as their own milestones is our recommendation, not a practice buyers describe.
When is a helpdesk migration finished?
Not necessarily at go-live. Depending on the scope, reporting, the phone integration and any AI can still be unfinished at ticket-desk go-live, or be run as separate projects: one team was only starting on its reports months after switching, and another, built on a tight timeline, took about a year to become properly usable. A company that does not plan AI has not left its migration unfinished for that reason. Testing the essential workflows and reports before cutover is our recommendation, not a practice buyers describe.
Does an outsourced support team change the timeline?
It can. One specialty retailer had 90 days to bring its call center in-house onto its helpdesk when the third party running it gave notice, and another retailer's outsourcer contract had just renewed, locking in the rest of its support stack while it weighed a move. Putting the outsourcer's notice period and contract dates on the migration plan is our recommendation, not a practice buyers describe.
A tech stack review, powered by the buyers who've been there
What matters most to you, a shortlist for your stack, and the next steps to take — built from hundreds of verified buyer interviews.
Get my stack reviewFree · no password · your answers are anonymized before they inform research like this.