Enterprise DNA

Instead of Onspring

Stop renting Onspring for continuity. Own your recovery planning system.

We build your continuity system around the services your business must keep running. We map your Onspring records, bring them across and run your version through Omni by Enterprise DNA.

Onspring quotes prices privately. User or product licences are separate from its platform level.

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

What the Onspring bill covers

A licence model, a platform level and the work around them

Onspring combines configurable business applications with its hosted platform. Check which parts your continuity team uses before deciding what to replace.

group

Named users or licensed products

Choose user licensing, product licensing with unlimited employee users, or a hybrid. The choice changes the scope of your quote.

layers

A separate platform level

Bronze, Silver, Gold and Platinum sit alongside the user or product licence.

storage

Storage and extra environments

Higher levels include more storage and development environments. Extra storage and non-production instances can also be purchased.

support_agent

Support coverage

Support coverage varies by platform level. Platinum includes round-the-clock support.

school

Training capacity

The platform levels include different numbers of training seats. Additional training can be purchased.

fact_check

A configured continuity programme

Impact analysis, recovery plans, exercises and reporting still need your owners, objectives and evidence. These are the records this free version centres on.

What you own instead

Recovery decisions tied to the evidence

Priorities

Know what has to recover first

Start with the business service and its agreed recovery deadline, then examine the dependencies beneath it.

  • check Services ranked by recovery objective
  • check Separate limits for downtime and data loss
  • check Dependencies whose recovery time exceeds the service target
  • check Shared suppliers and systems across several services

Plans

Keep approval tied to the current plan

A changed recovery instruction needs a fresh exercise and another person to approve it.

  • check Activation, recovery, communication and contact roles together
  • check Version changes clear earlier approval
  • check Reviews and exercises have named owners and dates
  • check Printable recovery plans carry their version and approval state

Exercises

Measure the result, then close the gaps

Compare measured recovery with the objectives in force for that exercise. Keep the failure and the lesson visible.

  • check Recovery time and data loss checked independently
  • check Historical results retain their original targets
  • check Corrective actions linked to the exercise
  • check Completion needs evidence and another named person

Weekly review

Ask the question your meeting needs

Read missing plans, stale evidence and overdue actions together. Onspring also offers configurable reporting; your owned version lets you change the questions around your own records.

  • check Plan reviews due in the next month
  • check Overdue work grouped by owner
  • check A weekly review drafted from current records
  • check Branded reports generated from the same database

Make it yours

Design your own Onspring replacement

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

2. What it runs

3. Make it fit

4. Your colour

Your business · your Onspring 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 Onspring 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 Business Continuity for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Business Continuity for Claude Code

Connected to your own database

Which services must recover first?

Customer dispatch

Ner cr
Mere
Iticality rt
critical
O hours rp
4
O hours ma
1
X outage hours
8

Client advice

Ner cr
Aroha
Iticality rt
high
O hours rp
8
O hours ma
4
X outage hours
24

Supplier ordering

Iticality rt
normal
O hours rp
24
O hours ma
8
X outage hours
48

Ask it anything

Questions Onspring cannot answer

Every one of these is a real question the demo answers today. Yours will be different, and that is the point.

chat_bubble Which services have the shortest recovery deadlines?
chat_bubble Which dependencies take longer to restore than their service allows?
chat_bubble Which supplier or system supports more than one service?
chat_bubble Which services have no recovery plan?
chat_bubble Which current plan versions have never been exercised?
chat_bubble Which exercises missed the data loss target?
chat_bubble Which high priority corrective actions remain open?
chat_bubble Which owner carries the most overdue actions?
chat_bubble Which plans need review in the next month?
chat_bubble Who changed an objective or approved a plan?

Switching

How to switch from Onspring

