This guide walks MSP engineers through two migration paths. Recommended Option 2 minimizes downtime and preserves appearances, forms, apps, and content.
Before you begin
- Access to your current Invarosoft Admin Portal (Master Admin or Admin).
- Credentials for both PSAs (current and target).
- Ability to deploy scripts via RMM for agent deactivation/reactivation.
Option 1 — Immediate Migration
Fastest path, but disruptive. Use if you must switch PSAs immediately.
- Request the “Clear Data” URL. Log a ticket with Invarosoft Support asking for a one-time Clear Data URL for your current instance.
- Open the URL while signed into Invarosoft. Confirm the decision when prompted.
This wipes your current instance configuration so you can re-create it against the new PSA. - Request Wizard access again. Through Invarosoft Ticketing, ask for renewed access to the Setup Wizard.
- Recreate your instance. Run the Wizard, connect the new PSA, and rebuild required items (appearances, forms, buttons/apps, news collections, catalogs, custom pages) as needed.
What to expect
- Shorter total time, but no parallel environment to compare.
- Immediate switch-over; agents will need re-activation.
- Higher risk of interruption during rebuild.
Option 2 — Recommended Side-by-Side
Safest and preferred approach with minimal downtime.
- Create a trial account. Go to invarosoft.com/try and sign up using an alias or an email not previously used as an Invarosoft Portal Login.
- Run the Setup Wizard. Connect the new PSA in the trial account and verify core data sync.
- Request license migration. Log a ticket with Invarosoft asking us to migrate your paid license to the new trial account.
- (Optional) Ask us to clone/recreate UI & content. In the same ticket, request that we recreate your appearances, forms, buttons/apps, news collections, catalogs, and custom pages. Our team will happily assist.
Why this is better
- Run both environments side-by-side for validation.
- Safer testing before touching production agents.
- Assistance from Invarosoft to replicate your setup.
Post-migration testing & rollout
- Test on your own device first.
- Deactivate the agent on your device.
- Reactivate using the new activation code from the new instance.
- Open the desktop app and submit a test ticket end-to-end to the new PSA. Verify ticket type, subtype, and workflow.
- Verify user experience. Check branding, buttons/apps, forms, knowledge links, and news collections.
- Rollout to all supported devices. Once happy with results, script the agent deactivation and reactivationat scale using your RMM.Tip: Run in waves (pilot group → department → full estate). Monitor ticket flow and agent health between waves.
Relink MS 365 / Azure (if used)
If you chose Option 2 (recommended), finish by moving your directory links:
- Break MS 365/Azure links between your clients and the old instance (Admin Portal).
- Run the new PowerShell provided for the new instance to create the links again.
AD Harvester (if used)
- Access the Domain Controller where the Harvester service runs.
- Deactivate the Harvester connected to the old instance.
- Activate it again using the new activation code from the new instance.
- Confirm devices/users synchronize as expected into the new PSA mapping.
FAQ & Troubleshooting
Will my data be copied automatically?
Core PSA-driven data syncs from your new PSA connection. UI elements and content (appearances, forms, buttons/apps, news, catalogs, custom pages) can be recreated—ask us in your ticket and we can assist.
Agents aren’t pointing to the new instance.
- Confirm the device was reactivated with the new activation code.
- Check for old GPO/RMM jobs redeploying legacy configs.
- Reboot and retest the desktop app; submit a test ticket.
Tickets are still landing in the old PSA board.
- Verify the instance the agent is bound to (About → Activation details).
- Confirm the service form mapping for Ticket Type/Subtype is correct.
- Check PSA workflow rules that might be reclassifying tickets.
Where do I get the latest activation code and scripts?
Open a ticket with Invarosoft Support and specify your new instance. We will provide the correct activation code and, if applicable, the current MS 365/Azure linking scripts.
Need help?
We’re happy to assist with license migration, recreating appearances/forms/apps/news, and validating your rollout plan.
Create/Access Trial Open Invarosoft Ticket
If your organization uses a different support URL, use your usual Invarosoft Support Portal link.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article