EU Cloud Migration

Move from US cloud to Sweden – cloud migration without downtime

Sovereignty Assessment + migration from AWS, Azure or GCP to a Swedish data center in 2 weeks. We map your cloud dependencies, produce an exit plan and carry out the move – while you keep working.

NIS2 DORA GDPR / Schrems II 🇸🇪 Data residency

Why migrate from AWS/Azure now?

Many Swedish SaaS companies and fintechs chose AWS or Azure because it felt secure, scalable and cheap. But the regulatory landscape has changed radically – and US cloud providers are subject to American legislation regardless of where the data is physically stored.

NIS2

The cybersecurity act applies now

NIS2 (the cybersecurity act) came into force in January 2026 and affects an estimated 8,000 Swedish organizations. If you sell to banks, insurance companies, municipalities or energy companies, you must be able to prove where your data resides – the supply chain is an audit point.

DORA

Mandatory for financial data

DORA (Digital Operational Resilience Act) requires full control over ICT third-party risks. The requirement is simple: the cloud must be in the EU and you must be able to prove it to auditors. Concentration risk towards US hyperscalers must be justifiable – and phased out.

Procurement

Customer demands for Swedish data

More and more procurements require it in black and white: “prove that your data resides in Sweden”. Under the CLOUD Act, US authorities can demand data from US providers – the only robust protection is a European provider on European soil.

What waiting costs you

  • Lost deals – failing compliance disqualifies you in procurements
  • Rising audit costs – you have to prove compliance you don't have
  • Competitive disadvantage – customers choose providers with sovereign data handling

The solution

  • Move to sovereign operations in Sweden before the regulatory requirements take full effect
  • 2 weeks – without you having to shut anything down
  • Documented compliance – certificates and agreements that hold up in an audit

What do we move – and what replaces the US cloud services?

A common objection is "but we use managed services in AWS". Here is how the most common services map to sovereign equivalents in our data center.

In the US cloud todayWith us in a Swedish data center
EC2 / Azure VM / Compute Engine Virtual machines on our VMware/KVM platform – same OS, same applications, often better performance per krona
RDS / Azure SQL / Cloud SQL PostgreSQL, MySQL or SQL Server as a managed database – we handle patching, backup and replication
S3 / Blob Storage S3-compatible object storage in the data center – your applications often only need a new endpoint and new keys
EKS / AKS / GKE Kubernetes clusters that we operate – your manifests and Helm charts work as before
CloudWatch / Azure Monitor Monitoring stack with alert chain – included in Managed EU Drift
Route 53 / Azure DNS Redundant DNS operations – or you keep your external DNS provider

Serverless services (Lambda, Functions) and proprietary PaaS services require rebuilding – this is captured in the assessment with a time estimate per service, so you know exactly what moves as-is and what needs adaptation.

What we do

A structured exit – not a risky lift-and-hope project.

Mapping & assessment

  • Inventory of workloads, data and integrations in your current cloud
  • Compliance gap analysis against NIS2, DORA and GDPR
  • Dependency map – which services can be moved as-is, which need replacing

Migration & verification

  • Migration plan with rollback points and minimal downtime
  • Move to a Swedish data center – our own data center in an air-raid shelter
  • Verification of function, performance and data residency after the move

Security during the move itself

  • Encrypted transport – all data is moved over encrypted tunnels (TLS/IPsec), never in plaintext over the internet
  • Checksum verification – every volume is cryptographically verified after copying
  • Source data is never touched – your US cloud environment remains untouched until you approve decommissioning
  • Controlled decommissioning – we help you delete data at the old provider, with documentation

Prepare yourselves – checklist before the assessment

  • List your systems – even a rough list saves time on day 1
  • Appoint a technical contact with an overview of the environment
  • Gather your contracts – current cloud agreements and any customer data residency requirements
  • Note deadlines – procurements, audits or contract renewals that drive the timeline

What's included in the Sovereignty Assessment?

Fixed price, fixed delivery in 2 business days. You get decision material you can take to the board – and a plan that can be executed immediately.

What's included

  • Current-state mapping – systems, data flows and cloud providers
  • Compliance review – NIS2, DORA and your specific requirements
  • Migration plan – time, risks, step by step
  • Quote for migration + operations (Managed EU Drift) with timeline and cost

What's not included

  • The migration itself – that's step 2, in a separate quote
  • Hardware purchases – we use our existing data center
  • Application testing – you test your systems, we handle the infrastructure
Time2 business days
CostFixed price – free of charge if you proceed with the migration
Next stepThe migration takes approx. 2 weeks if you say yes

How the assessment works

Three days from start to decision material.

Technical migration process – how we achieve zero downtime

We never migrate everything at once. Each step is verified before the next begins, and a rollback plan is in place the whole way.

Expected downtime0–5 minutes – DNS propagation only
Total time to "everything in a Swedish data center"2–3 weeks for a typical environment
RollbackBack to the old environment in < 15 minutes, throughout the entire migration period

Compliance documentation that holds up in an audit

After the migration you receive the three documents that reviewers, auditors and procurement teams ask for.

Certificate