A move usually involves exporting four continuity report sets, mapping their fields, checking a test import, then running the new register alongside Onspring before you retire it.

  1. 1

    Choose the records to move

    Start with Onspring report data for your services, plans, dependencies and actions. Decide how much history you need to bring across. Export what your account allows, usually CSV or Excel, and check with Onspring if you are unsure which formats are available. The import also supports saved report data as JSON.

  2. 2

    Rehearse the import

    Map the report columns to the fields in the new register before loading anything. The import can rehearse saved Onspring report data without writing records, so start with that test run. When you are ready, load the mapped records into the database. If you have Enterprise DNA run the migration, they handle this mapping and import work with you.

  3. 3

    Resolve the reported gaps

    Review what the test run reports, then compare the source IDs and record counts with your Onspring reports. Fix mapping problems or source records that need attention, and rehearse again until the results make sense. Check historical exercise evidence, attachments and permissions separately, because they need their own reconciliation.

  4. 4

    Run both side by side

    Keep Onspring available for a short period while you use the new register for continuity records. Compare the services, plans, dependencies and actions in both systems, and check that the people responsible can review and approve the records they own. Agree where approved plans will be held and how staff will reach them during an outage.

  5. 5

    Retire Onspring

    Switch off Onspring only after you have reconciled the records you chose to move and the responsible people have reviewed the new plans. Make sure you have separately dealt with any history, attachments, permissions or other Onspring modules you still need. Keep the source records available if you need to verify anything after the switch.

construction

Where the real effort goes

The loading is only part of the work. Most effort usually goes into mapping your own fields and rules, deciding how much history to bring across, and reconciling items such as exercise evidence, attachments and permissions. If Enterprise DNA runs the migration, they do the field mapping and record comparison with you. The history and scope you choose determine what else needs checking.

Not ready for a call?

Get your Onspring switch plan by email

We will send you the step-by-step plan for moving your business off Onspring, 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

Choose who builds and runs your version

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo, run npm install and npm run demo
  2. 2 Open it in Claude Code, Codex, OpenCode or Cursor
  3. 3 Try /attention and inspect the fictional demo records
  4. 4 Save your Onspring report data, map the fields and rehearse the import
Get it on GitHub

Built around your business

We customise it

Setup scoped around your business

  • check Your recovery rules, approval roles and report formats
  • check Your Onspring records mapped and reconciled
  • check A web front end or a different stack if you need one
  • check Team access, document access and connections agreed before rollout
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed and operated through Omni by Enterprise DNA
  • check Backups, access and ongoing changes managed for you
  • check Your continuity coordinator involved in testing and cutover
  • check A person to ask when the next exercise changes the plan
Book a discovery call

Questions

Instead of Onspring, answered

Does this replace every part of Onspring? expand_more

This free version covers continuity planning records: services, plans, dependencies, exercises and corrective actions. We agree the rest of your required workflows, team access and connections before building your version.

Can we bring our Onspring history across? expand_more

Yes, for the supported records. Your administrator saves the relevant report data, then we map its fields and compare the counts. Existing source records are recognised on repeat imports. Historical exercise evidence, attachments, permissions and other modules need separate reconciliation.

Does a passed check mean our business is compliant? expand_more

It means the implemented record checks passed. They flag missing instructions, late reviews, missing exercises and unresolved actions using cited guidance and your chosen rules. The responsible people still approve the plan and confirm the obligations that apply to your business.

What about staff screens and access during an outage? expand_more

We build the team access and screens your organisation needs. The free base produces printable review copies. We agree where approved plans are held and test that staff can reach them during an outage as part of your setup.

What do we pay Enterprise DNA? expand_more

One setup fee, then a retainer for a version we run for you. The scope covers your records, rules, connections and ongoing operation. The base is free to install and change yourself, with your own hosting and coding assistant costs.

Put your next continuity review on records you own

Spend 30 minutes with Sam. Bring your Onspring bill and one recovery plan. We look at what your team uses, what needs to come across and what your own version should do.

Book a discovery call Get the free version

Business Continuity for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Onspring?

Get your version built