Migration Program - Board Community

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

f31f9ae7-53f5-44dd-bb00-7d7a942140c3 (1).jpg

Migration today is reactive. It needs to become an operating model.

Migrating to the Latest Release is no longer a maintenance task — it unlocks security posture and a new generation of AI capabilities. The Migration Program has been established to support customers in transitioning from legacy Board versions to the latest release, through a standardized and value-driven approach.

Migration patterns

Based on your current setup, find the right path to B15 — with the strategy, roles and steps that apply to you.

0b55798a-924e-4888-b6a5-0637e433571b (1).png

Migration strategies

Two approaches apply across all migration paths. The right one depends on your current version.

⏱Time-boxed upgrade	🔄Application-based migration
Applies to: B14.5, B14.x A governed, assertive upgrade model based on predefined time-bound windows — ensuring fast and controlled alignment to the latest version.	Applies to: B12.6, B12.x, Below B12* Migration is highly application-dependent. Before anything reaches the customer, a mandatory internal pre-validation phase ensures functional equivalence and UI stability.
How it works Upgrade windows are defined and communicated in advance. The customer sandbox is automatically upgraded first, followed by Test/UAT (customers have two weeks to validate), then Production — migrated according to the assigned window. Each phase has a fixed maximum duration and issues must be raised within it.	How it works The Migration Coordinator collects test cases and scripts with the customer. The Migration Team then runs those scripts on the new version, verifies behaviour and performance, and validates all screens before handing the sandbox to the customer for full regression testing.
Who does what Migration Coordinator manages communication and coordinates go-live. The Technical Migration Specialist executes the upgrades and supports regression testing. The customer nominates a Board Champion and confirms Production readiness.	Who does what Migration Coordinator collects app info and test scripts. The Technical Migration Specialist executes the pre-test. The customer provides test scripts, runs regression, and formally validates before Production.