migration-planner

KO | EN

gitlite — search

#python #java #python3 #arduino #golang #machine-learning #rust #html #flask #javascript #seismology #nodejs

migration-planner

★ 18 Open GitHub ↗

The Migration Planner is a desktop application designed to help deployment partners and IT administrators assess a Microsoft tenant before migration.

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# Migration Planner Tool

**Doc version: v2.1.0**

## What's new

- **Microsoft Teams & Chat Migration Planning**: Full support for scanning and projecting migration timelines for Microsoft Teams, Channels, and Private Chats alongside Exchange Online.
- **Files in OneDrive / SharePoint Planning**: Support added for metrics related to OneDrive / SharePoint sites.
- **Process-Level Decoupling Architecture**: Architectural refactoring that decouples the launcher (`migration_planner.py`) and individual workload planners into isolated OS subprocesses to prevent runtime contention, memory corruption, or GIL clashes during highly concurrent MS Graph API scanning.
- **Bidirectional Navigation**: Addition of a top navigation bar featuring a `← Back to Selector` button for seamless transitions between workload planners.

#### UX change to support new features
- The startup screen would now show a selector that enables user to select if they want to run Exchange online estimations, Files estimations or Chat Estimations.
- The progress screen would have three progress bars for Files estimation:
  - **Site Discovery**: This progress bar will report the progress while scanning all the sites/subsites in the tenant under the root site, along with some other metadata like List count, Drives/DLs count, License units count, etc..
  - **Drive Discovery**: This progress bar will report the progress while scanning all the folders in the drives found in the site scan.
  - **Metrics Calculation**: This will show the progress of the metrics (like max depth, folder count, files count, etc.) for the drives.
- The report screen would display:
  - **Summary Metrics**: This will display the summary metrics for the entire tenant.
  - **File Size Distribution**: This will display the distribution of files based on their sizes as per the bucket ranges provided in the input screen.

#### System behaviour changes
- **Site Discovery** and **Drive Discovery** phases in the progress screen would show indeterminate progress as the total number of sites/folders/files are not known during those phases.
- However the **Metrics Calculation** phase would be determinate and show proper progress.
- The logs and CSV report would only be available through the export option and not under the outputs/ directory to minimize report creation latency for huge reports.

## DISCLAIMER

*   The estimations provided by this tool are calculated projections intended for preliminary planning only. Actual migration timelines (ETAs) and batch execution may vary based on real-time network conditions, source/target throttling policies, migration configurations, and the volume of delta migrations. The estimations do not constitute a performance guarantee or a binding service level agreement (SLA).
*   Please note that this release is an experimental feature with limited and evolving functionality.
*   Partners and/or Customers should **NOT** use this product for production projects where business outcomes rely on the product functionality or timelines.
*   Partners and/or Customers should **NOT** commit hard migration timelines based on this product.
*   By using this tool, you acknowledge that log files generated by this script contain personally identifiable information and that you are solely responsible for securing your local environment and these files.
*   Use of this tool is governed by the Apache 2.0 license.

### Functionality Limitations

*   This tool only provides migration time estimates for the new Data Migration Service with specific enhancements for large scale migrations. It does not cover Google Workspace Migrate, or any other data migration tool.
*   Microsoft Exchange Online, Microsoft OneDrive / SharePoint and Microsoft Teams / Private Chat scan and migration planning is supported. ETAs are based on Email and Chat/Channel corpus projections.
*   **Shared & Private Channels Coverage**:
    - **Private Channels**: Standard/private channels are fully scanned and included if their parent Team is resolved or specified.
    - **Shared Channels**: Shared channels hosted within a user's member Team are included. Shared channels hosted in teams the user is *not* a member of are not discovered by the `/users/{id}/joinedTeams` API and thus are not scanned, unless their host Team is explicitly included in the scan scope.
*   This tool only provides a guesstimate, and migration timelines should in no way be taken as guarantee or SLA.

---

## Table of Contents

