FeaturesPricingCompareIntegrationsSecurityMigrationContact usVersion française Let's talk →

Migration

You do not rebuild your fleet. You change agents.

Migration to OKTO RMM happens in four steps, included in the subscription: the OKTO agent is deployed by the current RMM and coexists with the old one, organizations and sites are imported, policies are rebuilt from 58 packs by role, then the old agent is removed by script. A fleet of 100 devices takes about two weeks.

Nobody loses a day reinstalling anything by hand.

  1. Coexist

    We deploy the OKTO agent through your current RMM, in one script, on a few devices then the whole fleet. Both run side by side. Nothing breaks, you compare.

  2. Import

    Organizations, sites, custom fields, per-device documentation. We import from your export; devices attach themselves to their organization through the enrolment key.

  3. Rebuild the policies

    Patches, alerts, maintenance, software. We start from our 58 packs by role and your current rules, adjust with you, and test on a pilot group.

  4. Remove the old one

    When you are ready, an OKTO script uninstalls the old agent across the fleet. You cancel the other contract. We stay on the line for the first week.

What migrates as is

  • Your PowerShell, Bash, Python and CMD scripts, with their parameters
  • Your organizations, sites, contacts and custom fields
  • Your alert thresholds, translated into our 21 condition types
  • Your patch schedules and maintenance windows
  • Your allowed and banned software lists
  • Your PSA and antivirus integrations, reconnected with the same credentials

What does not migrate, and why

  • The alert and session history of the old tool: it stays there, we help you export it before you cancel
  • Scripts written in the old tool's proprietary language: we rewrite them together in PowerShell or Bash
  • Custom dashboards: we rebuild them in the console, you choose what matters

We would rather tell you here than on cutover day.

Real duration

How long does the migration take?

One day for the pilot, one week of coexistence to compare alerts, a few days for the policies, one night to remove the old agent. A 500-device fleet takes a month because we move organization by organization, not because the tool is slow.

  • No migration or setup fees
  • You are only billed from the month the old agent is removed
  • A named OKTO technician for the whole migration
Migration · Lemieux Workshop · day 9 of 14
OKTO agents18 of 18 devices, stable heartbeatDeployed
Import1 organization, 1 site, 18 records, 6 custom fieldsDone
PoliciesPatches, Windows workstation alerts, Sunday maintenanceTested
ComparisonAlerts over the last 7 days: 11 here, 9 there, 2 real ones moreReviewed
Old agentRemoval scheduled Friday 10 p.m., script readyDay 12

Questions

What we get asked before migrating.

Can both agents run at the same time?
Yes, and it is the recommended method. The OKTO agent deploys through the current RMM in one script. Both coexist while you compare alerts and inventories. No device is left unmonitored during the switch.
Do my scripts work as they are?
PowerShell, Bash, Python and CMD scripts paste into the library with their parameters. Only scripts written in the old tool's proprietary language need rewriting, and we do it together.
Is the old RMM's history carried over?
No. The alert and session history stays in the old tool. It is best to export it before cancelling. What migrates: organizations, sites, contacts, custom fields, thresholds, patch schedules, maintenance windows, software lists, integrations.
How much does the migration cost?
Nothing. It is included in the subscription, with no setup fee, and billing only starts in the month the old agent is removed.
Who does the work?
A named OKTO technician, from the pilot to the first week after the old agent is removed. The calendar is the client's: two weeks for 100 devices, about a month for 500, because we move organization by organization.

Where to start

We start with a few devices in coexistence. The rest follows at your pace.