Enterprise DNA

Instead of Cutover

Stop renting Cutover. Own your migration runbooks.

We build your version around your change windows and approval rules, bring your Cutover records across, and run it for you. Your operators keep control of every production change.

Cutover prices by tailored quote. Its current pricing page lists team size, usage and advanced functionality as factors.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

The Cutover bill

Price the work you need, then decide what to own

Cutover asks for a quote rather than publishing a current price. Compare that quote with the work your team needs: the coordination record, the connections and the people running it.

groups

Team size

The vendor asks how many people will actively use Cutover. Your owned record keeps a named owner against each step.

account_tree

Automation usage

Cutover asks about automation needs. This free base records human-operated work. We scope automated actions separately with you.

link

Connected platforms

Integrations form part of the quote discussion. We identify which connections your version needs before building them.

shield

Security functionality

The vendor asks about advanced security needs. Your own installation needs access, hosting and backup arrangements matched to your business.

settings

Configuration and support

Cutover describes support and professional service options. Compare those with having Enterprise DNA configure and operate your version.

assignment

Your recurring change record

Keep plans, rehearsal results and handover evidence in your own database. The record remains yours when a delivery engagement ends.

Your version

A plan that remembers which evidence belongs to it

Prepare

Find the missing owner before the change window

Read every planned step alongside its owner, duration and predecessor. Look across migrations when one team has too much work.

  • check Unassigned acceptance steps appear in the attention list
  • check Critical steps show missing rollback instructions
  • check Planned dates show overdue preparation
  • check Owner workload combines planned minutes across runbooks

Rehearse

A pass applies to the plan that was tested

Every rehearsal keeps its own copy of the plan. Changes require fresh evidence before the new version is ready.

  • check Earlier task wording stays with the old run
  • check A later failed rehearsal supersedes an earlier pass
  • check A changed step makes earlier readiness out of date
  • check Each supplied outcome records its actor and evidence

Decide

Keep the go or no-go decision with its reasons

The change owner supplies the decision. Passing checks prepare the record for review and never decide on the owner’s behalf.

  • check A live record needs a current go decision
  • check A later no-go pauses live task recording
  • check Predecessors must be complete before the next task is recorded
  • check Abandoned runs close as failed and retain their evidence

Handover

Answer the next review from the same record

Produce a change plan, decision record and run evidence in your own brand. Extend the record around your way of delivering migrations.

  • check Compare old rehearsal revisions with today’s plan
  • check Draft the handover with recorded outcomes
  • check Read the week, workload and rehearsal snapshots
  • check Export original fields, decisions and history together

Make it yours

Design your own Cutover replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Cutover. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your Cutover replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your Cutover data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the demo data that ships with Cutover Runbooks for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Cutover Runbooks for Claude Code

Connected to your own database

Which steps need attention before the migration?

MIG-01

De ti
T1
Tle ow
Confirm restore evidence
Ner st
Mara Chen
Ream re
Preflight
Ason
Critical task has no rollback; Planned date overdue

MIG-01

De ti
T3
Tle ow
Record owner acceptance
Ream re
Handover
Ason
No owner

MIG-02

De ti
R1
Tle ow
Check reporting extract
Ner st
Ari Patel
Ream re
Preflight
Ason
Planned date overdue

Ask it anything

Ten questions your owned runbook answers

These questions are supported by the working demo. They show the record you can own, rather than claiming the incumbent cannot answer them.

chat_bubble Which migrations lack a current passing rehearsal?
chat_bubble Which critical steps have no rollback instructions?
chat_bubble Which acceptance steps still need an owner?
chat_bubble What is the longest chain using planned task durations?
chat_bubble Who carries the most planned work across migrations?
chat_bubble Which tasks have completed predecessors?
chat_bubble Which rehearsals refer to an older plan?
chat_bubble Who changed this step, and what did it say before?
chat_bubble Which records need a retention review?
chat_bubble What evidence was supplied for each task in that run?

Switching

How to switch from Cutover

