--- title: Outsourced Service Desk Migration | A UK Playbook description: "How UK companies move an outsourced IT service desk to a dedicated offshore team: baseline, contract exit, TUPE, knowledge transfer and phased cutover." image: https://blog.potentiam.co.uk/hubfs/blog/images/service-desk-migration-planning-hero.webp --- [![footer-logo](https://blog.potentiam.co.uk/hubfs/footer-logo.svg "footer-logo")](https://potentiam.co.uk) - [Solutions](https://www.potentiam.co.uk/solutions) [![Technology icon](https://blog.potentiam.co.uk/hubfs/Images/Icons/Technology%20icon.svg) Technology Scale your team with a dedicated advisor who aligns architecture and performance 
to your goals.](https://www.potentiam.co.uk/solutions/technology) [![Finance and Accounting icon](https://blog.potentiam.co.uk/hubfs/Images/Icons/Finance%20and%20Accounting%20icon.svg) Finance and Accounting Finance specialists build offshore teams using the right processes and skills to strengthen accounting and deliver results.](https://www.potentiam.co.uk/solutions/finance-accounting) [![Marketing and Creative](https://blog.potentiam.co.uk/hubfs/Images/Icons/Marketing%20and%20Creative.svg) Marketing & Creative Marketing advisors build offshore teams that close capability gaps and integrate seamlessly with local operations.](https://www.potentiam.co.uk/solutions/marketing-and-design) [![Data Analytics icon](https://blog.potentiam.co.uk/hubfs/Images/Icons/Data%20Analytics%20icon.svg) Data Analytics Analytics experts design scalable offshore data teams that deliver actionable insights and business value.](https://www.potentiam.co.uk/solutions/data-analytics) [![Sales and Customer Success icon](https://blog.potentiam.co.uk/hubfs/Images/Icons/Sales%20and%20Customer%20Success%20icon.svg) Sales & Customer Success Specialists build offshore sales and customer success teams aligned for growth and strong client relationships.](https://www.potentiam.co.uk/solutions/sales-customer-service-solutions) [![Engineering and Construction icon](https://blog.potentiam.co.uk/hubfs/Images/Icons/Engineering%20and%20Construction%20icon.svg) Energy Consulting Solutions Scale engineering and construction projects with offshore teams that improve control, efficiency, and on-time delivery.](https://www.potentiam.co.uk/solutions/energy-consulting) - Locations [![menu-icon](https://blog.potentiam.co.uk/hubfs/Images/Icons/menu-icon.svg) Cape Town, South Africa English-speaking teams with seamless UK collaboration](https://www.potentiam.co.uk/locations/south-africa) [![menu-icon](https://blog.potentiam.co.uk/hubfs/Images/Icons/menu-icon.svg) Bengaluru, India Technology and data capability with EU and UK time-zone overlap](https://www.potentiam.co.uk/locations/india) [![menu-icon](https://blog.potentiam.co.uk/hubfs/Images/Icons/menu-icon.svg) Iași, Romania Multilingual EU talent aligned with European markets](https://www.potentiam.co.uk/locations/romania) [![menu-icon](https://blog.potentiam.co.uk/hubfs/Images/Icons/menu-icon.svg) Johannesburg, South Africa English-speaking talent with UK time-zone alignment](https://www.potentiam.co.uk/locations/johannesburg) [![menu-icon](https://blog.potentiam.co.uk/hubfs/Images/Icons/menu-icon.svg) São Paulo, Brazil Latin American talent with US and EU time-zone overlap](https://www.potentiam.co.uk/locations/brazil) - [Careers](https://www.potentiam.co.uk/careers) - [About](https://www.potentiam.co.uk/about-us) - Resources [![Blog](https://blog.potentiam.co.uk/hubfs/Blog.svg) Blogs Explore strategies and insights on building high-performing offshore teams, scaling global operations, and unlocking performance growth.](https://blog.potentiam.co.uk) [![case guides](https://blog.potentiam.co.uk/hubfs/case%20guides.svg) Guides Explore essential offshoring strategies for IT managed service providers with our comprehensive guides tailored for COOs and CEOs.](https://www.potentiam.co.uk/guides) [![webinar](https://blog.potentiam.co.uk/hubfs/webinar.svg) Webinars Watch Potentiam’s webinars to discover how offshore teams can accelerate growth, cut costs, and boost performance.](https://www.potentiam.co.uk/webinars) [![case studies](https://blog.potentiam.co.uk/hubfs/case%20studies.svg) Case Studies Explore case studies showcasing how companies in various industries are enhancing efficiency and growth through innovative strategies and specialised services.](https://casestudies.potentiam.co.uk) - [Contact](https://www.potentiam.co.uk/contact-us) - [Book a meeting](https://www.potentiam.co.uk/contact-us) Back to Articles ![An IT service delivery manager and a colleague reviewing a service desk transition plan on a tablet, with an open-plan support floor behind them](https://blog.potentiam.co.uk/hubfs/blog/images/service-desk-migration-planning-hero.webp) Scroll Back to Articles [Blog](https://blog.potentiam.co.uk/tag/blog) | 12 August 2026 # Migrating an Outsourced Service Desk to an Embedded Offshore Team [Potentiam](https://blog.potentiam.co.uk/author/potentiam) Migrating an outsourced IT service desk to an embedded offshore team means ending or reducing a third-party managed service contract and rebuilding the same capability as a dedicated, office-based team that you direct yourself, usually in a lower-cost location. Done properly it is a phased transition over several months. The two things that determine whether it works are the baseline you capture before you start, and how seriously you treat knowledge transfer. This is a playbook for UK companies and MSPs that already outsource their service desk and have concluded the arrangement is not working. It assumes you are not returning the function to expensive UK headcount, and that you want to keep the cost position while taking back control. Key takeaway The step most worth protecting is the baseline. Without a pre-migration baseline you cannot prove improvement, you cannot hold anyone to account, and you will not spot degradation until users complain. Capture the baseline before you serve notice. ## Why companies leave an outsourced service desk The decision to move rarely comes from a single failure. It builds up over a contract term, and the pattern is consistent enough to be recognisable. **Shared agents rather than dedicated ones.** Multi-tenant service desks are efficient for the provider precisely because agents work across several clients. That efficiency is what makes the price attractive. It is also why the agent handling your ticket may know very little about your environment, and why the person who solved the same problem last month is now on a different account. **Attrition inside the provider.** Contact centre and service desk roles carry high turnover across the industry. When your desk sits inside a provider, that churn is invisible to you until it shows up as declining resolution quality. You do not choose the replacements, you are not told when experienced people leave, and each departure takes undocumented knowledge with it. **Change requests become the commercial relationship.** Anything outside the original statement of work is a variation, and variations are priced. Teams learn to stop asking. The desk gradually stops adapting to how the business actually works, and the gap between what you need and what you contracted for widens every quarter. **Institutional knowledge ends up in the wrong place.** Runbooks, known error records, workarounds and the informal understanding of who to call are all built inside the provider's systems and people. That knowledge is an asset your business paid for. Whether you can actually take it with you depends entirely on what your contract says, which is why the contract review comes early in this playbook. **SLAs that are met while the service gets worse.** Response-time targets are easy to hit and easy to game. A ticket can be acknowledged within minutes, bounced between tiers for a week and closed without the user's problem being solved, and the contract will show green. If your SLA reporting looks healthy while your users are unhappy, you are measuring the wrong things. None of this makes outsourcing wrong. Traditional outsourcing genuinely suits stable, high-volume, well-documented processes where you want someone else to own the outcome. We set out where each model fits in our comparison of [BPO versus an embedded offshore team](https://blog.potentiam.co.uk/bpo-vs-embedded-offshore-team). The problem arises when a process that needs contextual judgement and institutional memory has been handed to a structure designed for neither. ![Service delivery manager and colleague reviewing service desk performance metrics on a wall-mounted dashboard](https://blog.potentiam.co.uk/hs-fs/hubfs/blog/images/service-desk-migration-baseline-body.webp?width=1200&height=675&name=service-desk-migration-baseline-body.webp) ## Step one: baseline your current desk before you do anything else This is the step most easily skipped, and without it a migration cannot be defended afterwards. A word on industry benchmarks. You will find plenty of published figures for cost per ticket, first contact resolution and mean time to resolve. Treat them carefully. The genuinely rigorous benchmarking datasets, such as those produced by MetricNet, are commercial products, and their full figures are not freely available. A great deal of what circulates freely online as an industry benchmark traces back to vendor marketing rather than to research, and often carries no stated sample or methodology. Comparing your desk against an unverifiable average tells you very little. Your own historical performance is a far better yardstick. Establish your rights to access and export the ticket data first, because the contract may not give you them. Capture at least three months, and ideally twelve, of the following before you serve notice. | Measure | Why it matters in a migration | | --- | --- | | **Ticket volume and mix** | Determines how many people you need and at what skill level. Splitting by category, priority and requester group tells you which queues can move first. | | **First contact resolution** | The clearest early indicator of gaps in knowledge transfer. If FCR drops after cutover, check ticket mix, access and routing first; if those have not changed, the new team probably does not yet know what the old one knew. | | **Mean time to resolve** | Measure by priority band rather than as a single average. A blended figure hides the degradation that users actually feel. | | **Escalation rate** | Rising escalations after cutover are an early warning that tier one may be out of its depth, once access and routing problems are ruled out. | | **Reopen rate** | Can reveal tickets closed to hit a target rather than because the problem was solved. | | **Cost per ticket** | Your true baseline cost, including internal management time spent on the provider relationship. That time is real and routinely omitted. | | **User satisfaction** | Run your own survey before you move. Provider-reported satisfaction is measured by the party being judged. | Extract this data yourself, from your own ITSM tooling where you can. If the only route to it is a report the provider generates, request it well before you give any indication that you are considering leaving. ## Step two: read the contract properly Three provisions determine how difficult your exit will be, and they are worth finding before you build a plan around assumptions. **Notice and termination.** Establish your notice period, whether you can terminate for convenience or only for cause, and whether there is an early termination charge. Managed service contracts commonly run to multi-year terms with substantial notice, so the calendar may drive your plan more than anything else. **Exit management and transition-out obligations.** A well-drafted contract obliges the provider to co-operate with an orderly handover: supplying data, documenting processes, and supporting a successor for a defined period. A poorly drafted one leaves you dependent on goodwill from a supplier who has just lost your account. Find out which you have before you serve notice, because your bargaining position is strongest beforehand. **Data and intellectual property.** Who owns the knowledge base articles, the runbooks, the ticket history and the configuration data? If ownership sits with the provider, or the contract is silent, you may be entitled to far less than you assume. Ticket history in particular is valuable: it is the record of how your environment actually behaves. Where TUPE may apply The Transfer of Undertakings (Protection of Employment) Regulations 2006 can apply when a service provider changes, not only when a business is sold. [Acas](https://www.acas.org.uk/tupe-transfers) confirms that transfers can include both business transfers and service provider changes, which means employees currently delivering your desk may in principle have rights on a change of provider. Where the work moves offshore, the position is more specific than it first appears. The service provision change rules ask whether, immediately before the change, an organised grouping of employees situated in Great Britain was doing the work. If your current provider runs your desk from outside Great Britain, that limb will often not apply; if the desk is staffed in Great Britain, it may apply even though the work is moving offshore. A business transfer analysis can work differently, and [government guidance](https://www.gov.uk/transfers-takeovers/employees-working-abroad) notes that employees of a UK business based outside the UK may still be protected in a business transfer. The facts decide it, so take employment law advice early rather than assuming either outcome. ![Two IT support analysts working side by side during a knowledge transfer shadowing session](https://blog.potentiam.co.uk/hs-fs/hubfs/blog/images/service-desk-knowledge-transfer-body.webp?width=1200&height=675&name=service-desk-knowledge-transfer-body.webp) ## Step three: treat knowledge transfer as the main risk Every service desk runs on a large body of undocumented knowledge. Which application breaks after a particular update. Which supplier actually answers the phone. Which director should never be left waiting. None of this is in the knowledge base, and none of it transfers by itself. A structured transfer has three stages, and compressing them is where migrations go wrong. **Documentation and extraction.** Pull the knowledge base, runbooks and known error records into your own systems. Then audit them honestly against real ticket history, because documentation that has not been maintained is worse than none: it produces confident wrong answers. **Shadowing.** Your incoming team observes the current desk handling live tickets. This is where the undocumented context surfaces, and it needs long enough to cover the monthly and quarterly cycles rather than a fortnight of routine traffic. **Reverse shadowing.** Your incoming team handles the tickets while the experienced team observes and corrects. This is the stage most easily cut when the timetable slips, and cutting it leaves first contact resolution exposed after cutover. Build the transfer plan around ticket complexity rather than a flat calendar. Password resets and access requests transfer in days. Anything touching a bespoke application, an integration or a regulated process takes considerably longer, and those are the tickets that damage your reputation internally when they are handled badly. ## Step four: phase the cutover A single-date switch concentrates all your risk on one morning. Phasing spreads it and gives you a route back if something breaks. A realistic sequence for a mid-sized desk looks like this. | Phase | Indicative duration | What happens | | --- | --- | --- | | **Discovery and baseline** | 4 to 6 weeks | Capture metrics, review the contract, map ticket categories, decide the target operating model and location. | | **Build the team** | Varies by hub and client | Recruit (we typically take four to six weeks from starting the search to the candidate accepting the offer, four to eight in São Paulo), then onboard and set up the office, tooling and access. Runs in parallel with the notice period; candidates' own notice periods can push start dates later. | | **Knowledge transfer** | 4 to 8 weeks | Documentation, shadowing and reverse shadowing, sequenced by ticket complexity. | | **Pilot queue** | 2 to 4 weeks | The new team takes one contained category end to end. Measure against baseline before widening. | | **Dual running** | 4 to 8 weeks | Both desks live, volume shifting progressively by category or shift. Your safety net. | | **Full cutover** | 1 to 2 weeks | Remaining volume transfers. Provider access revoked on a planned schedule. | Dual running costs money, because you are paying twice for a period. Put that cost in the business case from the beginning. A migration presented without it will look cheaper than it is, and the gap will surface at exactly the wrong moment. ## Step five: work the risk register | Risk | Mitigation | | --- | --- | | **Provider disengages after notice** | Extract data and documentation before serving notice. Use any retention or exit-payment mechanism your contract already gives you, or agree one as a variation, and take legal advice before withholding any payment. | | **Service dips during cutover** | Expect a dip and plan for it. Publish the transition to users, set expectations, and keep dual running until the pilot metrics hold. | | **Access and identity gaps** | Provision the new team fully before revoking anything. Run a joiners and leavers schedule for the transition itself, and audit it afterwards. | | **Out-of-hours cover lapses** | Transfer in-hours volume first. Move out-of-hours and major incident cover last, once the team has proven itself in daylight. | | **Key person dependency returns** | Document as you go rather than afterwards. If one analyst becomes indispensable, you have rebuilt the problem you left. | ## Data protection: the detail most comparisons get wrong Where your team sits has direct consequences under UK data protection law, and this is worth getting right early because it can influence the location decision itself. Giving an overseas organisation access to personal information you hold counts as a transfer, even if no data leaves your systems. The [Information Commissioner's Office](https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/international-transfers/a-brief-guide-to-international-transfers/) uses exactly this scenario as its worked example: a UK business that allows an organisation in India to access personal information on its systems to support customer services is making a restricted transfer. Every restricted transfer must be covered by UK adequacy regulations, appropriate safeguards, or an exception. | Location | UK adequacy position | What that means in practice | | --- | --- | --- | | **Romania** | Covered, as an EEA member state | No IDTA or transfer risk assessment needed. Your processing contract and other UK GDPR duties still apply. | | **South Africa** | No UK adequacy regulations | Restricted transfer. Requires an appropriate safeguard, such as the International Data Transfer Agreement or the EU standard contractual clauses with the UK Addendum, plus a transfer risk assessment. | | **India** | No UK adequacy regulations | Restricted transfer. Same requirement: an appropriate safeguard and a transfer risk assessment. | | **Brazil** | No UK adequacy regulations | Restricted transfer. Same requirement. The EU's adequacy decision for Brazil does not cover transfers from the UK. | South Africa, India and Brazil remain open, but the transfer work needs owning: it belongs in the plan rather than being discovered late, and it is worth taking advice on your own data flows. Note also that you carry this obligation whether the team is yours or a provider's. Outsourcing does not transfer it away. ## Choosing where the team sits For a UK service desk, time zone tends to matter more than raw salary differential, because a desk that cannot answer at 09:00 is not really your desk. **South Africa** suits UK-hours service desk work particularly well. Cape Town and Johannesburg are one hour ahead of the UK in summer and two in winter, so a 9 to 6 day there runs from 8am to 5pm UK time in summer and 7am to 4pm in winter; for UK evening cover, São Paulo is the better fit. There is a deep pool of English-speaking talent familiar with the UK market, and the country has an established base of UK-facing service operations. For a desk whose users are in the UK and expect a live answer during business hours, this alignment is the deciding factor. **Bengaluru** offers the deepest technical talent pool of our hubs and a strong cost position. It is 4.5 hours ahead in summer and 5.5 in winter, so its standard day runs from 4.30am to 1.30pm UK time in summer and 3.30am to 12.30pm in winter, and the time difference becomes an advantage where you need overnight or follow-the-sun cover on agreed shifts. Covering the whole UK working day from Bengaluru means late shifts there, around 1.30pm to 10.30pm local time in UK summer and 2.30pm to 11.30pm in winter, and overnight UK cover means night shifts. Be realistic about the human cost of permanent late or night rotas: they are hard to sustain, and attrition is the very problem you are trying to solve. **Iași in Romania**, two hours ahead all year (7am to 4pm UK time), makes most sense where you serve EU users as well as UK ones, need European language coverage, or where the adequacy position materially simplifies a compliance-heavy environment. **São Paulo**, four hours behind in summer and three in winter (1pm to 10pm and 12pm to 9pm UK time), covers your evening and any users in the Americas. A multi-hub approach is worth considering rather than treating this as one choice. In-hours cover from a time-aligned hub with overnight cover elsewhere is a common and sensible pattern, and it removes the single-location dependency that makes some boards uncomfortable. For a hub-by-hub comparison, read our guide to the [best offshore location for a technology or MSP team](https://blog.potentiam.co.uk/best-offshore-location-technology-msp-team), and for the wider options, our guide to [offshoring, nearshoring and onshoring](https://blog.potentiam.co.uk/offshoring-vs-nearshoring-uk-guide). ## What good looks like ninety days after cutover Set the success criteria before you start, and judge against your own baseline rather than an external average. By ninety days, first contact resolution should be at or above your pre-migration baseline. Mean time to resolve should be back to baseline by priority band. Escalation and reopen rates should be stable or improving. User satisfaction, measured by your survey rather than a supplier's, should be at least level. And the team should be adding knowledge base articles rather than only consuming them, which is the clearest sign that institutional memory is now accumulating inside your business instead of someone else's. Plan for a dip in the first weeks after cutover as a risk, and if there is none, confirm independently that the volume has actually moved. What matters is the shape of the recovery, and whether it is trending back to baseline by the end of the first quarter. ## Where Potentiam fits We build and operate embedded offshore teams for UK and European companies across five hubs in four countries: Cape Town and Johannesburg in South Africa, Iași in Romania, Bengaluru in India and São Paulo in Brazil. For service desk and ITSM work we provide the office, the local management, the recruitment and HR support, while you keep ownership of priorities, processes and quality standards. The team works to your standards inside your tooling, and the institutional knowledge accumulates in your business. If you are weighing up a migration, the most useful first step is the baseline. You can do that work yourself with the table above, and you should do it whether or not you end up moving. For how the operating model works once the transition is complete, read our guide to [offshore service desk teams](https://blog.potentiam.co.uk/offshore-service-desk-teams-for-msps), and for the wider approach, the [embedded offshore team model](https://blog.potentiam.co.uk/embedded-offshore-team-model). ## Frequently asked questions **How long does it take to migrate an outsourced service desk to an offshore team?** It depends on your contractual notice period, which often sets the pace, and on how far the phases overlap. Using our indicative durations, discovery and baselining take four to six weeks, knowledge transfer four to eight weeks, and the pilot, dual running and final cutover a further seven to fourteen. Building the team takes a time that varies by hub and client: hiring typically takes four to six weeks from starting the search to the candidate accepting the offer (four to eight in São Paulo), before notice periods and onboarding. Team build usually runs alongside discovery and the notice period, and knowledge transfer starts as the first hires arrive, so the total is shorter than the sum of the phases. **Does TUPE apply when moving a service desk offshore?** TUPE covers service provision changes as well as business transfers, so bringing a service back in house or moving it between providers can trigger it. That route turns on whether, immediately before the change, an organised grouping of employees in Great Britain was doing the work: a desk your provider already runs from abroad often falls outside it, while a desk staffed in Great Britain may not, even if the work is moving offshore. A business transfer analysis can differ. This turns on the facts, so take employment law advice before committing to a timetable. **Who owns the knowledge base and ticket history in an outsourced service desk?** It depends entirely on your contract. Some agreements give the client full ownership of documentation and ticket data; others leave ownership with the provider or say nothing at all. Establish this before serving notice, because your ability to insist is greatest while the relationship is still live. **Do I need extra data protection measures for an offshore service desk?** If the team is outside the UK and is a separate legal entity, giving them access to personal information is a restricted transfer under UK GDPR, even if the data never leaves your systems. Romania is covered by UK adequacy as an EEA member state, which removes the need for an IDTA or transfer risk assessment but not your other UK GDPR duties. South Africa, India and Brazil are not, so transfers there need an appropriate safeguard such as the International Data Transfer Agreement or the EU standard contractual clauses with the UK Addendum, together with a transfer risk assessment. This applies equally to an outsourced provider. Take advice on your own data flows. **Will service quality drop during the transition?** Plan for a dip in the first weeks. The way to contain it is to phase the cutover, run both desks in parallel while volume shifts, start with a contained pilot queue, and move out-of-hours cover last. Judge recovery against your own pre-migration baseline, which is why capturing that baseline first matters so much. **Which location is best for a UK service desk?** For UK business-hours cover, South Africa aligns most closely: one hour ahead of the UK in summer and two in winter, a 9 to 6 day in Cape Town or Johannesburg runs from 8am to 5pm UK time in summer and 7am to 4pm in winter, with a deep pool of English-speaking talent. Bengaluru suits overnight and follow-the-sun cover on agreed shifts and offers the deepest technical talent pool. Iași fits where you also serve EU users or need the simpler adequacy position, and São Paulo covers the UK evening. Many organisations combine hubs rather than choosing one. Scroll ## Ready to scale your team? Discover how our proven model builds teams that drive performance, reduce costs, and multiply growth. [Book a Demo](https://www.potentiam.co.uk/contact-us) ### Related case studies [![A UK founder at his desk comparing options on a printed document, laptop open, London skyline behind](https://blog.potentiam.co.uk/hs-fs/hubfs/blog/images/freelance-vs-embedded-decision-hero.webp?length=750&name=freelance-vs-embedded-decision-hero.webp)](https://blog.potentiam.co.uk/freelance-marketplaces-vs-embedded-offshore-team) [Blog](https://blog.potentiam.co.uk/tag/blog) #### [Freelance Marketplaces or an Embedded Offshore Team? Choosing for Ongoing Work](https://blog.potentiam.co.uk/freelance-marketplaces-vs-embedded-offshore-team) [![Two consultants reviewing a document together at a desk in a bright modern professional services office](https://blog.potentiam.co.uk/hs-fs/hubfs/blog/images/professional-services-offshore-hero.webp?length=750&name=professional-services-offshore-hero.webp)](https://blog.potentiam.co.uk/offshore-teams-professional-services-consulting) [Blog](https://blog.potentiam.co.uk/tag/blog) #### [Offshore Teams for Professional Services and Consulting Firms](https://blog.potentiam.co.uk/offshore-teams-professional-services-consulting) [![An offshore team leader guiding two colleagues at their desks in a bright, well-run office](https://blog.potentiam.co.uk/hs-fs/hubfs/blog/images/managed-services-offshore-team-office-2026-09.webp?length=750&name=managed-services-offshore-team-office-2026-09.webp)](https://blog.potentiam.co.uk/benefits-of-using-managed-services-for-building-an-offshore-team) [Featured](https://blog.potentiam.co.uk/tag/featured) #### [Managed Services vs BPO vs EOR: Which Model Delivers the Best Offshore Team?](https://blog.potentiam.co.uk/benefits-of-using-managed-services-for-building-an-offshore-team) [![An IT operations manager and colleague reviewing a shift rota in a UK service desk office](https://blog.potentiam.co.uk/hs-fs/hubfs/blog/images/loc1-hero-20260904-231148.webp?length=750&name=loc1-hero-20260904-231148.webp)](https://blog.potentiam.co.uk/best-offshore-location-technology-msp-team) [Blog](https://blog.potentiam.co.uk/tag/blog) #### [Best Offshore Location for a Technology or MSP Team](https://blog.potentiam.co.uk/best-offshore-location-technology-msp-team) [![Offshore team in boardroom meeting and collaborating with onshore colleagues](https://blog.potentiam.co.uk/hs-fs/hubfs/offshore-team-boardroom-meeting-collaboration-hero-1.jpg?length=750&name=offshore-team-boardroom-meeting-collaboration-hero-1.jpg)](https://blog.potentiam.co.uk/hidden-costs-of-an-offshore-entity-what-businesses-miss-potentiam) [Featured](https://blog.potentiam.co.uk/tag/featured) #### [Hidden Costs of Building an Offshore Entity: What Most Businesses Miss](https://blog.potentiam.co.uk/hidden-costs-of-an-offshore-entity-what-businesses-miss-potentiam) [![A UK chief operating officer and finance director reviewing an outsourcing contract together in a London office, weighing the pros and cons](https://blog.potentiam.co.uk/hs-fs/hubfs/blog/images/outsourcing-pros-and-cons-hero.webp?length=750&name=outsourcing-pros-and-cons-hero.webp)](https://blog.potentiam.co.uk/outsourcing-pros-and-cons) [Blog](https://blog.potentiam.co.uk/tag/blog) #### [Outsourcing Pros and Cons: An Honest Guide for UK Businesses](https://blog.potentiam.co.uk/outsourcing-pros-and-cons) [![A UK operations director reviewing a service contract and cost figures in a modern boardroom](https://blog.potentiam.co.uk/hs-fs/hubfs/blog/images/bpo-contract-review-hero.webp?length=750&name=bpo-contract-review-hero.webp)](https://blog.potentiam.co.uk/bpo-vs-embedded-offshore-team) [Blog](https://blog.potentiam.co.uk/tag/blog) #### [BPO or Embedded Offshore Team? How to Choose for Your Process](https://blog.potentiam.co.uk/bpo-vs-embedded-offshore-team) [![A business leader at a window considering a strategic location decision, city skyline beyond](https://blog.potentiam.co.uk/hs-fs/hubfs/blog/images/location-decision-hero.webp?length=750&name=location-decision-hero.webp)](https://blog.potentiam.co.uk/offshoring-vs-nearshoring-uk-guide) [Blog](https://blog.potentiam.co.uk/tag/blog) #### [Offshoring vs Nearshoring vs Onshoring: A Location Guide for UK Companies](https://blog.potentiam.co.uk/offshoring-vs-nearshoring-uk-guide) [![A UK business leader and team lead reviewing team growth and hiring options in a modern office](https://blog.potentiam.co.uk/hs-fs/hubfs/blog/images/positioning-hiring-options-hero.webp?length=750&name=positioning-hiring-options-hero.webp)](https://blog.potentiam.co.uk/recruitment-agency-vs-embedded-offshore-team) [Blog](https://blog.potentiam.co.uk/tag/blog) #### [Recruitment Agency, Staffing Firm or Embedded Offshore Team: Which Do You Need?](https://blog.potentiam.co.uk/recruitment-agency-vs-embedded-offshore-team) [![footer-logo](https://blog.potentiam.co.uk/hubfs/footer-logo.svg)](https://blog.potentiam.co.uk/) We strategically build offshore teams that integrate seamlessly into your business. ##### Solutions - [Technology](https://www.potentiam.co.uk/solutions/technology) - [Finance & Accounting](https://www.potentiam.co.uk/solutions/finance-accounting) - [Marketing & Design](https://www.potentiam.co.uk/solutions/marketing-and-design) - [Data Analytics](https://www.potentiam.co.uk/solutions/data-analytics) - [Sales & Customer Success](https://www.potentiam.co.uk/solutions/sales-customer-service-solutions) - [Energy Consulting](https://www.potentiam.co.uk/solutions/energy-consulting) ##### Locations - [Cape Town](https://www.potentiam.co.uk/locations/south-africa) - [Johannesburg](https://www.potentiam.co.uk/locations/johannesburg) - [Bangalore](https://www.potentiam.co.uk/locations/india) - [Iași](https://www.potentiam.co.uk/locations/romania) - [São Paulo](https://www.potentiam.co.uk/locations/brazil) ##### Quick links - [About us](https://www.potentiam.co.uk/about-us) - [Careers](https://www.potentiam.co.uk/careers) - [Contact us](https://www.potentiam.co.uk/contact-us) © 2026 Potentiam. All rights reserved. [Privacy Policy](https://blog.potentiam.co.uk/privacy) ```json { "@context" : "https://schema.org", "@id" : "https://blog.potentiam.co.uk/migrating-outsourced-service-desk-offshore-team#article", "@type" : "Article", "author" : { "@id" : "https://www.potentiam.co.uk/#organization" }, "dateModified" : "2026-09-29", "datePublished" : "2026-08-12T12:16:14Z", "description" : "How UK companies move an outsourced IT service desk to a dedicated offshore team: baseline, contract exit, TUPE, knowledge transfer and phased cutover.", "headline" : "Migrating an Outsourced Service Desk to an Embedded Offshore Team", "image" : "https://5804539.fs1.hubspotusercontent-na1.net/hubfs/5804539/blog/images/service-desk-migration-planning-hero.webp", "keywords" : [ "service desk outsourcing", "outsourced service desk", "service desk transition plan", "insourcing service desk", "offshore service desk", "service desk migration" ], "mainEntityOfPage" : { "@id" : "https://blog.potentiam.co.uk/migrating-outsourced-service-desk-offshore-team" }, "publisher" : { "@id" : "https://www.potentiam.co.uk/#organization" }, "wordCount" : 3494 } ``` ```json { "@context" : "https://schema.org", "@id" : "https://www.potentiam.co.uk/#organization", "@type" : "Organization", "address" : { "@type" : "PostalAddress", "addressCountry" : "GB" }, "description" : "Potentiam is a London-based strategic offshoring consultancy that helps mid-sized companies build high-performing, embedded offshore teams across South Africa, Romania, India and Brazil.", "logo" : { "@type" : "ImageObject", "url" : "https://www.potentiam.co.uk/hubfs/logo.svg" }, "name" : "Potentiam Ltd", "sameAs" : [ "https://www.linkedin.com/company/potentiam-ltd" ], "url" : "https://www.potentiam.co.uk" } ``` ```json { "@context" : "https://schema.org", "@id" : "https://blog.potentiam.co.uk/migrating-outsourced-service-desk-offshore-team#breadcrumb", "@type" : "BreadcrumbList", "itemListElement" : [ { "@type" : "ListItem", "item" : "https://www.potentiam.co.uk", "name" : "Home", "position" : 1 }, { "@type" : "ListItem", "item" : "https://blog.potentiam.co.uk", "name" : "Blog", "position" : 2 }, { "@type" : "ListItem", "name" : "Migrating an Outsourced Service Desk to an Embedded Offshore Team", "position" : 3 } ] } ``` ```json { "@context" : "https://schema.org", "@id" : "https://blog.potentiam.co.uk/migrating-outsourced-service-desk-offshore-team#faq", "@type" : "FAQPage", "mainEntity" : [ { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "It depends on your contractual notice period, which often sets the pace, and on how far the phases overlap. Using our indicative durations, discovery and baselining take four to six weeks, knowledge transfer four to eight weeks, and the pilot, dual running and final cutover a further seven to fourteen. Building the team takes a time that varies by hub and client: hiring typically takes four to six weeks from starting the search to the candidate accepting the offer (four to eight in São Paulo), before notice periods and onboarding. Team build usually runs alongside discovery and the notice period, and knowledge transfer starts as the first hires arrive, so the total is shorter than the sum of the phases." }, "name" : "How long does it take to migrate an outsourced service desk to an offshore team?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "TUPE covers service provision changes as well as business transfers, so bringing a service back in house or moving it between providers can trigger it. That route turns on whether, immediately before the change, an organised grouping of employees in Great Britain was doing the work: a desk your provider already runs from abroad often falls outside it, while a desk staffed in Great Britain may not, even if the work is moving offshore. A business transfer analysis can differ. This turns on the facts, so take employment law advice before committing to a timetable." }, "name" : "Does TUPE apply when moving a service desk offshore?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "It depends entirely on your contract. Some agreements give the client full ownership of documentation and ticket data; others leave ownership with the provider or say nothing at all. Establish this before serving notice, because your ability to insist is greatest while the relationship is still live." }, "name" : "Who owns the knowledge base and ticket history in an outsourced service desk?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "If the team is outside the UK and is a separate legal entity, giving them access to personal information is a restricted transfer under UK GDPR, even if the data never leaves your systems. Romania is covered by UK adequacy as an EEA member state, which removes the need for an IDTA or transfer risk assessment but not your other UK GDPR duties. South Africa, India and Brazil are not, so transfers there need an appropriate safeguard such as the International Data Transfer Agreement or the EU standard contractual clauses with the UK Addendum, together with a transfer risk assessment. This applies equally to an outsourced provider. Take advice on your own data flows." }, "name" : "Do I need extra data protection measures for an offshore service desk?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "Plan for a dip in the first weeks. The way to contain it is to phase the cutover, run both desks in parallel while volume shifts, start with a contained pilot queue, and move out-of-hours cover last. Judge recovery against your own pre-migration baseline, which is why capturing that baseline first matters so much." }, "name" : "Will service quality drop during the transition?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "For UK business-hours cover, South Africa aligns most closely: one hour ahead of the UK in summer and two in winter, a 9 to 6 day in Cape Town or Johannesburg runs from 8am to 5pm UK time in summer and 7am to 4pm in winter, with a deep pool of English-speaking talent. Bengaluru suits overnight and follow-the-sun cover on agreed shifts and offers the deepest technical talent pool. Iași fits where you also serve EU users or need the simpler adequacy position, and São Paulo covers the UK evening. Many organisations combine hubs rather than choosing one." }, "name" : "Which location is best for a UK service desk?" } ] } ```