Migrate Microsoft 365 policies between tenants with a dry run first: Conditional Access, Intune, Defender, Exchange, Purview and Teams. Map dependencies, pre-flight checks, deploy, rollback. Plus compare, snapshots, drift monitor and baselines. Free Windows app.
Repo sameerk27/movewise, read from GitHub 15 h ago. sameerk27 has not joined Take My Repo.
sameerk27/movewise is a public repo on GitHub by sameerk27. Migrate Microsoft 365 policies between tenants with a dry run first: Conditional Access, Intune, Defender, Exchange, Purview and Teams. Map dependencies, pre-flight checks, deploy, rollback. Plus compare, snapshots, drift monitor and baselines. Free Windows app. It declares the MIT license on GitHub. It is written mainly in C#, has 1 stars and last changed on 2026-11-17. Nobody has reviewed it on Take My Repo yet, which says nothing about its quality. Read from GitHub on 2026-11-22.
In the maintainer's words. Shown from GitHub; Take My Repo does not keep a copy.
Free, open-source Microsoft 365 tenant-to-tenant migration tool for policies and apps: move Conditional Access, Intune, Defender, Exchange, Purview and Teams policies, and enterprise applications, to another tenant, with a dry run before anything changes.
Website · Screenshots · Download · How it works · Applications · What it migrates · FAQ · Build from source · Docs
Movewise is a free Windows app for Microsoft 365 tenant-to-tenant migrations, for mergers, acquisitions, divestitures and MSPs consolidating tenants. It migrates policies and settings, not mailboxes or files: Entra ID Conditional Access, Intune, Defender for Office 365, Defender for Endpoint, Exchange Online, Purview, Teams and SharePoint. It also migrates enterprise applications: enterprise apps, app registrations and SAML gallery apps, with who can use them.
An admin signs in to the source tenant (read only) and the destination tenant, picks the policies to move, maps every group, user, app and named location they depend on, checks the result in a dry run, and deploys. Every run can be resumed, and rolled back to take out only what it created. After the migration, Movewise compares tenants, takes snapshots, monitors configuration drift, and saves policy baselines to apply to other tenants.
All screenshots use the built-in demo tenants (Contoso and Fabrikam), so no real tenant data is shown.
flowchart LR
A["Connect<br/>source + destination"] --> B["Discover<br/>read the source's policies"]
B --> C["Map<br/>groups, users, apps, domains"]
C --> D["Pre-flight<br/>dry run against the destination"]
D --> E["Deploy<br/>in dependency order"]
E -. if needed .-> F["Roll back<br/>only what the run created"]
| Step | What happens |
|---|---|
| Connect | Sign in to each tenant through the Windows sign-in broker. Guest accounts and same-tenant pairs are refused, and each side's admin roles and licenses are checked. Tick the services to migrate: only those are read |
| Discover | Policies are read from the source with everything they point at: groups, users, apps, locations, filters, scope tags, domains, mailboxes and sites |
| Map | Each dependency is matched in the destination automatically where possible (by name, email, app ID or domain), or matched, created or removed by hand. Mappings export to and import from CSV |
| Pre-flight | Every policy is rewritten for the destination and checked: unmatched objects, name conflicts, missing licenses and roles, removed exclusions, and a before/after view per policy |
| Deploy | Groups and policies are created in order, with progress saved after every object. A run survives a crash, a stop or a dropped connection |
Applications in the sidebar migrates apps, apart from the policies, in four steps of its own: Choose apps, Map users & groups, Pre-flight and Deploy. It uses the tenants signed in on Connect. Microsoft's own apps and managed identities are left out: every tenant has them.
| Kind | What happens |
|---|---|
| Enterprise apps | Another organization's app, such as a SaaS app, is created in the destination for the same app ID, with its settings (assignment required, visible to users, notes, home page, sign-on URL), its owners, and every user and group assigned to it, each keeping its app role. An app the destination already has can be skipped or updated in place; nothing is taken away from it |
| App registrations | The source's own apps are recreated with a new app ID, with their redirect URIs, app roles (same role IDs), optional claims, exposed API scopes and requested permissions, and an application ID URI made from the new app ID. Every new app ID is listed when the run finishes |
| Gallery apps | Made again from the same gallery template, then set up as in the source: entity ID, reply and logout URLs, and app roles. An app whose template can't be found is listed to add from the gallery by hand |
| SAML single sign-on | Sign-on mode, relay state, claims mapping policies and the claims on the Attributes & Claims page are copied, with a new signing certificate: the old one's private key can't be exported. Pre-flight lists each app whose vendor needs the new certificate or federation metadata |
Linked to the policy migration. Each app registration and gallery app Movewise migrates is recorded in an app ID map: old app ID to new. On Map dependencies, a policy's app is matched to its migrated copy as Migrated by Movewise, and the policy is rewritten with the new app ID. An app the destination doesn't have yet has a Migrate it in Applications button, and policy pre-flight lists the policies pointing at missing apps. Migrate the apps first, then the policies.
What Movewise never does with apps. It never grants admin consent: the API permissions an app had in the source are listed for an admin to grant. It never copies secrets: client secrets, certificate private keys, provisioning (SCIM), Application Proxy and password-based sign-on are listed under Set up by hand. Rolling back an app run deletes the apps it created (Entra ID keeps them for 30 days), and puts back apps it updated, taking off only the owners and assignments it added.
In the destination this needs Application Administrator, Cloud Application Administrator or Global Administrator, and three more Graph permissions (see docs/app-registration.md). More on the website.
Besides Migrations and Applications, the sidebar has four screens. All of them only read, except a restore you start yourself.
| Screen | What it does |
|---|---|
| Compare | Source with destination shows which policies and settings are only in one tenant, and which are set differently. The source's policies are first put in the destination's terms (groups, users, locations matched as for a migration), so a group with a different ID isn't a difference. A tenant with a snapshot shows what was added, removed or changed since the snapshot. Each item shows both versions side by side, with only the settings that differ, and the comparison exports to CSV. Also opens from the Deploy screen once a run has finished |
| Snapshots | Take a point-in-time copy of either tenant, list them by tenant, and compare one with its tenant as it is now. Kept in %LOCALAPPDATA%\MovewiseData\Snapshots until you delete them |
| Baselines | Policies saved from a migration (Save as baseline on Discover), to apply to other tenants later without signing in to the template tenant again: on Connect, a baseline can be the source once the destination is signed in. Each baseline lists its policies |
| Drift monitor | Check now compares each signed-in tenant with its latest snapshot and lists what changed since, with the settings that differ. Open any item in Compare to see both versions or restore it |
Restore from a snapshot. After comparing a tenant with a snapshot, Restore… recreates what was removed since and puts changed settings and policies back as they were. It runs the same pre-flight checks as a migration, then opens on the Deploy screen as a run you start, and can roll back. Restored policies come back in report-only or test mode unless you choose to recreate them as they were. A policy changed since, even renamed, is updated back in place. A restore never deletes anything added since. A snapshot can only be restored into the tenant it was taken of, signed in as the destination: the source is never changed.
Get- cmdlets. See why the source stays unchanged.Pre-release. 0.3.0 is an unsigned test build. Try it against test tenants, and don't hand it to client admins until it's signed (see what's left).
Open the latest release. Pre-releases are listed there too.
Download the file for your case:
| File | Use it for |
|---|---|
Movewise-win-Setup.exe |
Most people. Installs for the current Windows user, with no admin rights needed, adds a Start menu shortcut, and installs WebView2 where it's missing |
Movewise-win-Portable.zip |
Locked-down PCs where installers aren't allowed. Unzip it and run Movewise.exe |
*.nupkg, RELEASES, releases.win.json, assets.win.json |
Update packages. Only needed on the server that installed copies update from; don't download these to run the app |
Run the installer. Until the build is signed, Windows SmartScreen shows "Windows protected your PC" with Unknown publisher. For a test build you trust, choose More info, then Run anyway, or clear the download flag first:
Unblock-File "$env:USERPROFILE\Downloads\Movewise-win-Setup.exe"
Start Movewise and sign in to the destination first: that sets up Movewise's app registration there. Then sign in to the source, which approves Movewise once. To use a registration you made yourself, and for the full list of permissions it's granted, see docs/app-registration.md.
Requirements: 64-bit Windows 10 or 11, and admin accounts in both tenants. Nothing else is needed: .NET and the Exchange Online and Teams PowerShell modules are included.
Updates: once a download location is set in UpdateUrl, Movewise checks for a newer version when it starts. An Update to x.y.z button then appears in the sidebar. It only installs when you click it, and never during a deployment.
Where your data lives: everything is kept under %LOCALAPPDATA%\MovewiseData, outside the install folder, so updates and reinstalls leave it alone.
| Folder | Holds |
|---|---|
Projects |
Saved exports. They hold full policy settings, so they're kept out of Documents, which is often synced to OneDrive |
Runs |
One folder per deployment, of policies or apps. run.json is what resume and rollback work from, and destination-before holds the destination's policies as they were before the run. App IDs holds one file per destination tenant mapping each migrated app's old app ID to its new one |
Snapshots |
Snapshots of tenants, for Compare, Snapshots and the Drift monitor |
Baselines |
Saved baselines, with what their policies point at in the template tenant |
Logs |
Daily support logs, with tokens, secrets, addresses, tenant domains, usernames and IPs removed. Save support log in the sidebar zips the last two weeks |
| Tool | Version | Why |
|---|---|---|
| Windows | 10 or 11 | WPF and WebView2 (built into Windows 11) |
| .NET SDK | 8 | Build and test |
| PowerShell | 5.1 or 7 | The module and release scripts in tools/ |
| Git | any | Clone the repository |
git clone https://github.com/sameerk27/movewise.git
cd movewise
# Bundle ExchangeOnlineManagement and MicrosoftTeams, needed for Defender, Exchange, Purview and Teams policies
.\tools\Save-Modules.ps1
dotnet build
dotnet test
dotnet run --project src/Movewise.App
The engine and its tests (Movewise.Core) also build and run on Linux. Only the app itself needs Windows.
| On GitHub (recommended) | On your own PC |
|---|---|
|
The output goes to |
The version must go up with every release, or installed copies won't see it. The full process, signing and hosting updates are in docs/releasing.md.
| Service | Policies and settings |
|---|---|
| Entra ID | Conditional Access, named locations, custom authentication strengths, user settings, the authentication methods policy, cross-tenant access, custom admin roles |
| Intune | Settings catalog, device configuration, compliance (with noncompliance actions), iOS and Android app protection, Autopilot profiles, assignment filters, scope tags, each with its assignments |
| Defender for Office 365 | Anti-phishing, anti-spam, outbound spam, anti-malware, Safe Links, Safe Attachments, quarantine policies, Tenant Allow/Block List, preset security policies |
| Defender for Endpoint | Indicators and custom detection rules |
| Exchange Online | Mail flow rules, journal rules, remote domains, Outlook on the web policies, mailbox retention tags and policies, mobile device mailbox policies |
| Purview | DLP and retention policies with their rules, sensitivity labels and label policies, Endpoint DLP settings |
| Teams | Meeting, messaging, calling, app setup, app permission, channels and update policies with group assignments, plus org-wide settings |
| SharePoint and OneDrive | Sharing, sync and site creation settings |
| Applications | Enterprise apps (same app ID), app registrations and gallery apps (new app ID), with owners, user and group assignments, SAML single sign-on and claims. See Migrate enterprise applications |
Settings every tenant already has, such as default policies and org-wide settings, are changed to match the source rather than created. Only settings that differ are changed, and rolling back puts the earlier values back.
Phases 0 to 5 of the build plan, then application migration:
%LOCALAPPDATA%\MovewiseData\Logs with tokens, secrets and passwords, addresses, tenant names, the signed-in tenants' domains (in any case), DOMAIN\user names, profile paths and IPs removed from every line; unexpected errors logged; "Save support log" in the sidebarHow do I migrate Conditional Access policies to another tenant? Sign in to both tenants, choose the policies on Discover, match the groups, users, apps, named locations and authentication strengths they use on the Map screen, check the pre-flight dry run, and deploy. Every Conditional Access policy is created in report-only mode. See migrating Conditional Access.
Does it migrate mailboxes, files or Teams chats? No. Movewise migrates policies and settings only. User data needs a separate data migration tool.
Can it migrate enterprise apps and app registrations? Yes, since 0.3.0. Enterprise apps keep their app ID; the source's own app registrations and gallery apps get a new one, and SAML apps a new signing certificate. Owners and user and group assignments come with them, and policies are matched to the migrated apps. Admin consent is never granted for you, and secrets aren't copied. See migrating enterprise applications.
Can it change the source tenant?
No. The source only gets read-only clients: a Graph client with no write methods, and PowerShell sessions that refuse anything but Get- cmdlets.
Can I undo a migration? Yes. Rollback deletes only what the run created and puts changed settings back. Nothing that was in the destination before is deleted.
Can I try it without a tenant? Yes. Try the demo connects two sample tenants that live only on your PC.
More answers on the website's FAQ.
UpdateUrl| Project | What it holds |
|---|---|
src/Movewise.Core |
The engine, tested without a tenant: policy type registry, export, mapping, pre-flight, deployment and rollback, project and run files |
src/Movewise.M365 |
Talking to Microsoft 365: sign-in (MSAL + WAM), Graph client with throttling retries, tenant inspection, hosted Exchange Online, Security & Compliance and Teams PowerShell |
src/Movewise.App |
The Windows app: WPF window hosting Blazor screens |
tests/Movewise.Core.Tests |
Unit tests for the engine |
tools/ |
Save-Modules.ps1 (bundle the PowerShell modules) and Publish.ps1 (build a release) |
.github/workflows/release.yml |
The Release workflow |
site/ |
The website, published to GitHub Pages by .github/workflows/pages.yml |
Adding a policy type means adding one entry to ResourceRegistry: where to read and create it, how to assign it, which fields are read-only, and which fields point at other objects.
Runs that earlier versions saved under Documents\Movewise\Runs are still listed, and resumed or rolled back where they are.
Found a bug, or a policy type Movewise should cover? Open an issue. Include the support log (Save support log in the sidebar) if something failed. Identifying details are removed from it, but check it before attaching it anyway.
| Document | Covers |
|---|---|
| docs/app-registration.md | The app registration, every permission it's granted and why, and why the source stays unchanged |
| docs/releasing.md | Building, signing and hosting releases, and what admins see when installing and updating |
Movewise is released under the MIT License. It comes without warranty: test it against non-production tenants first, and review every pre-flight report before deploying.
sameerk27/movewise is a public repo on GitHub by sameerk27. Migrate Microsoft 365 policies between tenants with a dry run first: Conditional Access, Intune, Defender, Exchange, Purview and Teams. Map dependencies, pre-flight checks, deploy, rollback. Plus compare, snapshots, drift monitor and baselines. Free Windows app.
It declares the MIT license on GitHub.
Its maker tagged it for Windows. That is declared by the maker; Take My Repo has not tested it.
Open "Take it" on its page: Take My Repo writes an install plan for your machine and hands it to your AI agent (Claude Code, Codex or Cursor), which asks you before each step. Take My Repo has not tested it on any machine.
Its last change on GitHub was on 2026-11-17. GitHub counts 0 open issues and pull requests. Take My Repo does not judge from that whether it is maintained.
Nobody has reviewed it on Take My Repo yet, which says nothing about its quality.
Predicts what Entra Conditional Access does to real sign-ins today and once report-only policies go live, across a persona matrix, with baseline drift detection.
The Free Software Media System - Server Backend & API
Roadmap to becoming an ASP.NET Core developer in 2026
A modern file manager that helps users organize their files and folders.
Open-source web application framework for ASP.NET Core! Offers an opinionated architecture to build enterprise software solutions with best practices on top of the .NET. Provides the fundamental infrastructure, cross-cutting-concern implementations, startup templates, application modules, UI themes, tooling and documentation.

Self-hosted Microsoft 365 security operations dashboard — aggregates Defender XDR, Entra ID Protection, Intune, Compliance and more into one place.
This page is also available as structured data, with the same sources and dates.
/api/v1/resources/gh/sameerk27/movewiseTake My Repo has not tested this on your machine. Requirements come from the project's own documentation.