Enterprise DNA

Instead of HaloPSA

Stop renting HaloPSA. Own your MSP system.

We build your version around how you support clients and charge for the work. We map your HaloPSA exports, check the records and run your system through Omni by Enterprise DNA.

Halo displays a UK rate of £66 per agent per month billed annually, or £792 per agent per year at that rate. Your quote depends on region and licence needs, with bespoke onboarding separate.

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 your subscription covers

A complete platform, charged by agent

Halo includes its modules in one price. The choice is whether to keep renting that platform or own a narrower system built around your MSP.

paid

Licensed staff access

The subscription covers the team managing tickets and projects. Customer and end-user portal access is free under Halo’s published model.

support_agent

The service desk

Ticket handling and service deadlines sit inside Halo. Your own version starts with the records and reviews your support business needs.

description

Agreements and billing

Halo includes contract and billing functions. Your own agreement rules can be built around the device, user or flat arrangements you actually sell.

devices

Assets and projects

Halo includes asset and project management. The free base keeps device ownership, warranty dates and project time budgets together.

analytics

Reporting

Halo offers custom reporting and CSV exports. An owned database gives you another way to ask questions and change the analysis yourself.

settings

Onboarding

Halo states onboarding is required at a bespoke cost. Enterprise DNA scopes the records, rules and connections for your version before the switch.

Your working MSP desk

See the work, the agreement and the next action together

Service delivery

Start the day with the right tickets

Open work is ordered by priority and the recorded resolution deadline. The review also keeps historical breaches visible.

  • check First-response and resolution deadline checks
  • check Unassigned tickets alongside the named technicians
  • check Stale work with no activity for three days
  • check Project time against its budget and due date

Commercial review

Check the month before invoicing

Prepare a billing proposal from the current agreement quantities and approved time. Review it before invoicing in your accounting system.

  • check Device, licensed-user and flat monthly arrangements
  • check One included-time allowance for each client
  • check Pending approval shown before a proposal can be saved
  • check Frozen amounts and time references for later review

Client relationships

Bring evidence to the next discussion

Client reviews join open work, service breaches, unbilled minutes and device concerns. Add your own questions as the business changes.

  • check Renewal reviews due within the next 60 days
  • check Old device observations and expired warranties
  • check Branded service and renewal review documents
  • check A client discussion draft saved for your review

Your records

Keep the rules within reach

The free version includes a documented migration process and checks for missing privacy incident evidence. Your responsible person makes the decisions.

  • check Mapped Halo CSV reports with a test run before import
  • check Repeated identical imports skip existing records
  • check Incident assessments and notification evidence in one place
  • check Branded reports and complete record exports

Make it yours

Design your own HaloPSA replacement

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

2. What it runs

3. Make it fit

4. Your colour

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

forum

MSP for Claude Code

Connected to your own database

Which agreements need a renewal discussion in the next 60 days?

Harbour Accounting

Me re
Harbour managed support
Newal_due en
2026-09-23
Ds_on
2026-10-28

River Engineering

Me re
River support block
Newal_due en
2026-11-27
Ds_on
2026-12-27

Ask it anything

Questions your MSP can answer from its own records

Halo supports custom reports too. These are ten questions the free version answers today, with rules you can inspect and change.

chat_bubble Which agreements need a renewal discussion in the next 60 days?
chat_bubble Which open tickets have missed a recorded service deadline?
chat_bubble Which tickets have had no activity for three days?
chat_bubble Which technicians have unassigned or urgent work in their queue?
chat_bubble Which billable entries are still waiting for approval?
chat_bubble Which client has unbilled work and overdue device checks?
chat_bubble Which projects are late or over their time budget?
chat_bubble Which active devices have old observations or expired warranties?
chat_bubble What does this month look like under our current agreement quantities?
chat_bubble Which privacy incidents lack assessment or notification evidence?

Switching

How to switch from HaloPSA

