# migration runbook

GLOSSARY, read 10 Nov 2026

**Definition.** A migration runbook is the step-by-step document for the move: owners, dates, commands, checks and the stop rule. Nucleus describes its own playbook as three moves: map current connectors and workflows, run in parallel, and cut over once results are validated.

Write the runbook around the objects in the export: assets, vulnerabilities, findings, fixes, tags, users, roles, reports and tickets. Each gets an owner, a source, a target and a check.

A vendor playbook covers the vendor's side. Your runbook also covers the scanners, the ticketing system and the people who read the reports.

## A sourced example

Nucleus's Kenna page, last modified 2026-08-25, describes a migration playbook that maps connectors and workflows, runs in parallel with Kenna, then cuts over, and offers an on-demand migration webinar.

## Related terms

- [parallel run](/glossary/parallel-run/)
- [cutover](/glossary/cutover/)
- [connector parity](/glossary/connector-parity/)
- [rollback plan](/glossary/rollback-plan/)

## Sources

- Source for the example: migration runbook: https://nucleussec.com/kenna-end-of-life-upgrade-to-nucleus/ (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/glossary/migration-runbook/
