Migrating from ConnectWise: the order to move Automate, Manage and ScreenConnect
When you migrate from ConnectWise as a whole stack, the order that usually works is: audit contracts and data first, move the RMM (Automate) or the PSA (Manage) depending on how tightly they are integrated, and cut over remote access (ScreenConnect) last. The deciding factors are your renewal dates, which tool the others depend on, and whether ScreenConnect came bundled with Automate. Here is the sequencing decision, step by step.
Why the order matters more than the tools
Each product on its own is a well-understood migration. Agents get redeployed, tickets get exported, sessions get replaced. The trouble is that the three products lean on each other, and the contracts lean on each other too. Pull one out at the wrong moment and the other two either break or keep billing you.
It also helps to agree on names before you start, because the paperwork and the interface rarely match. ConnectWise's own ConnectWise Invent Agreement confirms that ConnectWise Manage is now known as ConnectWise PSA and ConnectWise Sell is now ConnectWise CPQ. Remote access has moved around more: according to Wikipedia: ConnectWise ScreenConnect, ConnectWise acquired it in February 2015, renamed it ConnectWise Control, rebranded it ConnectWise ScreenConnect on 15 May 2023, and dropped the ConnectWise prefix in 2024. Your invoices may say any of these.
Step one: map the contract dates before anything technical
The calendar sets the plan, not the technology. Under the ConnectWise Master Agreement, subscriptions renew automatically unless either party gives written notice of non-renewal at least sixty days before the end of the current term. The same agreement explicitly covers Automate licensing for managed services, so Automate sits under the same 60-day clause as the PSA.
ScreenConnect SaaS has its own terms. The ScreenConnect agreement says the service will automatically renew at ConnectWise's then current list price unless terminated in accordance with the agreement. A missed notice does not just extend the term, it renews at whatever the list price is on the day.
The 60-day test: for each product, write down the term end date, subtract sixty days, and subtract another two weeks for internal sign-off. That date, not the term end, is your real deadline.
Then lay the three dates side by side. They are often different, because products were bought at different times. Our guide on how to cancel a ConnectWise contract covers the notice mechanics in detail.
The ScreenConnect bundling trap
This is the dependency most migration plans miss. Where a ScreenConnect licence is bundled into an Automate and Command licence, the ConnectWise ScreenConnect SaaS End User License Agreement requires you to be an active and current maintenance subscriber in good standing for Automate and Command, and ConnectWise may revoke the ScreenConnect licence at any time, with or without notice, if that lapses.
In plain terms: if your remote access came with Automate, ending Automate can end remote access too, potentially without warning. So you cannot treat ScreenConnect as the last thing to switch off unless you know how it is licensed. Check whether it is a standalone subscription or part of the Automate bundle. Skip this and you may find your technicians locked out of client machines mid-migration.
RMM first or PSA first?
There is no universal answer, and anyone who gives you one has not looked at your integration. It depends on which way data flows.
Move the RMM first when
- Automate's contract ends sooner. The calendar usually wins. Moving the tool with the nearest deadline avoids paying for another term.
- The Automate to Manage integration is light. If alerts only create tickets and little else, you can point a new RMM's alerts at Manage by email or a simple connector while the PSA stays put.
- Your scripts and monitors are the biggest unknown. Agent redeployment and script rebuilding take the longest, so starting early buys time.
Move the PSA first when
- Billing is the risk you cannot afford. Agreements, additions and time entries feed invoices. Getting a clean billing cycle on the new PSA before touching agents protects cash flow.
- Manage's contract ends first. Same logic as above.
- Automate syncs configurations and agreement counts into Manage. If device counts drive billing, settle the billing side first and rebuild the count source on the new platform.
The consistent rule underneath both: avoid running a new RMM into the old PSA, or the old RMM into a new PSA, for longer than you must. Cross-platform integrations are where alerts quietly go missing. The product-level detail lives in our guides on leaving ConnectWise Automate and leaving ConnectWise Manage.
Why remote access goes last
ScreenConnect is built to integrate with ConnectWise RMM and PSA, which is why its cut-over is usually sequenced around the other two rather than done in isolation. Technicians need remote access throughout the migration, especially while redeploying agents and fixing whatever the redeployment breaks. Switching it first removes the tool you will lean on hardest.
The exception is the bundling trap above. If ScreenConnect depends on Automate maintenance, its replacement must be live before Automate lapses, so remote access cut-over moves to just before the RMM exit rather than after it.
Remote access is the scaffolding. You take it down when the building stands, not before.
A realistic phased plan
- Audit (weeks 1 to 2). Collect contract dates and licence types for all three products. Export a list of agents, scripts, monitors, agreements and open tickets. Decide what to archive rather than migrate.
- Notice (by the earliest deadline). Serve written non-renewal on every product whose term ends before your planned exit, in writing and well inside the 60 days.
- First platform (weeks 3 to 8, roughly). Move whichever of RMM or PSA your dates and dependencies favour. Run a pilot client first, then roll out in batches.
- Second platform. Move the other, ideally into the same new stack so integrations are native rather than bridged.
- Remote access cut-over. Deploy the replacement to every endpoint, confirm technicians can reach each one, then retire ScreenConnect.
- Decommission. Remove old agents, revoke API keys and integrations, and keep read-only exports for records.
The timing varies with fleet size, script count and how much history you insist on bringing. A small MSP with a light integration might finish within a quarter; a heavily customised estate will take longer. The firm constraint is that the whole plan has to fit between today and the last notice deadline you can still meet, or it has to span another renewal deliberately.
Rule of thumb: plan backwards from the earliest 60-day deadline, never forwards from the day you feel ready.
Failure modes worth naming
- The orphaned alert. A new RMM sends alerts into the old PSA, the connector fails, and nobody notices for days.
- The vanishing remote session. Bundled ScreenConnect is revoked when Automate lapses.
- The surprise renewal. One product is forgotten and renews at list price.
- The half-billed month. Agreements are split across two PSAs and one invoice run misses them.
Where this fits with Helios
Most of this plan is contract discipline, not tooling, and no platform removes the need to serve notice on time. What Helios changes is the destination: RMM, PSA, helpdesk, remote access and billing into Xero or QuickBooks sit in one product, so there is no cross-vendor integration to bridge once you arrive. Every feature is on every plan with no charge per technician, and the pricing page sets out the per-device rates. If you want to compare it against your other shortlist options first, the comparison pages are a sensible next stop.
Common questions about leaving ConnectWise
Can I cancel ConnectWise Automate and keep ScreenConnect?
Keeping ScreenConnect after cancelling Automate depends on how ScreenConnect is licensed. If ScreenConnect was bundled with Automate and Command, ConnectWise's terms require current Automate maintenance and allow the licence to be revoked if that lapses. A standalone ScreenConnect subscription is governed by its own agreement and renewal terms instead.
How much notice does ConnectWise need to cancel?
The ConnectWise Master Agreement requires written notice of non-renewal at least sixty days before the end of the current term, and that clause covers both the PSA and Automate. Missing the window means the subscription renews automatically, so serve notice early and keep proof of when it was sent.
Should I run old and new tools in parallel?
Running ConnectWise and a new platform in parallel is sensible for a short pilot and during batched agent rollouts, because it limits risk. Long parallel running is costly and confusing, since technicians must check two consoles and alerts can fall between them. Keep the overlap as short as the migration allows.
Related: Where ConnectWise users actually go: Halo, Syncro, Atera and Autotask compared as migration destinations, How to export tickets from ConnectWise Manage before you cancel
Read next
Why MSPs choose Helios
One platform that does the work, at a price that stays put
Helio fixes, not just flags
When an alert fires, Helio, the AI technician built into Helios, investigates it, writes the fix and runs it once you approve. It keeps what works, so the next one is quicker.
Everything in one product
RMM, a service desk with SLAs, patching including third-party apps, remote access, Microsoft 365 and Defender checks, backup monitoring, a client portal and billing into Xero or QuickBooks.
Priced by fleet, not by people
£4 a device on Launch up to 25 devices, from £20 a month, then £99, £199 or £399 a month by fleet size, with any number of technicians and every feature on every plan.
A price that stays put
Your price is locked for as long as you stay subscribed, and that is written into our terms. Monthly billing, cancel any time.
Bring your clients across
Import your clients and machines from another RMM's CSV export, then roll the Helios agent out at your own pace, with a count of how many have arrived.
14 days free, no card to start
The full platform from the first minute, on your own machines. No sales call. Remote control asks for one card check, and nothing is charged.
See it on your own fleet
Helios is the AI-native platform for MSPs: monitoring, patching, security, Microsoft 365, backup monitoring, remote access, client billing and an AI service desk in one product, at one flat price per MSP. Contracts and logged time become invoices in Xero or QuickBooks without leaving the platform. Every feature is on every plan. 14-day free trial, card-free, set up in minutes, cancel any time.
Start freeResearched and written with Helio SEO, our AI writer for business blogs.