Data residency certificate (DLI)

Formal certificate: your data resides physically in Sweden, in our data center, and never leaves the jurisdiction without your explicit approval. The appendix you present in a procurement, saying: "here is the proof from the host".

Agreement

Data Processing Agreement (DPA)

Legal agreement covering GDPR (we are your data processor), subprocessor requirements, incident notification within 24 hours and your right to audit us – at any time.

Traceability

Logs & audit trail

All system changes are logged (who, what, when), access logs for everyone touching your data, documented security updates and monthly updated compliance status.

Pricing & timeline for the migration

Fixed price per package – you know the cost before we start. The assessment is always free of charge if you proceed with the migration.

Small system
SEK 50,000 one-time

< 50 GB data, 5–10 VMs

  • Time: 2 weeks
  • Downtime: ~5 min (DNS propagation)
  • Rollback plan the whole way
  • If it takes longer: free extra support
Large system
Quote

> 500 GB, 50+ VMs or multi-region

  • Time: 4–6 weeks
  • Dedicated migration engineer
  • Zero downtime commitment
Guarantee 1

Zero downtime commitment

If the cutover takes longer than 5 minutes, we cover the cost in the form of extended support.

Guarantee 2

30-day money-back

Not satisfied within 30 days? We restore your systems to your old environment and refund the migration fee.

Guarantee 3

One contact, not a ticket queue

Throughout the migration period you have a dedicated engineer on your team – plus 30 days of burn-in support after go-live.

Prices are indicative, excl. VAT. Post-migration support and knowledge transfer to your IT team are included, followed by an optional transition to Managed EU Drift.

Case study: fintech company from AWS to a Swedish data center in 10 days

Anonymized customer – we're happy to share details in a call.

The starting point

  • Entire platform on AWS (eu-north-1): 14 VMs, 120 GB data, PostgreSQL + Redis
  • Two major banks required proven data residency outside US jurisdiction in an ongoing procurement
  • DORA review scheduled – concentration risk towards a US hyperscaler could not be justified

The result

  • 10 days from decision to full operations in a Swedish data center
  • 3 minutes of downtime – DNS cutover on a Sunday night
  • Same performance – database latency even 15% lower than on AWS
  • NIS2/DORA documentation completed – DLI + DPA delivered, the procurement was won

Frequently asked questions about cloud migration

How long does a cloud migration from AWS or Azure take?

A typical migration takes 2 weeks for a small system (< 50 GB, 5–10 VMs) and 3–4 weeks for larger environments. We always migrate in stages: non-critical systems first, production systems last.

Will there be downtime during the migration?

Expected downtime is 0–5 minutes – DNS propagation only at cutover, which we schedule outside business hours. We provide a zero downtime commitment: if it takes longer than 5 minutes, we cover the cost of extended support.

What does a cloud migration to Sweden cost?

The Sovereignty Assessment is free of charge (fixed price SEK 15,000 if you don't proceed, otherwise deducted). The migration costs from SEK 50,000 for a small system and from SEK 150,000 for a medium system. Larger environments are quoted separately.

What happens if something goes wrong during the move?

Every migration has a rollback plan: traffic can be sent back to your old environment in under 15 minutes, throughout the entire migration period. In addition, a 30-day money-back guarantee after go-live is included.

Are we NIS2 and DORA compliant after the migration?

You receive a data residency certificate (DLI), Data Processing Agreement (DPA) and auditable logs – the documentation auditors and procurement teams ask for. Responsibility for your applications and processes remains with you, but the infrastructure part is documented as compliant.

Can you migrate databases without data loss?

Yes. Databases are continuously replicated to the target environment and the cutover is synchronized so that no transaction is lost. Cryptographic verification ensures that every byte matches.

Do we have to move all systems at once?

No. We migrate in stages and can run hybrid during the transition. Many customers start with their most compliance-sensitive systems and move the rest in phases.

We use managed services like RDS and S3 – can they be moved?

Yes. Managed databases are moved to the equivalent managed service with us (PostgreSQL/MySQL/SQL Server) and S3 is replaced with S3-compatible object storage – your applications usually only need a new endpoint and new keys. Serverless functions require rebuilding, which is time-estimated in the assessment.

What happens to our old environment after the move?

It remains untouched until you have approved that everything works in the new environment. We then help you decommission it in a controlled manner – including documented deletion of data at the old provider, a GDPR requirement many miss.

How are our developers and their workflows affected?

Minimally. VMs, containers and databases work as before. CI/CD pipelines are repointed to the new environment – that's included in the migration. Kubernetes manifests and Helm charts are reused as-is.

Can you take over operations after the migration?

Yes – that's our service Managed EU Drift: patching, backup, 24/7 monitoring and NIS2 reporting from SEK 5,000/mo. 30 days of burn-in support is always included after the migration, whether or not you choose managed operations with us.

Start with a free assessment

One call is enough for us to give you an initial picture of your exit path – with no obligations.

Book a free Sovereignty Assessment See what managed operations cost
Next step in the journey

Managed EU Drift – compliance-ready operations in a Swedish data center

Learn more →