# IFS Cloud rollout to the next site or country

In rollout mode Implementer reuses the design you already approved for the next site or country, records only what is local, and gives each wave its own cutover plan, gates and handover.

## How does a rollout run in Implementer?

Work on the delta, not on the whole project again.

1. **Set the project mode to rollout**

   The project gets its own gates, schedule and baselines.

2. **Keep what is common**

   The approved design, Book of Rules and standard CRIM decisions stay the reference for the new site.

3. **Record what is local**

   Local legal and process differences, interfaces, data groups and users become rows with owners.

4. **Cut over per wave**

   Each wave or site has its own cutover plan, rehearsals, readiness review and handover.

![Cutover plan page with runbook tasks, rehearsals and go/no-go checkpoints](https://implementer.ifs-erp.com/site-assets/img/en/idk-20-cutover.png)

*Cutover page in the demo project, demo data*

## What is rollout mode?

Rollout mode is the project mode in Implementer for extending an IFS Cloud solution that is already live to another site, country or business unit. It keeps the same registers and the same way of changing state as a [new implementation](https://implementer.ifs-erp.com/en/new-implementation.md), but the work is the delta between the template solution and the new site. Compare it with [BAU and Evergreen](https://implementer.ifs-erp.com/en/bau-evergreen.md), which covers updates after go-live.

## Why is a rollout not just a small implementation?

A rollout looks small and goes wrong in the same places as the first project, only faster. The design is assumed, so local differences slip in through e-mail: another tax rule, another interface, another data source. In Implementer every local difference is a CRIM object, an interface row or a Book of Rules exception with an owner and a decision trail, so the change to the shared design is visible before anyone approves it. See [problems](https://implementer.ifs-erp.com/en/problems.md) for how scope and migration gaps are closed.

## What does each wave get?

- A **cutover plan** with runbook tasks (freeze, go/no-go, point of no return, switches, rollback), rehearsals and their results.
- A **migration scope** for the site: data groups, migration objects, load cycles, reconciliation by object and sign-off per data group.
- A **test cycle** with scenarios and a verdict.
- A **readiness review** with 42 criteria and a Go, Go with conditions or No-go decision.
- A **handover** to support, with hypercare, per site or module.

## What does it cost?

A rollout licence is EUR 6,000 per project and year for up to 25 named users, net, plus VAT. A further environment is EUR 1,500 one-off. A [pilot](https://implementer.ifs-erp.com/en/pilot.md) can run on one wave. See [pricing](https://implementer.ifs-erp.com/en/pricing.md).

## What does it not do yet?

Copying a policy or a set of decisions from a template project into a new rollout project is not automated yet. You enter the shared decisions once per project. The IFS Cloud connection stays read-only, as described on [security and trust](https://implementer.ifs-erp.com/en/security-and-trust.md).

## How do you see it?

Open the [live demo](https://implementer.ifs-erp.com/login) on demo data, or [book a scoping call](https://www.ifs-erp.com/en/book-time-with-me) and describe your next site.

Last updated: 13 November 2026

## Ready for a pilot?

A 30-minute scoping call and a 15-minute demo on demo data.

[Book a scoping call](https://www.ifs-erp.com/en/book-time-with-me)
