Direct Migration to Nextcloud

Direct Migration discovers all SharePoint Document Libraries and Teams document libraries across your tenant and automatically creates one migration job for each — so you can go straight from discovery to migration without a prior Business Intelligence scan. OneDrive accounts are not auto-identified during enumeration; they are configured separately in the OneDrive dialog — see OneDrive configuration below.

Content Governance enumerates the entire tenant and creates one job item per library or OneDrive in the Job list. Each job is created in the context of the source tenant and is ready to migrate all files, folder structure, version history, and metadata to the configured Nextcloud destination. If you select job status Ready, all jobs will start automatically. If you select Hold, you can start them individually at your own pace.

Migration scope
Teams Libraries / SharePoint Libraries Content Governance discovers all SharePoint Document Libraries and Teams document libraries across the entire tenant and creates one migration job per library.
OneDrive OneDrive accounts are not auto-identified during tenant enumeration. They are configured separately in the OneDrive dialog — see OneDrive configuration below. One migration job is created per mapped OneDrive.
OneDrive configuration
  • Click Next
 After the tenant enumeration step, click Next to open the OneDrive configuration dialog. OneDrive accounts are configured here because each OneDrive must be paired with a target Nextcloud user and an app password before it can be migrated.
  • Automatic mapping
 Content Governance matches each Microsoft 365 user to its corresponding Nextcloud username automatically. Use this when M365 and Nextcloud identities follow a consistent naming convention across both systems.
  • Manual mapping
 Map M365 users to Nextcloud users individually with manual intervention. Use this when identities differ between systems, or when you want to scope OneDrive migration to a specific subset of users.
  • App password
 For each mapped user, supply the Nextcloud app password used to authenticate WebDAV access during migration.
SharePoint metadata — automatic MetaVox column creation
Automatically create SharePoint custom columns in MetaVox app When enabled, Content Governance inspects every SharePoint library and reads all custom columns defined there — including Choice, Text, Date, Numeric, and Managed Metadata column types. For each library, Content Governance automatically creates matching metadata columns in the MetaVox app in Nextcloud, maps and transfers all source values from SharePoint to MetaVox during migration, and creates a MetaVox view so the columns are immediately visible and usable in Nextcloud. This means your entire SharePoint metadata landscape is fully preserved in Nextcloud — with zero manual column configuration required.
SharePoint views — automatic MetaVox view creation
Automatically recreate SharePoint views in MetaVox app When automatic column creation is enabled, Content Governance additionally reads every view defined on each SharePoint library and recreates it as a corresponding view in the MetaVox app in Nextcloud. For each SharePoint view, Content Governance creates a matching MetaVox view with the same columns in the same order and applies the first sort column from the SharePoint view’s sort specification — preserving the view definition to the extent that MetaVox currently supports. Your users land in Nextcloud with the same list layouts they already know, with zero manual view configuration required.
Job status
Ready Migration jobs are set to Ready immediately after creation and will be picked up and executed by Content Governance automatically. Choose this option to start migrating right away.
Hold Migration jobs are created but remain paused. No migration takes place until you explicitly start them from the Job list. Choose this option if you want to review or adjust jobs before migration begins.