FR EN
Offer — Power Platform Migration

Tenant-to-tenant migration, industrialized.

Merger, divestiture, reorganization: when your Power Platform estate needs to move to a new tenant, Microsoft provides no tool for it. KALIFY built its own — KALIFY Migration Tool, a migration cockpit proven on 88 real migrations.

1,361
Applications inventoried on the source tenant of a real project
7,050
Power Automate flows analyzed and mapped
88
Migrations run with a single shared configuration
11
Automated steps per migration, in one click
The reality

Migrating a Power Platform tenant, with no native tool.

No global export, no remapping, no share recovery: everything gets redone by hand, application by application.

01 — Cost

5 to 15 days per application

Rebuilding connections, rewriting hard-coded SharePoint URLs, manually re-sharing with every user. Multiply that by hundreds of apps.

02 — Risk

Invisible dependencies

An app depends on flows, SharePoint lists, Dataverse tables. Without a map, gaps break production on cutover day.

03 — Blind spot

Forgotten Power Apps forms

Many SharePoint lists use a Power App as their entry form. These apps belong to no solution: invisible to exports, they disappear during migration.

04 — Accounts

Identities that change

New UPNs, new domains, new teams. Every owner, every share and every security role has to be re-translated.

05 — Data

Dataverse doesn't follow along

Records, their relationships and their GUIDs must be carried over table by table, in the right order, without corrupting references.

06 — Users

Makers left to fend for themselves

After the import, everyone has to reconnect their connection references with no documentation tailored to their app.

The answer

KALIFY Migration Tool: a single migration cockpit, from the first inventory to the closing email.

The internal cockpit our migration operators use — nothing to install on your side. It connects to your tenants via Azure AD certificate for the duration of the engagement, and your data stays within your Microsoft environments.

PILLAR 01

Inventory

Environment discovery, full tenant inventory and 15 CoE analysis views kept continuously up to date.

PILLAR 02

Build

Solution creation from any object, with dependency analysis or grouping by maker.

PILLAR 03

Migrate

One-click pipeline: export, remapping of accounts, URLs and variables, import, data, shares, flow activation.

PILLAR 04

Deliver

Personalized PDF guide for the maker, Excel report, SharePoint deposit and closing email sent automatically.

The tool in detail

Six features that change the game.

Screenshots of the migration cockpit on demo data — same volumes and behavior as the real project.

Feature 1

Full environment inventory

  • The whole tenant in one screen: apps, flows, makers, solutions, connectors, DLP, connections and audit logs.
  • 15 CoE analysis views: real app usage, orphaned makers, inactive flows.
  • Cache + background refresh: instant display, continuous sync via the Power Platform APIs.
  • Search, sort, Excel export on every view, with per-object detail.
KALIFY Migration Tool inventory: 1,361 apps, 7,050 flows, 440 makers and 15 CoE analysis views
117,500 consolidated audit entries on the project's source tenant.
Feature 2

Creating a solution from an object

  • The reality: most apps live outside any solution. Impossible to export them cleanly without grouping them first.
  • "By dependencies" mode: the tool starts from the chosen app or flow and pre-checks everything that needs to come along.
  • "By maker" mode: groups all of a given creator's objects into one solution — up to dozens of apps and flows at once.
  • Solution ready to export: name, publisher and components added automatically via the Dataverse API.
Solution creation mode choice in KALIFY Migration Tool: by dependencies or by maker
The choice offered from any app outside a solution.
Feature 2 — the analysis engine

How the tool finds dependent objects

  • 12-step analysis: linked flows, .msapp parsing, SharePoint list matching, child flow chain, transitive analysis, security roles.
  • Sorted, filterable results: each dependency can be checked or unchecked before creation, required items are locked.
  • Built-in risk report: manual actions are identified in advance and ranked by criticality.
  • Caching: the analysis is reused by the migration and by the PDF guide.
KALIFY Migration Tool dependency analysis: 42 dependencies found, including 6 required, report of 146 actions ranked by criticality
42 dependencies found, 146 manual actions identified before migration.
Feature 3

AD accounts: mapping, shares and security roles

  • Account-to-account matching: source UPN to target UPN, users and teams, bulk CSV import — 11,000 matches on a real project.
  • Automatic transformation rules: any UPN without an explicit match is rewritten by rule.
  • Shares rebuilt on the apps: permissions read from the source and reproduced identically on the target.
  • Environment security roles: users are automatically added to the required roles.
AD account mapping: source-to-target UPN matches and automatic transformation rules
Explicit matches plus automatic UPN rewrite rules.
Feature 3 — continued

