Global HR 9 min read

Global Mobility and the Equipment That Has to Follow

Global mobility programmes plan for visas, tax and housing. The laptop is usually an afterthought, and it is the thing that breaks on day one.

Rachel Kim Rachel Kim • • 9 min read
Global Mobility and the Equipment That Has to Follow

TL;DR

Global mobility teams are good at the hard parts. Immigration, payroll registration, tax equalisation, housing. Then somebody lands in Lisbon on a Monday with a laptop that cannot be supported there, a charger with the wrong plug, and a warranty that stops at the border. The hardware is the smallest line in the budget and the first thing the employee notices.

  • Equipment is usually nobody’s line item on a relocation. Assign it before the move.
  • A laptop that crosses a border may lose its warranty and its support path.
  • Shipping the existing machine is often slower and dearer than issuing a local one.
  • Customs and duty turn a two-day courier into a three-week problem.
  • Decide early whether the device belongs to the old entity or the new one.
  • Build the equipment step into the relocation timeline, not the arrival week.

Why global mobility keeps missing the hardware

Relocation programmes are built around the things that stop somebody working legally. Visas. Payroll registration. A local bank account. Tax status.

Equipment stops somebody working practically, which is a different category and tends to sit with a different team.

So the relocation checklist says housing and schooling and shipping allowance, and nowhere does it say who is responsible for the machine the person actually opens on Monday.

What that looks like in practice

Say you move an engineer from Manchester to Berlin. Mobility handles the paperwork. IT finds out on the Thursday before. The existing laptop is on a UK support contract, the keyboard layout is wrong for the new team, and nobody has checked whether the device can legally leave with the data on it.

None of that is hard. All of it is slow once it is urgent.

Free Weekly Briefing Stay ahead of what's changing in HR and people ops.

Join 4,200+ leaders getting practical insights every week — no fluff, just signal.

Join Free →

The three routes, and when each one is right

There are only three ways to get a working machine in front of a relocating employee. The choice is usually made by default rather than deliberately.

Route When it fits What goes wrong
Ship the existing device Short assignments, familiar setup matters Customs, duty, warranty ends at the border
Issue a new local device Permanent moves, new entity employs them Data migration, and the old device needs recovering
Collect on arrival Country has a local partner or office Depends entirely on local stock existing

Shipping feels like the cheap option because the asset already exists. It frequently is not. A laptop crossing a border is a commercial import, and the duty, the broker fee and the delay belong to somebody.

Issuing locally costs more on paper and less in practice, with one condition: somebody has to recover the old machine. A device left in a drawer in the origin country is a data problem and a write-off at the same time.

The question that decides it

Is this a move or a transfer? A six month assignment where the person stays on the original payroll is a move, and shipping usually wins. A permanent transfer to a new entity is a transfer, and issuing locally almost always wins.

Who owns the asset after the border

This is the part that produces an argument with finance eighteen months later.

If an entity in one country bought the laptop and an employee of another entity is now using it, the asset register and the payroll are describing different companies. That is fine until somebody runs an audit, a depreciation schedule or an intercompany recharge.

Decide at the point of the move, not at the point of the audit. There are only three sensible answers.

  • Stays with the origin entity and is recharged. Simple, and it keeps the depreciation where it started.
  • Transfers to the destination entity at book value. Cleaner long term, more paperwork now.
  • Written off and replaced locally. Honest for older machines and much faster.

The third option is undervalued. A three year old laptop with eight months of depreciation left is rarely worth an intercompany transfer and a customs declaration. Our note on equipment depreciation and what finance needs covers how that calculation usually lands.

The data question nobody raises until late

A device moving countries is also data moving countries, and that is a separate decision from the hardware one.

the General Data Protection Regulation text on EUR-Lex governs transfers out of the European Economic Area, and whether a given move needs anything beyond ordinary internal controls depends on where the data sits, who the controller is and what is on the machine. That is a question for your own counsel rather than for an equipment vendor, and it is worth asking before the box is sealed rather than after.

The practical version for most teams is simpler. Wipe and reimage, or issue clean and migrate through your own systems. the NCSC device security guidance sets out what device security guidance looks like in general terms, and a clean build on arrival avoids most of the argument.

The sanitisation step

If a device is being retired rather than moved, it needs a documented wipe rather than a quick format. That matters more when the device is crossing a border, because the chain of custody is longer and the people handling it are not yours.

The decision table

Pick the row that matches the move, not the headcount.

Situation Scale Setup Primary pain Recommended starting point
Six month assignment, same entity Any Origin payroll continues Support stops at the border Ship the device, extend support explicitly
Permanent transfer, new entity Series A+ Local employment contract Asset sits on the wrong books Issue locally, recover the original
Move to a country with no presence Any Employer of record arrangement Nobody local can hand over kit Use a partner that ships and recovers
Several moves a quarter Series B+ Mobility programme exists Each move handled from scratch One standing process, one owner
Employee relocating by choice Any Remote-first policy Policy silent on who pays Write the rule before the first request

