Enterprise DNA

Instead of Nintex Process Manager

Stop renting Nintex Process Manager. Own your process governance.

We build your version around how your team reviews and improves its procedures, map your Nintex records and run the system for you through Omni by Enterprise DNA.

Nintex Process Manager pricing is quoted through its sales team. Bring your renewal quote and compare the scope your business actually uses.

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

Look at the renewal

What sits behind the Process Manager agreement

Separate the software package from the work: keeping procedures current, owners accountable and improvements moving. Start with your actual quote.

layers

A package around your procedures

Nintex separates Process Manager into Essentials, Professional, Expert and Enterprise packages. Your quote depends on the package and scope.

users

Room for people and processes

Its licensing help describes usage limits and extra capacity. Check the capacity in your actual agreement before comparing your annual bill.

file-text

A place to document the work

Process Manager holds process documentation. Your own version keeps the procedure, responsible roles and review record together.

user-check

Ownership and improvement feedback

Nintex includes ownership and feedback tools. In your version, owners and unresolved improvements are records you can combine in a weekly review.

bar-chart-3

Views of process health

Nintex provides dashboards and reports. Your version answers questions across review dates, proposed changes and the improvement backlog you keep.

calendar

An ongoing software agreement

The vendor asks you to discuss pricing. Compare your renewal quote with the work your team needs, then scope a system you own.

Your own version

Make the process review answer your questions

Procedure control

An approved version that stays intact

Keep proposed changes separate until a reviewer records the approval.

  • check A named process owner and responsible roles
  • check Approved steps preserved when a new version is proposed
  • check Approval evidence and the next review date recorded together
  • check Pending safety changes shown beside overdue owner reviews

Owner reviews

A Monday review across the whole register

See where review work and unresolved improvements meet.

  • check Reviews due within thirty days
  • check Open improvements ordered by due date
  • check Owners compared by overdue review load
  • check Quiet records and missing owners flagged for attention

Improvement follow-up

Find waiting time with unfinished actions

Compare recorded procedure times with the improvement work already assigned.

  • check Active and waiting minutes from the approved steps
  • check High-priority open actions beside each process
  • check An owner and due date on each improvement
  • check Resolution evidence required before an action closes

Procedure evidence

Know which version people acknowledged

Use version-specific records and print the paperwork from the same approved content.

  • check Assigned readers checked against the current approved version
  • check New versions create fresh acknowledgement gaps
  • check Procedure sheets, review briefs and change records in your brand
  • check Retention review prompts with sources and clear limits

Make it yours

Design your own Nintex Process Manager replacement

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

2. What it runs

3. Make it fit

4. Your colour

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

forum

Process Governance for Claude Code

Connected to your own database

Which process reviews are due soon, and do they have overdue improvements?

PROC-001

Name
Receive bulk deliveries
Owner
Aroha
Review due
2026-10-06
Days to review
-7
Overdue improvements
1

PROC-002

Name
Approve supplier onboarding
Owner
Aroha
Review due
2026-10-23
Days to review
10
Overdue improvements
1

Ask it anything

Ten questions to ask your process records

These checks run on the demonstration records today. Your version can combine your own fields and review rules. Similar reporting may also be available in Nintex.

chat_bubble Which overdue process reviews also have overdue improvement actions?
chat_bubble Which pending safety procedure changes still need a control review?
chat_bubble Who has acknowledged an old version but not the current one?
chat_bubble Which processes combine the most waiting time with high-priority open actions?
chat_bubble Which owners carry the largest overdue process review load?
chat_bubble Which procedures have proposed changes while an older version remains approved?
chat_bubble Which process records have gone quiet for thirty days?
chat_bubble Which personal-information processes need their retention purpose reviewed?
chat_bubble Which imported records still need procedure content and approval?
chat_bubble What are the review dates, open improvements and missing read receipts for Monday?

Switching

How to switch from Nintex Process Manager