The move involves exporting your task records, mapping them into a new plan, checking the imported data and running both systems side by side before switching.

  1. 1

    Export your Cutover records

    Export all Cutover tasks as a CSV, using the export path available to your account. The importer uses task IDs, titles, teams, durations, due dates and predecessors, and needs the export timezone specified. If your account offers different export options, check with Cutover. Attachments, historical approvals and integrated actions are not brought across automatically, so identify those separately.

  2. 2

    Preview, then import

    Start with the import preview before saving records. It creates a new destination plan and its tasks together, and keeps the original columns with the imported records. Check that the preview uses the right export and timezone, then load the records. If the preview does not match what you expect, pause and resolve the issue before importing.

  3. 3

    Review the import results

    Check the imported task and dependency counts against your Cutover export, then review anything the import flags. It rejects broken dependencies and dependency cycles. If source rows have changed, their mapping needs review. Check attachments, historical approvals and integrated actions separately, since they need their own mapping and checks and do not become active behavior through the import.

  4. 4

    Run both systems side by side

    Keep Cutover available while your team uses the new records for an agreed short period. Compare the plans, owners, dependencies and evidence your operators need, and check that the team can follow the new process. The new system records coordination, decisions and evidence. It does not execute infrastructure changes, so operators still perform those actions and a human makes the go or no-go decision.

  5. 5

    Switch off Cutover

    Once your team has checked the records and agreed that the new process is ready, switch off Cutover according to your account and internal process. Keep the exported records and any separately mapped material you need for reference. The imported task data does not automatically carry over attachments, historical approvals or integrated actions, so confirm how those records will be retained before you close out Cutover.

construction

Where the real effort goes

Most of the work is usually mapping your own fields and change rules, then deciding how much history to bring across. The task export covers the current plan structure, but attachments, historical approvals and integrated actions need separate mapping and checks. If Enterprise DNA runs the system for you, Enterprise DNA brings across the agreed records and fits the rules to your change process.

Not ready for a call?

Get your Cutover switch plan by email

We will send you the step-by-step plan for moving your business off Cutover, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Do it yourself, have it customised, or have it run for you

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo, install Node and run npm install
  2. 2 Run npm run demo, then open it in Claude Code, Codex, OpenCode or Cursor
  3. 3 Export Cutover tasks to CSV and preview the import with the export timezone
  4. 4 Review the mapped owners, dependencies and rollback steps before rehearsing
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer for ongoing work

  • check Your change rules, owners, fields and acceptance evidence
  • check Your Cutover export mapped and reconciled
  • check Your documents, web front end and agreed connections
  • check A different technology stack when your business needs it
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed with agreed access and backup arrangements
  • check Weekly reviews and handover drafts prepared from your records
  • check Maintained as your delivery process changes
  • check Run through Omni by Enterprise DNA, beside the rest of your business
Book 30 minutes with Sam

Questions

Instead of Cutover, answered

Is this the whole Cutover platform? expand_more

The free version owns the runbook, dependencies, rehearsal record, human decisions and evidence. It coordinates work that your operators perform. It does not execute infrastructure changes. Enterprise DNA scopes your required automation, connections, permissions and web front end as part of your version.

Can we bring our Cutover runbooks across? expand_more

Yes. Cutover documents a task export in its help centre. The free importer reads task IDs, titles, teams, durations, due dates and predecessors from a complete export, with the export timezone specified. Original columns stay with the records. Attachments, historical approvals and integrated actions need separate mapping and checks.

What happens when somebody changes the plan after rehearsal? expand_more

The plan gets a new revision. Earlier runs retain their original steps and evidence, while readiness for the new plan requires a fresh passing rehearsal and go decision. A failed later rehearsal does not borrow an earlier pass.

Does a green result mean the migration is safe or compliant? expand_more

It means the recorded plan clears the defined checks. The software cannot verify an external backup or prove a supplied result happened. A human owns the change decision. The record checks reference published change-control guidance, and we fit your rules to your obligations.

What do we pay Enterprise DNA, and who owns the records? expand_more

One setup fee, then a retainer for the work agreed with you. Your runbooks, evidence and history stay in a database you own. We review your current Cutover quote and delivery needs with you before defining the work.

Put your next migration plan beside your software bill

Spend 30 minutes with Sam. Bring a Cutover quote and one representative runbook. We look at the records, the change rules and the connections your team needs, then show what an owned version would involve.

Book 30 minutes with Sam Get the free version

Cutover Runbooks for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Cutover?

Get your version built