How We Moved a 35-Person IT Co. to Cyprus in 10 Weeks

Relocating an IT company from Norway to Cyprus is an increasingly common strategy for founders who want predictable corporate tax, EU market access, and founder-friendly personal planning. A cross-border move is complex: corporate governance, staff immigration, payroll, VAT, banking, and contract transitions all need to follow a precise sequence.

Done right, projects continue without a single missed invoice. Done wrong, you risk permanent establishment exposure in Norway, delayed payrolls, or gaps in customer billing.

Below we set out the practical roadmap, the pitfalls to avoid, and the documents you need.

Why IT companies move to Cyprus

  • Predictable corporate tax (12.5%) – among the lowest stable rates in the EU.

  • Non-dom and first-employment reliefs – founder-friendly personal planning, no SDC on dividends/interest, and generous income tax relief for new arrivals.

  • Treaty network and EU access – strong double-tax treaties and freedom to operate across the EU/EEA.

  • Modern substance rules – a clear framework to build management and control in Cyprus, without over-regulation.

Key risks to manage

  1. Tax residency & substance – a Cyprus entity only counts if management and control genuinely sit in Cyprus (board, records, banking, decision-making).
  2. People sequencing – EEA nationals register under EU rules, but non-EEA hires need the CFE route; payroll cannot run until Social Insurance and GHS numbers are active.
  3. Commercial continuity – contracts, data protection, and VAT place-of-supply must transition without billing interruptions.
  4. Norway touchpoints – you must avoid triggering a permanent establishment in Norway and address any exit or transfer-pricing impacts on assets and IP

The Roadmap

1. Structure & governance (weeks 1–2)

  • Incorporate a Cyprus OpCo while retaining the Norwegian company for legacy contracts.

  • Reconstitute a majority Cyprus-resident board; adopt a board calendar and move records and bank mandates to Cyprus.

  • Build an audit-ready TD98 residency file with minutes, leases, utilities, and execution logs.

2. People & immigration (weeks 2–6)

  • Register EEA staff under MEU1; obtain Cyprus tax numbers, Social Insurance and GHS enrolments.

  • Qualify under the CFE regime to sponsor non-EEA engineers; issue compliant contracts and insurance.

  • Run payroll from week 6 with Cyprus employer registrations, capped contributions, and GHS applied.

3. Tax & incentives (weeks 2–5)

  • Configure Cyprus corporate tax at 12.5% and establish the provisional tax calendar.

  • Document non-dom status for founders; assess first-employment relief for relocating hires.

  • Evaluate IP Box eligibility; ring-fence IP with DEMPE functions governed in Cyprus.

4. Commercial & VAT (weeks 3–7)

  • Novate EU contracts to the Cyprus OpCo; retain the Norwegian entity for Norway-only public contracts.

  • Complete VAT registration (19%); set up OSS for B2C digital services; embed place-of-supply rules in ERP.

  • Shift contract execution to Cyprus to control PE risk; CRM/e-signature workflows evidence location.

5. Banking & KYC (weeks 2–6)

  • Prepare a full KYC pack (UBO tree, SoF, board authorities, auditor engagement, lease).

  • Open Cyprus banking; test SEPA and FX rails; set standing orders for payroll and utilities.

6. Controls, transfer pricing & intercompany (weeks 5–8)

  • Execute intercompany agreements (services, secondment, IP licence) at arm’s length and create a TP/master file aligned with Cyprus substance.

  • Implement a monthly close checklist for VAT, payroll, and contributions; set the year-end audit timetable.

Common mistakes

  • “Incorporate and hope” – a paper entity with no local control is not Cyprus tax resident.
    • Fix: appoint a majority Cyprus board, execute contracts locally, and build a TD98 file.

  • Late payroll/VAT setup – leaving registrations to the last minute causes gaps.

    • Fix: file before first payslips and invoices; apply caps correctly.

  • Norway PE risk – sales still contracting in Norway trigger tax exposure.

    • Fix: repaper sales processes, execute contracts in Cyprus, and limit NO authority.

  • Banking KYC gaps – incomplete UBO or source-of-funds delays account opening.

    • Fix: prepare a consolidated KYC file with board minutes and local IDs.

  • IP transfer without DEMPE in Cyprus – moving IP without substance risks denial of IP Box benefits.

    • Fix: locate DEMPE functions in Cyprus and evidence decisions in board minutes.

Relocation checklist

Governance — Appoint Cyprus-resident directors; adopt board calendar; move records & seal; bank mandates in CY.
Registrations — TIC, VAT, PAYE, Social Insurance, GHS; e-filing access; compliance calendar.
People — MEU1 for EEA staff; CFE for non-EEA; contracts and payroll onboarding; health insurance until GHS active.
Commercial — Novate EU contracts; define Norway retention plan; update invoices/OSS; CRM + e-signature location controls.
Tax/TP — Intercompany services/licences; TP files; provisional tax; residency certificate request pack.
Banking — KYC pack; open accounts; SEPA tests; standing orders; FX policy.
Facilities — Office lease, utilities, IT stack; data-processing records (GDPR) pointing to Cyprus controller.

Relocating an IT company from Norway to Cyprus takes around 10 weeks if sequencing is managed correctly. The reward is lower tax friction, stable EU access, and a founder-friendly personal regime. The risk, if mismanaged, is PE exposure in Norway, delayed operations, or failed compliance.

Preparation is everything: with a structured roadmap, an audit-ready file, and proactive KYC and payroll planning, the move runs smoothly — and your projects continue without a single missed invoice.

Insights & Success Stories

Related Industry Trends & Real Results