A move usually involves exporting your Process List, mapping and testing the register import, then checking records and separately mapping the history and content you choose to bring.

  1. 1

    Export your Process List

    Export the Process List from Nintex Process Manager as a CSV if your account allows it. If you cannot find that export, check with Nintex and use the export options available to your account. Review the exported headings before moving on. The import can preserve the original fields, but heading differences may need mapping.

  2. 2

    Test and load the register

    Run a test import before loading the records. The free version can bring in the Process List CSV as draft register records and preserve its original fields. Check the test results and any heading mappings, then load the records once you are satisfied with what will come across. The import does not bring procedure content, attachments, permissions or approval history across automatically.

  3. 3

    Review what the import reports

    Check everything the test import reports, including records or fields that need attention. Compare a sample of the draft records with the Nintex export and confirm that important details have landed in the right places. Resolve mapping issues before relying on the new register. Treat procedure content, attachments, permissions and approval history as separate items to map and reconcile.

  4. 4

    Run both systems briefly

    Keep Nintex Process Manager available while your owners check the imported register against the records they use. Confirm that key processes, owners and other important fields are present, and complete the separate mapping and reconciliation you need for procedure content and history. Use this short period to resolve discrepancies and agree that the new register is ready to use.

  5. 5

    Switch off Nintex Process Manager

    Once your owners have checked the register and resolved the outstanding migration work, agree when the new system becomes the one you use. Confirm that required procedure content, attachments, permissions and approval history have been handled as needed. Do not switch off Nintex Process Manager based on the register import alone. Close or end your Nintex service when your team is ready to stop using it.

construction

Where the real effort goes

The main work is usually mapping your own fields and rules, then deciding how much procedure content and history to bring across. The Process List import gives you draft register records, but procedure content, attachments, permissions and approval history need separate mapping and reconciliation. If you have Enterprise DNA install and run it for you, Enterprise DNA does this migration work with you.

Not ready for a call?

Get your Nintex Process Manager switch plan by email

We will send you the step-by-step plan for moving your business off Nintex Process Manager, 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, customise it, or have us run it

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo, run npm install, then npm run demo
  2. 2 Open it with Claude Code, Codex, OpenCode or Cursor
  3. 3 Ask for /weekly-review and inspect the fictional records
  4. 4 Read the switching guide and preview the Nintex CSV import
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer

  • check Your procedure fields, review rules and approval evidence
  • check Your Nintex exports mapped and reconciled
  • check A web front end or mobile workflow scoped around your team
  • check A different technology foundation 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 and connected through Omni by Enterprise DNA
  • check Your process register and review routines maintained
  • check Access controls, backups and evidence storage configured
  • check A team to operate the system and make agreed changes
Book a call

Questions

Instead of Nintex Process Manager, answered

What does the free version cover? expand_more

A process register, procedure revisions, owner reviews, improvement actions and version-specific acknowledgements. It also produces branded procedure sheets and internal review briefs. The code is free under an MIT licence. Hosting and agent use have separate costs.

Can we bring our Nintex records across? expand_more

Yes. The free version imports the Process List export as draft register records and preserves the original fields. Check the exported headings and do a test run first. Procedure content, attachments, permissions and approval history need separate mapping. Enterprise DNA can scope and complete that migration with you.

How do we compare the cost with Nintex? expand_more

Use your renewal quote. Nintex currently directs pricing enquiries to sales, and its licensing help describes packages with different features and limits. We scope your version around the work you need, for one setup fee and then a retainer.

Can our team have a screen or phone access? expand_more

Yes. Enterprise DNA can build a web front end, mobile capture and agreed connections around your records. We scope those needs with the migration so your operators get the access and working methods they need.

Does an approval prove the procedure is compliant? expand_more

No. The checks flag missing or due evidence for an owner to assess. Approval records and acknowledgement references do not prove safety, legal compliance or competence. Your responsible people still review the procedure and its supporting evidence.

Own the procedures your business runs on

Book 30 minutes with Sam. Bring your Nintex renewal quote and one process your team struggles to keep current. We will work through the records, migration and operation your version needs.

Book a call Get the free version

Process Governance for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Nintex Process Manager?

Get your version built