Migrating to STACKIT from the Netherlands: what changed and how to prepare

What changed in the Netherlands

Three developments, each with the source it rests on.

1. 01

   Framework agreement for central government

   On 23 April 2026 the Dutch government published that a framework agreement with STACKIT is signed and in effect. SLM Rijk negotiated it. Central government organisations (rijksorganisaties) can buy STACKIT cloud services on agreed terms without negotiating their own contracts.

2. 02

   Terms named to parliament

   In an answer to parliamentary questions, received on 9 June 2026, State Secretary Aerdts names the terms. All data, including personal data, is processed exclusively within the European Economic Area (EEA). SLM Rijk will check compliance by exercising the audit right in the contract. There are agreements on (early) termination of the contract when ownership changes, for example if STACKIT is acquired by an owner outside the EEA. That is a contract safeguard, not news of a takeover: the answer mentions no actual or planned acquisition.

3. 03

   KPN European Sovereign Cloud, powered by STACKIT

   On 28 May 2026 KPN and Schwarz Digits, the IT and digital division of the Schwarz Group, announced this offering for the Dutch market. KPN data centres in the Netherlands host it. The release expects the Dutch region from mid-2027, so a Dutch STACKIT region is not available yet, and it says the offering is sold exclusively through KPN and its partners.

4. 04

   Reported: De Nederlandsche Bank

   Techzine reports that De Nederlandsche Bank, the Dutch central bank, signed a deal with STACKIT to reduce its dependence on American cloud companies. The article names no primary source and gives no scope, value or duration. We have not verified the report against a primary source, so read it as a report.

What this means for your organisation, and what it does not

• An option, not a duty

  The answer is plain: “Er geldt geen afnameverplichting”, there is no purchase obligation. SLM Rijk made no agreements on purchase; that decision lies with the organisations themselves. Signing the agreement does not mean that any part of central government has actually bought STACKIT services.

• Eligibility is yours to check

  The answer speaks of central government organisations (rijksorganisaties) and does not address other public bodies. A central government organisation that wants to buy cloud services can ask its purchasing organisation how to arrange this. If yours is not one, or you are unsure, put the question to your procurement and legal teams. StackToIT gives no procurement advice.

• No Dutch region yet

  Until the Dutch region exists, a workload you move to STACKIT does not run in a Dutch STACKIT region. The target region is one of the questions a StackToIT run asks you to answer, so settle it early.

• No savings and no certification implied

  None of the sources states cost savings. A framework agreement or the name of a sovereign cloud is not a compliance certification of your own workload, and StackToIT makes neither claim.

• Independent tooling

  StackToIT is an independent product. It is not affiliated with STACKIT, KPN, SLM Rijk or the Dutch government, and none of them endorses it.

How to prepare a migration from AWS, Azure or VMware

The order is the same for every source. What differs is the input you start from.

1. 01

   1. Take stock of what you run

   Collect the Terraform of your AWS or Azure estate with its variable files, or an RVTools export of your VMware estate. A variable without a value leaves a unit without a draft, so give the tool the same files your pipeline uses.

2. 02

   2. Classify every resource

   Find out which services have a like-for-like target on STACKIT and which need work. In the AWS guide's run, for example, DynamoDB has no compatible service and Lambda has no generally available function service, so both change the design.

3. 03

   3. Settle the open decisions early

   Target region, exposure to the internet, sizes, boot images and the method of data movement are decisions, not defaults. Give each one an owner before you build.

4. 04

   4. Prepare the landing zone

   Before the first apply the organisation and project on STACKIT must exist with their networks and access. A run lists what you have to provide.

5. 05

   5. Plan data and cutover

   For every stateful unit choose a mechanism by data size, change rate and tolerated downtime. Record the rollback limit before the window and name who decides go or rollback.

6. 06

   6. Review, then apply with your own pipeline

   An architect reviews the draft, the owner approves, and a person applies it. Move in waves and keep the source running until the switch is proven.

Which input to start from

The guides show real StackToIT output on small example estates.

What StackToIT contributes

StackToIT prepares the migration and stops before deployment.

• Assessment

  Every migration unit gets a target, a class, a confidence, findings and reasons. What is unknown stays open instead of being guessed.

• Target architecture

  Resources are mapped to STACKIT services, and architecture diagrams are generated.

• Terraform drafts

  STACKIT Terraform drafts for the units that have a target, for your architects to review.

• Plan and decisions

  A step-by-step plan with migration sequencing, dependencies and risks, and a decision register that names who must answer what.

• Runs on your files

  StackToIT runs on your own machine or in your CI. It reads files and writes files, applies nothing, and your own pipeline stays in charge.

Questions Dutch organisations ask first

Sources

• Answer of State Secretary Aerdts on the STACKIT framework agreement (Aanhangsel Handelingen 2025-2026, nr. 2189)
• Dutch government secures deal with European cloud platform STACKIT (nldigitalgovernment.nl)
• Raamovereenkomst Rijk van kracht voor Europese cloud (iBestuur)
• KPN and Schwarz Digits launch European Sovereign Cloud for the Netherlands (STACKIT)
• Dutch government selects STACKIT as its cloud alternative (Techzine)