Request a quote
Emergency SectorsCareers About us Blog Get in touch
Two colleagues at the same long row of desks, both at a keyboard and a monitor

IT nearshoring: what to move, and what to keep close

IT nearshoring looks like a saving on the map: a team a short flight away, with little time difference. Whether it works depends on which work you move and who directs it. This is the split we use: what fits a nearshore team, what is better kept close, and what to settle before the first ticket crosses a border.

6 min read Written by the ITproposal team
Short answer

Nearshoring works for IT work you do not have to touch and can describe: development, monitoring, second-line support, migrations and documentation.

The key choice is not the country but who directs the team: you, or the supplier taking over the work. Coordination and the legal form both follow from that.

If a team outside the UK or EEA can reach personal data, that is a restricted transfer. Settle access, logging and the legal basis before the first working day.

What IT nearshoring is, and what it is not

Nearshoring means placing IT work with a team in a nearby country: a short flight, a time difference of a few hours at most, and a working culture not far from your own. Offshoring is the same thing at a long distance; onshoring keeps it in your own country. The difference is not the map but the collaboration: with one or two hours between you, you can talk every day; with seven or eight you cannot.

IT nearshoring is not a service but a location. You can open your own entity there, hire people you direct yourself, or outsource a defined piece of work to a supplier who organises it there. The question that matters therefore comes before the choice of country: which work do you want done elsewhere, and who directs it?

What it usually is not: a way of making the same organisation cheaper. Work that runs messily in your own office does not run better at a distance. It runs messily with a time difference.

Which work suits nearshoring

The rule of thumb is the same as for remote work: anything you do not have to touch and can describe.

  • Software development and testing, with a backlog and acceptance criteria agreed before the work starts.
  • Monitoring and second-line support for servers, network and cloud, once runbooks and the escalation route exist.
  • Migrations and automation: scripts, deployment packages, configuring Microsoft 365 or Azure to a design that has already been approved.
  • Documentation and clean-up: updating the asset register, recording configurations, removing old scripts and permissions.

What these four have in common: the result can be checked without sitting next to the people doing it. If you cannot write down when something is finished, the work is not ready to move, not even within your own country.

What to keep close, or not move first

  • Anything physical. A laptop that will not boot, a switch that needs replacing, a new starter’s first day. You need someone on site for that, and a team one country away does not solve it.
  • First contact with users, when language and knowledge of the workplace matter. A service desk your people cannot understand costs more than it saves. If the team speaks their language, this point shrinks.
  • Work whose requirements are not yet settled. Architecture decisions, the design of a new environment, the question of what actually needs doing: that belongs close to the people who decide.
  • Access you cannot oversee. You do not give admin accounts with full rights to everything to a team you do not yet know, in any country. Access management first, then the work.

So start with a defined piece of work you can measure, and expand once it runs. A team handed “everything except the service desk” in one go spends its first months mostly asking questions.

Three models, and who directs the work

There are broadly three ways to organise nearshoring. The difference lies in who directs the people, and that decides where the coordination sits.

  • Your own entity. You are the employer in that country, with a legal entity, local employment terms, administration and management on the ground. Only worth it if you need the team for years and at scale.
  • Team extension. A supplier provides people who work in your team and whom you direct. Fast and flexible, but coordination, quality and knowledge transfer stay with you.
  • A work package or a managed service. A supplier takes over an outcome and directs the work itself, with its own point of contact and agreements on what is delivered. You manage the outcome, not the people.

That choice is also a legal one. Who directs the people determines, in many countries, what kind of contract it is and whether rules on supplying workers apply. Have that checked before you sign. How staffing compares with hiring in general is covered in IT staffing or hiring.

Data, access and UK GDPR

A team in the EEA is covered by the UK adequacy regulations, so data can flow there. If the team sits outside the UK and the EEA and can reach personal data, even only to look, that is a restricted transfer under UK GDPR. You then need a mechanism such as the International Data Transfer Agreement or the UK Addendum to the EU standard contractual clauses, plus a transfer risk assessment. Türkiye has no UK or EU adequacy decision, so for a team there it goes through contract clauses.

  • A data processing agreement with the supplier doing the work, and visibility of the sub-processors involved.
  • Access by role and for a set period, with multi-factor authentication and an admin account in your name that can revoke it.
  • Logging of admin actions in a place the team itself cannot erase.
  • Data stays where it is: the team works in your environment, not on a copy on its own laptop.

