Appearance
OpsMerge vs Autotask
A real PSA without the portfolio pressure.
Autotask is a mature PSA with deep ITIL workflows. It's also now part of the Kaseya portfolio alongside Datto RMM, BMS, VSA and IT Glue, which means roadmap priorities shift with portfolio strategy. OpsMerge gives you the PSA-first posture without the multi-acquisition baggage.
Autotask is a serious PSA. The workflow engine is deep, the ITIL ceremony is real, the contract management is sophisticated. For MSPs that built their operations on Autotask over the last decade-plus, the depth pays back. We're not going to pretend our PSA matches it on every workflow customisation surface, we don't, yet.
What we offer is a different trade-off. One vendor, not a portfolio. One bill that includes the RMM, PSA and billing, not three SKUs that Kaseya stitched together post-acquisition. Public GBP pricing at GA, not sales-gated quotes that change with the wind of portfolio repositioning. And cell-based data residency so EU and UK MSPs aren't second-class.
Autotask is the right answer if your operations depend on ITIL ceremony depth. OpsMerge is the right answer if you want a single vendor, public pricing and an MSP-first roadmap.
Feature-by-feature
| Capability | OpsMerge | Autotask | Notes |
|---|---|---|---|
| PSA depth | Fit for SMB MSPs | Deeper | Honest concession, Autotask has decade-plus head start on PSA depth |
| RMM on the same platform | Yes | Via Datto RMM | Different SKU under same parent (Kaseya) |
| Asset-based auto-billing | Yes | Yes | Both auto-count; OpsMerge live agent count, Autotask via integration |
| Void with full reversal | ✓ | Partial | OpsMerge: one-action CDR / credit / period unwind |
| Public pricing | ✓ | ✗ | Autotask is sales-gated |
| Single vendor (not a portfolio) | ✓ | ✗ | Autotask sits in Kaseya alongside Datto RMM, BMS, VSA, IT Glue |
| Region-based data residency | Yes | Optional | OpsMerge: EU and US regions live, AP on the roadmap |
| ITIL ceremony (CAB, KEDB, service catalogue) | On the backlog | Yes | Honest concession, Autotask ships full ITIL today |
| GBP pricing | Yes at GA | Quote-dependent | Currency-of-business matters |
| Best fit MSP size | 1-30 techs | 20+ techs | Different segments, be honest about where you sit |
Where Autotask is better
- PSA depth, deeper workflow engine, full ITIL, sophisticated contract management.
- Maturity, decade-plus heritage, refined over thousands of MSP deployments.
- Enterprise fit, at 30+ techs, the depth pays back.
- Marketplace breadth, wider third-party integration surface.
If you've built your operations on Autotask and the customisation is load-bearing, the migration is heavy. Be honest about that.
Where OpsMerge wins
- Single vendor, not a portfolio, one company, one roadmap, one bill.
- Public pricing, GBP, monthly or annual, on the page at GA.
- RMM and PSA on one database, not integrated SKUs.
- Regional data residency, your data lives in the region you signed up to.
- Void with full reversal, one action unwinds CDRs, credits and recurring periods.
- Founder voice, built by an MSP owner. Roadmap reflects operator priorities, not portfolio strategy.
Pricing posture
OpsMerge vs Autotask on pricing
Autotask pricing is sales-gated and varies with bundle composition (with or without Datto RMM, BMS, etc.). Indicative public reports place the PSA-only seat in the £50-£100 per technician per month range before bundle discounts.
- Autotask
- Sales-gated quote, bundle-dependent
- OpsMerge
- Flat per-MSP, public GBP pricing at GA
- Autotask
- Portfolio bundles (RMM via Datto, BMS, etc.)
- OpsMerge
- One platform. Full RMM + PSA, flat per-MSP
- Autotask
- Annual contract typical
- OpsMerge
- No contract during beta; monthly or annual at GA
Migration
Coming from Autotask? Here's what changes.
Autotask migrations are heavy because the customisation is deep. We'll be honest about what fits and what doesn't before you commit.
Workflow audit
We map your Autotask workflows, ticket categories and contract types against OpsMerge shapes. Gaps flagged up front.
Ticket and asset import
CSV / API export from Autotask maps to OpsMerge. Custom fields preserved via mapping.
Contract migration
Recurring contract lines port; complex contract types may need restructuring.
Run in parallel
Standard pattern, keep Autotask running for a window while you validate the cut-over.
Realistic timeline: 1-4 months staged depending on workflow customisation depth.
What MSPs migrating from Autotask tell us
Beta is closed and quiet. Once we have real customer quotes, they'll land here. We don't fake them.
Common questions
Is Autotask deeper than OpsMerge on PSA?
Yes, and we are not pretending otherwise. Autotask has decade-plus heritage on PSA depth. OpsMerge fits SMB MSPs whose workflows do not depend on full ITIL ceremony.Will moving from Autotask require workflow rebuild?
For heavy customisation, yes. Tickets and assets translate cleanly. Complex workflow customisations rarely port one-to-one and we will be honest about what fits.What about Datto RMM and BMS in the Kaseya portfolio?
Autotask now sits in the Kaseya portfolio alongside Datto RMM, BMS and VSA. Migrating from Autotask often involves replacing those too. We can scope the wider picture during onboarding.Why pick OpsMerge over Autotask?
One vendor instead of a portfolio, public GBP pricing, predictable renewal posture, RMM as a peer to PSA rather than a separate SKU.
Want PSA without the portfolio?
Apply for the beta. Tell us which Autotask workflows you depend on and we'll be honest about fit.