SharePoint URLs and forms: automatic translation

  • Global mapping database: over 20,000 sites and 54,000 lists matched source to target.
  • Hard-coded URLs rewritten everywhere: flows, PowerFX formulas, .msapp datasources, environment variables and migrated data.
  • List GUIDs resolved via Graph, SharePoint connections reassigned within the app: no more "not connected" datasources.
  • Power Apps forms migrated too: many SharePoint lists use a Power App as their form (create, edit, view). Outside any solution, and therefore invisible to standard exports, these apps are detected, rewritten, republished and re-linked to the target list.
SharePoint mapping: source tenant sites and lists automatically translated to the target tenant
Sites and lists mapped to the target, GUIDs resolved automatically.
Feature 4

Environment variables: automated enrichment

  • Hard-coded reference scan: the tool detects SharePoint sites and lists hard-coded within apps and flows.
  • Proposal then creation of variables: each reference becomes an environment variable, replacing the fixed GUID.
  • Target values set automatically at import time.
  • Dedicated ALM pipeline: backup, unpack, enrichment, repack, deployment — also usable outside of a migration.
Environment variable enrichment: source and target values set automatically
Every hard-coded reference becomes a variable, populated for the target.
Feature 5

The end-of-migration procedure writes itself

  • PDF guide generated per application, personalized with the app name, target environment and maker's account.
  • Illustrated step-by-step: annotated screenshots for each remaining action, especially recreating connection references.
  • Content derived from the analysis: only the actions actually needed appear.
  • Excel report attached: tables, flows, variables, shares and post-migration actions.
Cover page of the post-migration reconnection PDF guide generated by KALIFY Migration Tool Step in the generated guide: updating each connection reference, with annotated screens
The guide actually generated by the tool for a migrated application.
Feature 6

The closing email is sent automatically

  • Maker detected automatically, their target account resolved via the AD mapping.
  • Message body generated: migration summary and list of remaining actions.
  • PDF guide attached; sent via SMTP or Graph API, your choice.
  • Deliverables archived on the project's SharePoint, full session traceability.
Migration closing email: maker detected, body generated with summary and guide attached
The closing email ready to send: recipient resolved, content and attachments generated.
Execution

One migration = one click, eleven automated steps.

Dry-run simulation, adjustable parallel writes, pause/resume and real-time logs.

  1. Export solutions from the source
  2. Back up the target tenant's state
  3. Unpack solutions (PAC CLI)
  4. Scan SharePoint references
  5. Enrich environment variables
  6. Import into the target environment
  7. Configure connection references
  8. Set target variable values
  9. Migrate Dataverse data (insert/upsert)
  10. Reproduce application shares
  11. Activate Power Automate flows
KALIFY Migration Tool execution screen: migration summary, one-click launch and real-time report
Summary, launch, steps and real-time migration report.
Scope

What the tool actually migrates.

Solutions

Managed or unmanaged, components and option sets included.

Canvas Apps

.msapp rewritten: datasources, formulas, connections.

Power Automate flows

Definitions remapped, then reactivated.

SharePoint forms

The Power Apps used as forms for SharePoint lists, re-linked to the target list.

Connection references

Reconfigured against the target connections.

Environment variables

Created, enriched and populated.

Dataverse data

Insert/upsert, relationships, GUID tracking.

Application shares

Owner, co-owner, edit, view.

Security roles

Users added to environment roles.

Accounts & owners

UPNs remapped, users and teams.

SharePoint references

Sites, lists and GUIDs translated.

Deliverables

PDF guide, Excel report, closing email.

The added value

What changes, measured in the field.

88 migrations run with a single shared configuration on a real tenant-to-tenant project.

By hand With KALIFY Migration Tool
Migrating an application 5 to 15 days of manual rework A few hours, including oversight
Accounts, URLs, variables Manual re-entry, frequent omissions Mappings applied everywhere, automatically
Shares & roles Every user re-shared one by one Reproduced identically on the target
SharePoint forms (Power Apps) Lost, to be rebuilt afterward Detected, rewritten and re-linked to the target list
Documentation Written after the fact, rarely complete PDF guide + Excel report generated and sent
Risks Discovered in production Identified before migration, ranked by criticality
Why KALIFY

A tool built in the field, not on a slide.

KALIFY Migration Tool was born from a real tenant-to-tenant migration project for a major French media company. Every feature answers a problem encountered in real conditions.

88

Real migrations

The tool has already migrated dozens of applications, flows and forms in production, along with their data and shares.

0

Installation on your side

Nothing to deploy in your IT estate: the tool is ours, our migration operators run it. Your data stays within your Microsoft tenants.

20 years

Of IT experience

A firm founded by a former CIO: the migration is run like an IT project, not a script launched blind.

1

Turnkey engagement

Scope qualification, cutover, deliverables and closure: the migration is run end to end by the KALIFY teams.

Contact

A tenant-to-tenant
migration project?

Let's talk for 30 minutes to qualify your scope: number of applications, flows, SharePoint sites, and your cutover timeline.

Quoted after qualification · KALIFY · Power Platform specialist team

Book a 30-min qualification call