Switching

Move to Revolutionary RMM customer by customer

Plan your migration customer by customer: what to evaluate, how rollout works, and what you need to move yourself.

Each customer organization gets its own reusable enrollment token, so you can bring customers over one at a time instead of all at once. Before replacing your existing stack, agree on a small pilot scope, the tools you need to keep, and how you will retain history and retrieve your data if you leave. Confirm coexistence for your actual tools during evaluation.

Why switch

What changes for your team.

How the move works

Six steps, in the order most teams take them.

01

Scope it on a demo call

Bring approximate endpoint and customer counts, operating systems, network sites and the integrations you need to keep.

02

Create your customers

Add each customer organization in your workspace. Each one gets a reusable enrollment token, with an optional location.

03

Roll out the agent

Use the silent EXE or MSI through Group Policy, Intune or configuration manager. Windows 10 and 11, Windows Server 2016 and later, macOS on Intel and Apple silicon, and Linux.

04

Connect identity and Microsoft 365

Connect each customer's Microsoft 365 tenant, or Google Workspace through a service account with domain-wide delegation.

05

Add network sites

Place a relay at each site for SNMP and syslog monitoring of switches, printers and firewalls.

06

Connect billing and security tools

Connect your payment processor and import products from Stripe, Square or QuickBooks. Connect your EDR console if you use one.

Plan for this

What does not move automatically.

HISTORY

Tickets and old records

There is no importer for tickets, scripts or documentation from another tool today. Plan which history you need and how you will keep it.

OLDER SYSTEMS

Windows before 10 and Server 2016

The agent cannot run on older Windows versions. Cover those machines with network monitoring or plan their upgrade.

API

A limited API today

The bearer-token API covers enrollment tokens and security posture only. If your workflows depend on a broad API, ask us first.

Good to know

Questions buyers ask.

No. Enrollment tokens are per customer organization, so you can move customers one at a time.

Clients, devices, assets, ticket headers and documentation export to a single JSON file from Account > Billing. The rest of the workspace, full ticket threads and attachments are not in that export yet, so ask us about those before you commit.

No. Revolutionary RMM monitors and drives Microsoft Defender or the third-party engine that is actually running.

Revolutionary Software. Revolutionary IT is the founders' MSP, a related party, and our first design partner.

Plan your move on a call.

Bring your counts, your stack and the workflows you cannot lose. We will map the move with you.