Row five is the one that catches remote-first companies. An employee who moves themselves is not a relocation in the mobility sense, and the equipment question is identical.

Putting equipment on the relocation timeline

The fix is dull. Add two items to the plan you already run.

At offer or decision. Decide the route, the owning entity and who recovers the old device. Five minutes, and it removes most of the later friction.

Four weeks out. Start the equipment action. If you are shipping, that means customs paperwork. If you are issuing locally, that means an order placed against a real address.

Four weeks sounds generous until a device has to clear customs in a country where your company has no importer of record. Then it is tight.

Who should own the step

Mobility should own the trigger and IT should own the execution. The common failure is both assuming the other is watching the date.

For teams without a local presence in the destination country, a partner that handles procurement and recovery in-market removes the problem rather than coordinating it. RemoAsset handles global laptop procurement and delivery and the matching device retrieval when the assignment ends, which is the half most relocation plans forget until somebody has already left.

Allowances, reimbursement and the grey area

Many relocating employees buy something themselves in week one. A monitor, a desk, an adapter. Then they expense it, and the policy has nothing to say.

the UK guidance on homeworking expenses and benefits sets out how homeworking expenses and benefits are treated in the UK, and equivalent rules differ by country, which is precisely why a single global line in the policy is worth having. Decide what the company provides, what it reimburses and what it does not cover, and say so in the relocation pack.

the OSHA computer workstation guidance is also worth a look if you fund desk setups, because the guidance on workstation arrangement is the same wherever the desk physically is.

One rule that prevents most of it

Publish a short equipment section in the relocation document with three numbers: what is issued, what is reimbursed up to, and what is not covered. People do not argue with a published limit nearly as much as they argue with silence.

If you are building that document, our guide to what belongs in an employee relocation policy covers the structure.

RemoAsset places and recovers equipment in markets where you have no office, including holding stock between assignments. Read more on device operations at HROpsLab.

Frequently asked questions

Who owns equipment in a global mobility programme?

Usually nobody, which is the problem. Mobility owns immigration, payroll and housing, IT owns devices, and the relocation checklist rarely names an owner for the laptop. The fix is to assign it at the point the move is decided rather than the week the person travels. Mobility should own the trigger and the date, IT should own the execution, and the handover between them should be written down once rather than improvised per move.

Should we ship an employee’s laptop when they relocate?

For a short assignment on the original payroll, usually yes. For a permanent transfer to a new entity, usually no. A laptop crossing a border is a commercial import, so duty, broker fees and delay apply, and the warranty and support contract often stop at the border. Issuing a local device costs more on paper and less in practice, provided somebody is actually responsible for recovering the original machine.

What happens to the warranty when a device moves country?

It depends on the manufacturer and what was purchased, and the honest answer is that many standard warranties are regional rather than international. That is worth checking per vendor before the move rather than assuming either way. The practical consequence is a support path that works in the origin country and not the destination one, which surfaces the first time something breaks and the person is already working.

Which entity should own the asset after a relocation?

Pick one of three answers at the time of the move: it stays with the origin entity and is recharged, it transfers to the destination entity at book value, or it is written off and replaced locally. The third is undervalued, because an older machine with little depreciation left is rarely worth an intercompany transfer plus a customs declaration. What causes trouble is deciding none of them and discovering the mismatch during an audit.

How far ahead should equipment be arranged for a relocation?

Start four weeks before the move date, and earlier if the destination is a country where you have no legal presence. Four weeks sounds generous until a device needs to clear customs somewhere you have no importer of record, at which point it is tight. The two dates worth putting in the plan are the decision point, where the route and owning entity are chosen, and the action point four weeks out.

What about employees who relocate themselves?

Treat it as the same equipment question with a different trigger. A remote-first company whose policy is silent will get the request anyway, usually after the person has moved and bought something. Publish three numbers in the policy: what the company issues, what it reimburses and to what limit, and what it does not cover. People argue with silence far more than they argue with a published limit.

Do we need to wipe a device before it crosses a border?

If it is being retired or reassigned rather than travelling with its existing user, it needs a documented sanitisation rather than a quick format, and the chain of custody matters more than usual because more hands touch it. If it is travelling with the same person, the question is about data transfer rules rather than the hardware, and that is one for your own counsel since it turns on where the data sits and who controls it.

Share on X Share on LinkedIn

What to do next?

Explore More Articles

Dig deeper into HR Ops strategy, tools, and workflows built for real teams.

Browse the blog →
Join the HROpsLab Community

Connect with People Ops practitioners sharing real workflows, tools, and challenges.

Join now →