- [Introduction](#introduction)
- [Prerequisites & Installation](#prerequisites--installation)
  - [1. Python Version](#1-python-version)
  - [2. Installation Steps](#2-installation-steps)
    - [Windows](#windows)
    - [macOS](#macos)
    - [Linux (Ubuntu/Debian)](#linux-ubuntudebian)
  - [3. Setting up a Virtual Environment (Optional / Corp Policy)](#3-setting-up-a-virtual-environment-optional--corp-policy)
- [Setting up Microsoft Azure](#setting-up-microsoft-azure)
  - [1. Register the App](#1-register-the-app)
  - [2. Grant Permissions](#2-grant-permissions)
  - [3. Get Credentials](#3-get-credentials)
- [Running the Tool & Process Decoupling](#running-the-tool--process-decoupling)
- [Tool Configuration & Scanning](#tool-configuration--scanning)
  - [Workflow A: Exchange Online Planner](#workflow-a-exchange-online-planner)
  - [Workflow B: Microsoft Files (OneDrive + SharePoint) Planner](#workflow-b-microsoft-onedrive--sharepoint)
  - [Workflow C: Microsoft Teams & Chat Planner](#workflow-c-microsoft-teams--chat-planner)
- [Understanding the Results](#understanding-the-results)
  - [Workflow A: Exchange Online Planner](#workflow-a-results-exchange-online-planner)
  - [Workflow B: Microsoft Files (OneDrive + SharePoint) Planner](#workflow-b-results-microsoft-onedrive--sharepoint)
  - [Workflow C: Microsoft Teams & Chat Planner](#workflow-c-results-microsoft-teams--chat-planner)
- [Outputs & Artifacts](#outputs--artifacts)
  - [Workflow A: Exchange Online Planner](#workflow-a-outputs-exchange-online-planner)
  - [Workflow B: Microsoft Files (OneDrive + SharePoint) Planner](#workflow-b-outputs-microsoft-onedrive--sharepoint)
  - [Workflow C: Microsoft Teams & Chat Planner](#workflow-c-outputs-microsoft-teams--chat-planner)
- [Terms & Disclaimer](#terms--disclaimer)

---

## Introduction

The Migration Planner is a desktop application designed to help deployment partners and IT administrators assess a Microsoft 365 tenant before migration. Through its process-decoupled architecture, administrators can independently assess Exchange Online (Emails, Contacts, Calendars, In-Place Archives, Group Mails), Files in OneDrive / SharePoint or Microsoft Teams (Channels, Private Chats) to provide volume metrics and generate optimized Migration Batch Plans with estimated completion times (ETAs) (not applicable for files estimation).

---

## Prerequisites & Installation

### 1. Python Version

Please ensure you have **Python 3.10** or newer installed on your system.

### 2. Installation Steps

#### Windows
1.  **Download Python**: Visit [python.org/downloads](https://www.python.org/downloads/) and download the latest installer.
    *   **Important**: Ensure the checkbox **"tcl/tk and IDLE"** is selected during installation (it is usually selected by default). This installs the necessary GUI components.
    *   **Important**: Check the box **"Add Python to PATH"** during installation.
2.  **Verify Installation**: Open Command Prompt (cmd) or PowerShell and make sure the following commands run successfully and return you the version ids of python and pip:
    ```cmd
    python --version
    pip --version
    ```
3.  **Install Dependencies**: Run the following command:
    ```cmd
    pip install customtkinter requests pandas psutil Pillow urllib3 sortedcontainers aiohttp certifi
    ```

#### macOS
1.  **Download Python**: Visit [python.org/downloads](https://www.python.org/downloads/) and download the macOS installer. Alternatively, use Homebrew from the terminal (`brew install python`).
2.  **Install Tkinter**: If you are using Homebrew or encounter GUI errors, you may need to explicitly install the Tkinter library:
    ```bash
    brew install python-tk
    ```
3.  **Verify Installation**: Open Command Prompt (cmd) or PowerShell and make sure the following commands run successfully and return you the version ids of python and pip:
    ```bash
    python3 --version
    pip3 --version
    ```
4.  **Install Dependencies**:
    ```bash
    pip3 install customtkinter requests pandas psutil Pillow urllib3 sortedcontainers aiohttp certifi
    ```

#### Linux (Ubuntu/Debian)
1.  **Install Python**: Python is usually pre-installed. If not, run:
    ```bash
    sudo apt-get update
    sudo apt-get install python3 python3-pip
    ```
2.  **Install Tkinter**: Linux often requires the separate Tkinter package:
    ```bash
    sudo apt-get install python3-tk
    ```
3.  **Install Dependencies**:
    ```bash
    pip3 install customtkinter requests pandas psutil Pillow urllib3 sortedcontainers aiohttp certifi
    ```

### 3. Setting up a Virtual Environment (Optional / Corp Policy)

If your organization restricts installing packages globally, use a virtual environment:

1.  **Create the environment**:
    ```bash
    # Windows
    python -m venv venv

# Mac/Linux
    python3 -m venv venv
    ```
2.  **Activate the environment**:
    *   Windows: `.\venv\Scripts\activate`
    *   Mac/Linux: `source venv/bin/activate`
3.  **Install packages** as shown above inside this environment.

---

## Setting up Microsoft Azure

To scan your tenant, you need to register an app in the Microsoft Entra ID (formerly Azure AD) portal.

### 1. Register the App
1.  Go to [portal.azure.com](https://portal.azure.com/).
2.  Navigate to **Microsoft Entra ID > App registrations > New registration**.
3.  Name the app (e.g., "Migration Planner Tool").
4.  Select **"Accounts in this organizational directory only"** (Single Tenant).
5.  Click **Register**.

### 2. Grant Permissions
In your new app, go to **API permissions > Add a permission > Microsoft Graph > Application permissions** (NOT Delegated), and assign permissions based on the workloads you plan to scan:

#### Shared Permissions (Required for Both Workloads)
*   `User.Read.All` (To list users and enumerate rosters)
*   `Group.Read.All` (To get M365 group and team structures)

#### Exchange Planner Specific Permissions
*   `Mail.Read` (To count emails)
*   `Contacts.Read` (To count contacts)
*   `Calendars.Read` (To count calendar events)
*   `MailboxFolder.Read.All` (To count emails in in-place archives)
*   `MailboxSettings.Read` (To distinguish user and shared mailboxes)

#### Chat & Teams Planner Specific Permissions
*   `Reports.Read.All` (To fetch automated M365 activity reports for heuristics estimation)
*   `Chat.Read.All` (To scan private chats and chat memberships)
*   `ChannelMessage.Read.All` (To estimate channel messages across teams)
*   `ChannelSettings.Read.All` (To list channels)
*   `TeamsActivity.Read.All` (To read Teams activity analytics)
*   `TeamMember.Read.All` (To read team memberships)
*   `Group.Read.All` (To list teams)

### Files Planner Specific Permissions
*   `Sites.Read.All` (To list sites)
*   `Files.Read.All` (To count files)
*   `LicenseAssignment.Read.All` (To check license information)

5.  Click **Add permissions**.
6.  **Crucial Step**: Click **"Grant admin consent for [Your Organization]"** and confirm "Yes". All status icons should turn green.

### 3. Get Credentials
You will need three values for the tool:
1.  **Tenant ID**: Found on the app's Overview page ("Directory (tenant) ID").
2.  **Client ID**: Found on the app's Overview page ("Application (client) ID").
3.  **Client Secret**:
    *   Go to **Certificates & secrets > New client secret**.
    *   Add a description and click **Add**.
    *   Copy the **"Value"** immediately (you won't see it again).

---

## Running the Tool & Process Decoupling

1.  Open your terminal or command prompt.
2.  Navigate to the folder containing the script:
    ```bash
    cd path/to/migration_planner
    ```
3.  Run the script:
    *   Windows: `python migration_planner.py`
    *   Mac/Linux: `python3 migration_planner.py`

*(Ensure you are in your virtual environment if you created one).*

### Process Decoupling Mechanics
The launcher window (`migration_planner.py`) acts as a lightweight CustomTkinter `SelectorApp`, which can be used to select which estimations need to be run (Exchange Online, Chats or Files).
All workload planners feature a top navigation bar with a `← Back to Selector` button. Clicking this cleanly terminates the active planner process and respawns a fresh `migration_planner.py` selector session.

---

## Tool Configuration & Scanning

### Workflow A: Exchange Online Planner

#### 1. Connect & Source Selection (Exchange)
*   **Connect with Microsoft**: Enter your Tenant ID, Client ID, and Client Secret.
*   **User Source**:
    *   **Scan All Users**: Automatically fetches every user in your tenant.
    *   **Upload CSV**: Allows you to scan a specific subset of users or pre-load existing counts.
    *   **CSV Format**: Must contain a header **Email Id** (e.g., `user@domain.com`). Also if Group Mailbox estimation is required then a column called `"Type"` is needed to segregate group mailbox IDs from user mailbox IDs. The correct values for Type column are `"User"`, `"Group Mailbox"`.
    *   **Understanding Smart Delta Scans**: When using the CSV upload feature, the tool intelligently analyzes the provided columns to determine if a live scan is necessary.
        *   **Full Data Provided (No Scan Required)**: If your CSV contains all the count columns (e.g., `Email Count`, `Contact Count`, etc.) for the workloads you selected in the UI, the tool completely skips the scanning phase and immediately calculates the ETAs. **In this scenario, no Microsoft App ID credentials are required** (you can leave Tenant ID, Client ID, and Client Secret blank).
        *   **Partial Data Provided (Delta Scan)**: If you select workloads to scan (e.g., Contacts and In-Place Archives) but your CSV is missing those specific columns, the tool performs a "Delta Scan." It will use your CSV data for the columns provided and only run a live Microsoft Graph scan for the missing data types.
        *   **Credential Requirements**: Because a Delta Scan requires communicating with Microsoft Graph to fetch the missing data, **you must provide valid App ID credentials**. If you upload a CSV with missing columns and do not provide credentials, the tool will return an error: `Missing Credentials for Delta Scan (CSV missing some columns).`
#### 2. Advanced Settings (Exchange)
Click **"Show Advanced Settings"** to tune the performance:
*   **Sources**: Check/Uncheck Emails, Contacts, Calendars, In-Place Archives and Group Mails to define what you want to scan.
*   **Concurrency**: Controls how many parallel threads the tool runs.
    *   **Recommendation**: For a standard machine (8 Core, 16GB+ RAM), set this to **30**. Setting it too high may cause more frequent throttling errors from Microsoft and consume more resources from your system.
*   **Max Batches**: Defines the upper cap for the number of batches to be generated by the migration plan. In case of very large corpuses, it might not be possible to adhere to this number.

---

### Workflow B: Microsoft OneDrive / SharePoint

#### 1. Connect & Source Selection
*   **Connect with Microsoft**: Enter your Tenant ID, Client ID, and Client Secret.
*   **User Source**:
    *   **Scan All Sites**: Scans all the Sites in the tenant.
    *   **Upload CSV**: Allows you to scan a specific subset of users / site collections. Users and Site collections are differentiated by their expected regex. Site collections are expected to start with `https://` or `http://` while users are expected to have the standard email regex.

Note that for CSV flow, only one column by the name `Entity` is expected. The provided entries under this column are split into SharePoint sites and OneDrive user emails based on their regex. Several validations are added to ensure the integrity of the input CSV. Some of them include validations around not allowing emails if only SharePoint scanning is enabled, or not allowing site collections if only OneDrive scanning is enabled. If the user does not provide a valid CSV or provides a CSV with invalid entries, a error message is displayed and the tool does not proceed with the scan.

Also if invalid entries that pass the regex checks are provided they'll be skipped during discovery and will not be shown in the final report. Please refer to the logs for details around these invalid entries.

PFB an example of a valid CSV

```csv
    Entity
    bugbash4@smh3v.onmicrosoft.com
    https://smh3v.sharepoint.com/sites/sc2
    https://smh3v.sharepoint.com/

```

NOTE: If we already have the corpus data and we only want to re-calculate ETA then we can use the "Upload CSV" feature and upload the CSV report generated in the `outputs` directory for the corresponding run (for example `outputs/20260618_103419/site_report_20260618_103419.csv`). Note that this ETA calculation without re-scan would only be performed for legitimate OneDrive exported CSVs only (i.e., only the CSVs containing all the fields present in the original report and only personal oneDrive sites would be supported).

DISCLAIMER: If using the "Upload CSV" feature to re-calculate ETA, the final output would be missing some metadata like "Large Resources", "File Size Distribution", etc.. So the original corpus report should be used as the source of truth and the generated report without scan should be used only for batch planning.

#### 2. Advanced Settings
Click **"Show Advanced Settings"** to tune the performance and select your estimation mode:
*   **Site Types to Scan**:
    *   **Personal Sites (OneDrive)**: Scans all the Personal / OneDrive sites in the tenant.
    *   **SharePoint Sites**: Scans all the SharePoint sites in the tenant.
*   **Concurrency**: Controls how many parallel threads the tool runs. Note that this number is not the exact number of threads spawned but is a guidance on the thread count.

#### 3. Starting the Scan
Click **"Get Migration Estimates"**.
*   A disclaimer will appear noting that results are estimates. Click **OK** to proceed.
*   The tool will verify your credentials and permissions before starting.

#### 4. The Scan Page
Once started, you will see a real-time progress screen:
*   **Spinners**: Indicate active scanning phases.
*   **Progress Bars**: Show percentage completion for Site and Drive Discovery along with Metrics Calculations.
*   **Live Counts**: Updates in real-time as items are discovered.

---

### Workflow C: Microsoft Teams & Chat Planner

#### 1. Connect & Source Selection (Chat)
*   **Connect with Microsoft**: Enter your Tenant ID, Client ID, and Client Secret.
*   **User Source**:
    *   **Scan all teams and users**: Automatically fetches every team and user in your tenant.
    *   **Upload CSV**: Allows you to scan a specific subset of users/teams or pre-load existing counts.
    *   **CSV Format**: Must contain a header **Email or Team ID** and a **Type** column specifying whether the row represents a `"User"` or a `"Team"`.
        *   **Sample Format**:
            ```csv
            Email or Team ID,Type
            user@xyz.com,User
            124-adc-445,Team
            ```
        *   **User/Team Resolution**: If a CSV of users is supplied without teams, the tool automatically resolves all Teams these users are members of using the `/users/{id}/joinedTeams` MS Graph API endpoint in batch requests and performs the scan on these teams only. Note that this covers all private and shared channels hosted within those resolved Teams. Shared channels hosted in external teams the user does not belong to are not resolved, as MS Graph does not support querying external shared channel memberships directly.

#### 2. Advanced Settings & Estimation Modes (Chat)
Click **"Show Advanced Settings"** to tune the performance and select your estimation mode:
*   **Estimation Modes**:
    *   **Last 6 Months (Heuristics)**: Leverages automated M365 activity reports (`Reports.Read.All`) for instant, high-level tenant estimations without deep scanning. *Note: Sizing projections are computed using statistical multipliers based on standard enterprise averages. For precise customer-specific densities, use Deep Scan mode.*
    *   **Deep Scan (Sampling)**: Performs deep multi-threaded scanning across a customizable percentage of users and teams (e.g., 0.01% to 100%). *Statistical Note: Sampling users rather than individual messages may miss high-activity outlier accounts. To capture these outliers, we recommend using a higher sampling rate or uploading a targeted CSV containing known high-volume rosters (such as helpdesks or executive assistants).*
*   **Scan Options**: Check or uncheck Private Chats to control scan boundaries.
*   **Concurrency**: Sets async thread limits for channel message extrapolation.

#### 3. Starting the Scan (Chat)
Click **"Get Migration Estimates"**.
*   A disclaimer will appear noting that results are estimates. Click **OK** to proceed.
*   The tool will verify your credentials and permissions before starting.

#### 4. The Scan Page (Chat)
Once started, you will see a real-time progress screen:
*   **Spinners**: Indicate active scanning phases.
*   **Progress Bars**: Show percentage completion for Private Chats and Channels.
*   **Live Counts**: Updates in real-time as items are discovered.

---

## Understanding the Results

### Workflow A Results: Microsoft Exchange Online

#### 1. Top Level Metrics
The top cards display the total scope of the migration:
*   **Users**: Total distinct users identified/scanned.
*   **Emails / Events / Contacts / In-Place Archives / Group Mailboxes**: The aggregate sum of items across all users.

The CSV report would include additional details at the more granular site level.

### 2. Timeline Estimates & Parallel Batches
The tool calculates an Estimated Completion Time (ETA) based on the email corpus using a heuristic based logic:
*   **User Ordering**: Users are sorted in Ascending Order (Lightest users -> Heaviest users). The lightest users are packed into Batch 1, while the heaviest users usually end up in the final batches.
*   Max(Emails , (Calendar Events + Contacts), In-Place Archives, Group Mails) determines the sorting logic.
*   **Batch ETAs**: Calculated based on the regular emails, in-place archived emails and group mails corpus present in the batch.
*   **Bucketing**: Batches are distributed into Parallel Buckets.
    *   **Example**: If you selected 4 parallel batches, the tool creates 4 "lanes". As soon as Batch 1 finishes in Lane 1, Batch 5 immediately starts in that same lane.
*   **Total ETA** = The duration of the single longest bucket(lane).

---

### Workflow B Results: Microsoft OneDrive / SharePoint

#### 1. Top Level Metrics
For OneDrive we show the following metrics in the UI report.
*   **Total Corpus Size**: Total size of the files discovered in the scan.
*   **Site Collection Count**: Number of sites discovered in the scan.
*   **Subsite Count**: Total distinct subsites identified/scanned.
*   **Document Library Count**: Number of Document Libraries / Drives identified in the scan.
*   **Folder Count**: Total distinct folders identified/scanned.
*   **File Count**: Total distinct files identified/scanned.
*   **Shortcut Count**: Total distinct shortcuts identified/scanned.
*   **List Count**: Total distinct lists identified/scanned.
*   **File Size Distribution**: Distribution of files by size as per the buckets provided in input.
*   **Large Resources Count**: Number of Resources (folders) whose subtree item count is > 500k.

The CSV report would include the above mentioned details along with the granular site level details. If both Personal (OneDrive) and SharePoint Sites were scanned then results for both will be shown separately in the CSV report.

---

### Workflow C Results: Microsoft Teams & Chat Planner

#### 1. Top Level Metrics (Chat & Teams)
The top cards display the total scope of the Chat/Teams migration:
*   **Users & Private Chats**: Total distinct Users, Private Chats, and Private Chat Messages.
*   **Teams & Channels**: Total distinct Teams, Channels, and Channel Messages.

#### 2. Timeline Estimates & Pagination Controls (Chat & Teams)
*   **User & Team Ordering**: Entities are sorted in Ascending Order (Lightest entities -> Heaviest entities) to optimize packing.
*   **Pagination Controls**: The results Gantt chart and batch tables include interactive pagination dropdowns supporting 50, 100, 200, or All items per view.
*   **Total ETA** = The duration of the single longest bucket (lane).

---

## Outputs & Artifacts

### Workflow A Outputs: Exchange Online Planner

Once the scan completes, the tool creates a folder in the `/outputs` directory named with the current timestamp (e.g., `/outputs/20240520_143000/`).

It contains:
1.  **User Report (`user_report.csv`)**: A master list of all users, their item counts, and their suggested Batch (e.g., "Batch 1").
2.  **Batch Files (`suggested batches/`)**: Individual CSV files (Batch1.csv, Batch2.csv) ready for use in migration tool. Headers are formatted as **Source Exchange Email**.
3.  **Logs (`logs.log`)**: Detailed execution logs, including system performance (CPU/RAM) and any API errors encountered.

You can also download just the log file via the **"Export logs"** button or the user report via the **"Export full report"** button and save them in a custom location on your system.

---

### Workflow B Outputs: Microsoft OneDrive / SharePoint

Once the scan completes, the artifacts (CSV report and logs) can be downloaded via the "Export logs" and "Export full report" buttons in the UI.

The artifacts include:
1.  **Site Report**: A master list of all sites and their details (like folder, file counts, corpus size, etc)
2.  **Logs**: Detailed execution logs, including system performance (CPU/RAM) and any API errors encountered.

---

### Workflow C Outputs: Microsoft Teams & Chat Planner

Once the scan completes, the tool creates a folder in the `/outputs` directory named with the current timestamp.

It contains:
1.  **Teams Report (`teams_report_<timestamp>.csv`)**: Master list of analyzed Teams, IDs, channel counts, and assigned migration batch.
2.  **Batch Files (`suggested teams batches/`)**: Individual CSV batch files formatted with the header **Source MicrosoftTeamsID**.
3.  **Logs (`logs_<timestamp>.log`)**: Detailed execution logs, including system performance (CPU/RAM) and any API errors encountered.

You can also download just the log file via the **"Export logs"** button or the full report via the **"Export full report"** button and save them in a custom location on your system.

---

## Terms & Disclaimer

*   **Estimates Only**: The estimations provided by this tool are calculated projections intended for preliminary planning only. Actual migration timelines (ETAs) and batch execution may vary based on network latencies, Microsoft/Google throttling policies, migration configurations, data complexity (e.g., large attachments) and the volume of delta migrations. These figures do not constitute a performance guarantee or a binding service level agreement (SLA).
*   **Security**: This tool runs locally. No credentials or user data are sent to any external server other than the direct Microsoft Graph API calls required to fetch the counts. Log files generated by this script contain personally identifiable information and that you are solely responsible for securing your local environment and these files.
*   **Local Database & Storage**: To enable scan progress persistence and delta tracking, the tool creates and maintains local SQLite databases in the `data/` directory (`data/chat_migration_v2.db` and `data/scan_progress.db`). These databases store metadata, estimated item counts, and progress checkpoints entirely locally. No actual chat message contents or emails are stored. The `data/` directory can be safely deleted or purged at any time after your estimations are completed to reclaim local disk space.
*   **License & Additional Terms**: Use of this tool is governed by the Apache 2.0 license.
*   This is not an officially supported Google product. This project is not eligible for the [Google Open Source Software Vulnerability Rewards Program](https://bughunters.google.com/open-source-security).

migration-planner

Explore Similar Repositories

Was this content helpful?

Recent Feedback

Download README