The supplier also belongs in your supply chain review, as it would for any IT supplier, in any country. That is not extra paperwork for nearshoring alone.

Time difference, language and handover

With nearshoring the time difference is small but not zero, and it moves. Türkiye stays on UTC+3 all year without daylight saving, so it is three hours ahead of the UK in winter and two in summer. Plan meetings and maintenance windows for both.

  • A fixed overlap window: a few hours a day when both sides are reachable, with the daily stand-up inside it.
  • One ticketing system for incidents, changes and questions, so a handover does not run through email and chat.
  • A working language agreed in advance. English is fine, as long as it is also the language of the documentation and the tickets.
  • A fixed point of contact on your side of the border, so your own people never have to work out who sits where.

How we set that up for clients with sites in several countries is described on our page on global delivery.

What really drives the cost

The hourly rate is in every comparison, and it is the least decisive number. What nearshoring costs sits mostly in the items around it:

  • Onboarding: the weeks in which the team learns your environment and your people answer questions instead of doing their own work.
  • Coordination: meetings, reviews and checking what has been delivered. With team extension that is on you; with a work package it largely sits with the supplier.
  • Turnover: when people in the team change, you pay for onboarding again. Ask how knowledge is recorded and how replacement works.
  • Travel: sitting in one room a few times a year prevents more misunderstandings than a year of video calls.
  • Rework: work that has to be redone because the brief was not sharp. It appears in no quote and always happens at some point.

Compare offers on what is delivered and who directs it, not on a rate per hour.

Where our work stops

What we do. We work as one team from three offices: Amsterdam, Antwerp and Karaman in Türkiye. Client contact is handled by our own people, and on-site work by our own local engineers in every country; the team in Karaman serves our clients in Türkiye and does engineering and development work. Work that is not tied to a location we take over as a managed service or a defined work package, with a fixed point of contact and agreements on what is delivered. Which part runs from which office is agreed per engagement.

What we do not do. We do not set up an entity or a branch for you in another country, and we are not lawyers. Whether an arrangement falls under employment law, which tax and social security rules apply to cross-border work, and whether your data transfer is in order, you have checked by a lawyer or adviser. We explain what a technical arrangement means in practice, not whether it is legally sound.

Frequently asked

Questions we get about this

The five that come up most often.

What is IT nearshoring?

IT nearshoring means placing IT work with a team in a nearby country, with a small time difference and a short journey. It can be your own entity, contracted people you direct yourself, or a work package a supplier delivers from there. The difference from offshoring is distance, and with it how easily you work together day to day.

What is the difference between nearshoring and offshoring?

Nearshoring moves work to a nearby country; offshoring moves it far away, often with a large time difference. The further away, the more the collaboration relies on written handover rather than conversation. Which suits you depends on how much coordination the work needs.

Which IT work is suitable for nearshoring?

Work you do not have to touch and can describe: development and testing, monitoring and second-line support, migrations, automation and documentation. Less suitable are on-site work, first contact with users in their own language, and design decisions that are not yet settled. Start with a defined piece you can measure.

Can a team outside the UK access our personal data?

It can, but under UK GDPR it is a restricted transfer unless the country is covered by adequacy regulations, as the EEA is. You then need a mechanism such as the International Data Transfer Agreement or the UK Addendum, and a transfer risk assessment. Have the legal side checked by a lawyer.

Do you handle the legal side of nearshoring?

No. We are not lawyers and we do not set up entities or branches in other countries. We take over work as a managed service or a work package with a fixed point of contact, from our offices in Amsterdam, Antwerp and Karaman. Employment law, tax and the data transfer assessment are for a lawyer or adviser.

Related services

Further reading

What nearshoring connects to.

Which work can run at a distance?

Tell us which work you are thinking of moving and what your environment looks like. We will say what we can take over as a service, what is better kept close, and what to have checked legally first.

Practical IT knowledge in your inbox

New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.

We use your address for the newsletter only. See our privacy policy.

Request a quote Call