Moving off HaloPSA means exporting what your account allows, mapping those records into the new database, checking the import before you trust it, and running both systems side by side until you're sure nothing is missing.

  1. 1

    Export your HaloPSA records

    In HaloPSA, export what your account allows, usually CSV or Excel report exports, for clients, agreements, devices and tickets. Check with HaloPSA if you're unsure which reports you can pull. This export is the raw material the new system reads, so get as much of the history as you plan to keep before you move on.

  2. 2

    Map your fields and load them

    The import needs your actual HaloPSA column headings mapped to the new fields, done once for your setup. Run a test import first, on a copy or test database, before you touch your real records. Enterprise DNA does this mapping and test run for you if they install and run it on your behalf.

  3. 3

    Check what the import flags

    The import is deliberately strict. Unknown headings or missing references stop the whole import, exact repeats are skipped, and rows that changed since the last run are held for review rather than overwritten. Attachments, messages, detailed action history and past invoice allocations do not come across automatically, so decide what you need to handle separately.

  4. 4

    Run both systems side by side

    Once the import is clean, keep HaloPSA running alongside the new database for a short period. Use both for real work, compare agreements, device records and billing proposals against what HaloPSA shows, and confirm nothing important was left behind before you rely on the new system on its own.

  5. 5

    Switch off HaloPSA

    When you're confident the records match and your team works from the new database day to day, cancel HaloPSA. Keep a copy of your HaloPSA export on file in case you need to check something later, and keep any separately scoped mail intake or monitoring connections running until they've been tested against the new setup.

construction

Where the real effort goes

The real work is in mapping your own HaloPSA headings, agreement rules and billing figures into the new fields, and deciding how much history to bring across, since attachments, messages, detailed action logs and past invoice allocations need separate handling. Enterprise DNA handles this mapping and the test import for you if they install and run the system on your behalf.

Not ready for a call?

Get your HaloPSA switch plan by email

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

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

Open source

Do it yourself

Free source

  1. 1 Clone the repo, run npm install and npm run demo.
  2. 2 Open it in Claude Code, Codex, OpenCode or Cursor and read AGENTS.md.
  3. 3 Map your HaloPSA CSV headings and preview the import.
  4. 4 Reconcile agreements, deadlines and time before switching.
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer

  • check Your agreement rates, fields, service rules and approvals
  • check Your HaloPSA exports mapped and reconciled
  • check A web front end or mobile entry where your team needs one
  • check A different technology stack where your requirements call for it
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a monthly retainer

  • check Installed and operated through Omni by Enterprise DNA
  • check Mail intake and monitoring connections scoped and tested
  • check Access, backups and ongoing support agreed for your business
  • check Changes as clients, agreements and service processes change
Book a call with Sam

Questions

Instead of HaloPSA, answered

Halo already includes the modules. Why change? expand_more

Ownership and fit. Halo is a full platform with custom reporting. This gives you a smaller service and commercial base you can change. We build your version around the agreements, reviews and connections your MSP uses.

Will our HaloPSA history come across? expand_more

Halo supports report exports to CSV. We map the actual headings and linked records, run a test import and reconcile the result. Attachments, messages, detailed action history and past invoice allocations need separate migration work. The free version includes the mapping guide and a repeat-safe import.

Can we trust the billing figures? expand_more

The free version calculates a monthly proposal from current device or user quantities, a flat charge where used, and approved time above the allowance. It saves the calculation for review. Tax, credits, partial-month adjustments and supplier licence charges need your agreed rules before invoicing. We test those against your existing bills.

What about our portal, mail intake and monitoring? expand_more

We scope and build the connections and working screens your team needs as part of your version. Keep the existing intake and monitoring process until those connections and the migration have been tested together.

What do we pay Enterprise DNA? expand_more

One setup fee, then a retainer for the agreed customisation and operation. The source is free to use yourself. Hosting, subscriptions for the coding assistant and ongoing support are separate costs. Sam scopes the work with you before you commit.

Make the next MSP system yours

30 minutes with Sam. Bring your HaloPSA bill, a sample agreement and the review you do every week. We look at the records, the connections and what your own version needs to do.

Book a call with Sam Get the free version

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

Done paying for HaloPSA?

Get your version built