Appearance
OpsMerge vs Kaseya
One vendor. One platform. One bill.
Kaseya owns VSA, BMS, Datto RMM, Autotask, IT Glue, Datto BCDR, Spanning, RocketCyber, Unitrends and the rest. If you're an unhappy Kaseya customer, you've already noticed the post-acquisition pricing model and the ticket-routing roulette. OpsMerge is one company, one product, one bill.
Kaseya assembled its current portfolio through a long acquisition spree, VSA, BMS, Datto RMM, Autotask, IT Glue, Spanning, RocketCyber, Datto BCDR, Unitrends, ID Agent and others. Each of those products had a real customer base and a real product team before the acquisition. Some still do.
The pattern post-acquisition is well-documented across MSP forums: pricing renegotiations on renewal, bundle pressure (you wanted VSA but the renewal includes BMS, IT Glue and Datto BCDR), support routing across multiple historical helpdesks, and roadmap timing that follows portfolio strategy rather than individual product priorities.
OpsMerge is the opposite trade-off. One product, one company, one bill, one roadmap. Public GBP pricing at GA. Annual review with 90 days notice if anything changes. Founder reads support email. The platform is built to do less than the entire Kaseya portfolio, deliberately. You stop reconciling six products.
Feature-by-feature
| Capability | OpsMerge | Kaseya | Notes |
|---|---|---|---|
| Single vendor (not a portfolio) | Yes | No | Kaseya = VSA + BMS + Datto + Autotask + IT Glue + … |
| One platform (not multiple SKUs) | Yes | No | Each Kaseya product remains a separate platform |
| Public pricing | ✓ | ✗ | Kaseya pricing is sales-gated and bundle-dependent |
| Predictable renewal pricing | 90-day notice + annual review | Reported variable | MSP forums document renewal price renegotiation patterns |
| RMM + PSA + billing on one database | Yes | No | Kaseya: VSA + BMS / Datto RMM + Autotask, separate platforms |
| Asset-based auto-billing | Yes | Partial | OpsMerge: live agent count → invoice line in one platform |
| Void with full reversal | ✓ | Partial | OpsMerge: one-action unwind |
| Region-based data residency | Yes | Optional | OpsMerge: EU and US regions live, AP on the roadmap |
| Marketplace integrations breadth | Short list | Wide (across the portfolio) | Honest concession, Kaseya portfolio has wide marketplace surface |
| Best fit MSP size | 1-30 techs | Enterprise-shaped | Different segments, be honest about where you sit |
Where Kaseya is better
- Portfolio breadth, if you want one vendor to cover RMM, PSA, docs, backup, BCDR, dark web monitoring and security, Kaseya has a product for each.
- Individual product depth, VSA, BMS and Autotask are each mature in their own right.
- Marketplace surface, across the combined portfolio, the integration surface is wide.
- Enterprise scale, large MSPs that staff a Kaseya admin can extract real value.
If portfolio breadth genuinely matches how you operate, and you have the scale to absorb the trade-offs, Kaseya remains credible.
Where OpsMerge wins
- One company, one bill, not six products from one parent.
- Public pricing, GBP, on the page at GA. Predictable renewal posture: 90-day notice + annual review.
- RMM, PSA and billing on one database, not stitched-together SKUs.
- Regional data residency, your data lives in the region you signed up to.
- Founder voice, built by an MSP owner. Roadmap follows operator priorities, not portfolio strategy.
- Direct vendor relationship, no portfolio team between you and the people building the product.
Pricing posture
OpsMerge vs Kaseya on pricing
Kaseya pricing is bundle-dependent and varies sharply on renewal. MSPs report substantial pricing renegotiations at renewal time across the portfolio.
- Kaseya
- Sales-gated quote, bundle-dependent
- OpsMerge
- Flat per-MSP, public GBP at GA
- Kaseya
- Renewal renegotiation reported across the portfolio
- OpsMerge
- Annual review, 90-day written notice on any change
- Kaseya
- Multi-SKU portfolio
- OpsMerge
- One platform. Full RMM + PSA, flat per-MSP
Migration
Coming from Kaseya? Here's what changes.
Kaseya migrations vary sharply depending on which products you use. VSA + BMS migrations are different shapes from Autotask + Datto RMM. We're honest about that up front.
Portfolio audit
We map which Kaseya products you use today, VSA, BMS, Autotask, Datto RMM, IT Glue, etc., against OpsMerge scope.
Gap conversation
If you depend on Datto BCDR or specific Kaseya security products, those stay where they are. OpsMerge replaces RMM + PSA + billing.
Agent and ticket migration
Standard staged pattern, agents in pilot, tickets imported via CSV / API, contracts migrated.
Run in parallel
Keep Kaseya running for a window. Validate before cut-over.
Realistic timeline: 1-4 months depending on which Kaseya products are in scope and how customised they are.
What MSPs migrating from Kaseya tell us
Beta is closed and quiet. Once we have real customer quotes, they'll land here. We don't fake them.
Common questions
Will OpsMerge replace my entire Kaseya portfolio?
Honest answer: no, not in one move. OpsMerge replaces VSA / Datto RMM (RMM), BMS / Autotask (PSA) and the billing layer. If you also use IT Glue, Datto BCDR, Spanning, RocketCyber or ID Agent, those stay where they are or get replaced separately.What about renewal pricing patterns?
OpsMerge runs an annual pricing review and provides 90 days written notice before any change. If you do not like the new number you can talk to us. We would rather sort something out than lose a good MSP over a number.Is the migration heavy?
Depends on which Kaseya products are in scope and how customised they are. One to four months staged is realistic for a typical small-to-mid MSP.What is Kaseya genuinely better at?
Portfolio breadth. One vendor for RMM, PSA, docs, backup, BCDR, security. If genuine portfolio breadth matches how you operate, the trade-off may make sense.What about Datto BCDR specifically?
Out of scope for OpsMerge. Datto BCDR remains a respected BCDR product. Keep it; OpsMerge will not displace it.
One vendor beats a portfolio.
Apply for the beta. Tell us which Kaseya products you use and we'll tell you exactly what migration looks like.