Most SharePoint migration projects reach the same fork: a focused SharePoint-only tool that excels at fidelity, or a broader platform that handles email and files alongside SharePoint. The table below maps the key differences at a glance.
| Capability | Clone Master | MigrationWiz (BitTitan) |
|---|---|---|
| Source workloads | SharePoint Online only | SharePoint, Exchange, OneDrive, G Suite |
| Destination | SharePoint Online | Microsoft 365 (SharePoint, Exchange, OneDrive) |
| Architecture | Windows desktop app | Cloud SaaS (browser-based) |
| Cross-tenant SharePoint | Yes | Yes |
| Site and subsite migration | Yes | Library-level; site structure not migrated |
| Permission migration | Yes | Partial (library-level, with user mapping) |
| Metadata and column values | Full fidelity | Mapped; custom columns require manual configuration |
| Version history migration | Yes | Optional; can add to migration time significantly |
| Pricing model | Per seat (one product licence) | Per-user migration pass |
| Best for | SharePoint-to-SharePoint migrations (single or cross-tenant) | Multi-workload migrations: email + files + SharePoint together |
What each tool is built for
Clone Master
Clone Master is the SharePoint migration component of the ShareMaster suite, a Windows desktop toolkit for SharePoint Online administration. It is designed specifically for migrating sites, document libraries, and lists within SharePoint Online, including between different Microsoft 365 tenants. Because it works as a desktop application, there are no cloud connectors or SaaS subscriptions to configure: you install it, authenticate to both the source and destination tenants, and run the migration.
The scope is deliberately narrow. Clone Master does not migrate Exchange mailboxes, OneDrive for Business personal drives, or on-premises SharePoint content. Within its scope, that focus pays off in fidelity: column values, content types, version history, and permission structures carry across without requiring manual mapping in most standard configurations.
MigrationWiz by BitTitan
MigrationWiz is a cloud-based migration platform from BitTitan, positioned primarily at MSPs and enterprise IT teams running large-scale tenant consolidations. Its original and strongest use case is email migration (Exchange to Microsoft 365 or G Suite to Microsoft 365), and it has grown to cover OneDrive for Business and SharePoint document libraries as additional workload types.
MigrationWiz runs from a web console. Migrations are queued, monitored, and retried through the BitTitan portal without any on-premises tooling. This makes it practical for remote or distributed migration teams, and for projects where the same project manager oversees mailbox and file migrations simultaneously.
SharePoint Online migration feature comparison
| Feature | Clone Master | MigrationWiz |
|---|---|---|
| Document library migration | Yes, with metadata | Yes, with metadata mapping |
| List migration (non-document) | Yes | Limited; optimised for document libraries |
| Site Pages / news posts | Yes | Not natively |
| Content types | Yes | Partial; may require manual setup on destination |
| Custom columns and lookup values | Yes | Requires column mapping configuration |
| Incremental / delta migration | Yes | Yes |
| Migration scheduling | Yes (run from desktop) | Yes (cloud-queued jobs) |
| Error reporting | Per-item error log in the desktop UI | Per-item error log in the web portal |
Cross-tenant SharePoint migration support
Both tools support cross-tenant SharePoint migrations, but their approach differs. Clone Master connects directly to two SharePoint Online tenants using application credentials and moves content between them as a desktop process: no intermediary cloud service is involved. This suits consultants who do not want client data routed through a third-party cloud.
MigrationWiz handles cross-tenant SharePoint moves at the document library level through the BitTitan cloud platform. The source and destination are both connected to the BitTitan portal, which orchestrates the move. This works well for large, multi-project programmes where a single MSP is coordinating cross-tenant migrations for several clients simultaneously, since all jobs are visible in one portal.
For a detailed look at cross-tenant migration options including Microsoft's own tooling, see the Clone Master vs ShareGate vs Migration Manager comparison.
Metadata and permissions fidelity
Metadata fidelity - how accurately column values, content types, and permissions transfer - is where the tools separate.
Clone Master migrates column values, content types, version history, and permission structures as part of the standard migration operation. Custom SharePoint column types (choice, lookup, managed metadata) carry across without manual mapping in most cases, because Clone Master operates natively within the SharePoint API.
MigrationWiz migrates document content reliably, but custom SharePoint metadata requires explicit column mapping in the project configuration. Permissions can be migrated with user mapping configured in the BitTitan portal, but permission fidelity depends on the complexity of the source environment. For organisations with simple document libraries and straightforward permissions, this is rarely a problem. For libraries with content type inheritance, unique item-level permissions, or complex managed metadata columns, additional configuration effort is typical.
Cost and licensing
The two tools use different cost structures, which makes direct cost comparison depend on migration scale.
Clone Master is priced per seat as part of the ShareMaster suite. A single licence covers the admin running migrations across as many sites, libraries, and tenants as needed. For consultants or MSPs running many SharePoint migrations, the per-seat model becomes more economical as migration volume grows.
MigrationWiz charges per migration pass - each user whose content moves consumes one licence. For small SharePoint migrations, this is cost-competitive. For migrations involving hundreds of users across multiple libraries, the per-user cost adds up fast. MigrationWiz does offer MSP volume pricing through the BitTitan partner programme, which can reduce per-user cost at scale.
Decision matrix: choosing the right tool
| Your situation | Recommended tool |
|---|---|
| Migrating SharePoint sites and libraries only, single or cross-tenant | Clone Master |
| Migrating SharePoint alongside Exchange mailboxes in the same project | MigrationWiz |
| High metadata fidelity needed: content types, custom columns, managed metadata | Clone Master |
| Migrating Site Pages and news posts across tenants | Clone Master |
| MSP managing a large multi-tenant project centrally from a web portal | MigrationWiz |
| Migrating OneDrive for Business personal drives | MigrationWiz (Clone Master does not support OneDrive) |
| Running many SharePoint migrations over time from a single licence | Clone Master |
| Summary verdict | Clone Master for SharePoint-only depth; MigrationWiz for multi-workload breadth |
Explore what Clone Master migrates before comparing against your specific migration requirements.
Frequently Asked Questions
Is MigrationWiz suitable for SharePoint Online to SharePoint Online migrations?
MigrationWiz supports SharePoint document library migrations, including cross-tenant scenarios. It is primarily designed as a multi-workload platform, so for migrations scoped exclusively to SharePoint Online, a SharePoint-specialist tool such as Clone Master typically delivers higher metadata fidelity and simpler configuration.
Can Clone Master migrate Exchange mailboxes or OneDrive for Business?
No. Clone Master is a SharePoint Online specialist. It does not migrate Exchange mailboxes or OneDrive for Business. Organisations that need to move email alongside SharePoint should use MigrationWiz or Microsoft's own tooling for the mailbox workload, then use Clone Master for the SharePoint portion.
Which tool is better for a cross-tenant SharePoint migration?
Both support cross-tenant SharePoint migrations. Clone Master is SharePoint-native and migrates sites, libraries, and lists with full metadata and permission fidelity. MigrationWiz handles cross-tenant moves at the library level and is a strong choice when Exchange or OneDrive workloads are part of the same project.