Migrating from Microsoft 365 to Nextcloud: The Complete Infrastructure and Data Transfer Guide

Moving from Microsoft 365 to Nextcloud is one of the most significant infrastructure decisions an organization can make. It involves migrating not just files, but email workflows, calendars, contacts, collaborative documents, and deeply embedded habits. This guide walks you through every phase of the migration, from initial assessment to final cutover, so you can execute the transition with confidence and minimal disruption.

If you are still evaluating whether Nextcloud is the right replacement for Microsoft 365, read the complete guide to replacing Google and Microsoft with Nextcloud for a comprehensive overview of what Nextcloud offers as a self-hosted productivity platform.

Phase 1: Pre-Migration Assessment

Audit Your Microsoft 365 Usage

Before touching any migration tools, you need a clear picture of what you are actually using. Microsoft 365 is a sprawling ecosystem, and most organizations use only a fraction of it. Start by documenting the following:

• OneDrive storage: Total data volume per user. Check the Microsoft 365 Admin Center for storage reports. Note the largest accounts separately since they will take the longest to migrate.
• SharePoint sites: List every active SharePoint site, its purpose, and who owns it. Many organizations discover abandoned sites during this process.
• Exchange mailboxes: Total mailbox sizes, shared mailboxes, distribution lists, and any mail rules or automated forwarding. Export a list from the Exchange Admin Center.
• Teams channels and chats: Document active Teams channels and any important chat history. Note that Teams chat history cannot be migrated directly to Nextcloud Talk; you will need to archive it.
• Calendar and contacts: Shared calendars, room resources, recurring meeting patterns, and contact groups.
• Third-party integrations: Any apps connected via Microsoft Graph API, Power Automate flows, or SSO integrations that depend on Azure AD.

Define Your Target Architecture

Nextcloud replaces specific Microsoft 365 components. Map your current tools to their Nextcloud equivalents:

Infrastructure Sizing

Your Nextcloud server needs to handle the workload that Microsoft's global infrastructure currently manages for you. For a detailed guide on setting up a production Nextcloud server, see our complete Nextcloud production installation guide.

As a baseline for infrastructure planning, consider these guidelines:

• Small teams (10-50 users): 4 vCPU, 8 GB RAM, 500 GB–2 TB SSD storage. A single server with PostgreSQL can handle this comfortably.
• Medium organizations (50-250 users): 8 vCPU, 16 GB RAM, separate database server, 2-10 TB storage. Consider Redis for file locking and caching.
• Large organizations (250+ users): Multiple application servers behind a load balancer, dedicated database cluster, object storage backend (S3-compatible), 10+ TB storage. Redis Sentinel or Cluster for caching.

Storage tip: Calculate your total OneDrive and SharePoint usage from the Microsoft 365 Admin Center reports, then add 30% headroom for growth over the next 12 months. Do not forget to account for versioning overhead if you plan to use Nextcloud's file versioning feature.

Phase 2: Infrastructure Deployment

Server Setup and Configuration

Deploy your Nextcloud server before beginning any data migration. You want the environment stable and tested before users interact with it. Key infrastructure decisions include:

• Operating system: Ubuntu 22.04 LTS or 24.04 LTS is the most common choice. RHEL/AlmaLinux for enterprise environments requiring long-term support.
• Web server: Apache with mod_php for simplicity, or Nginx with php-fpm for higher concurrency.
• Database: PostgreSQL is recommended for new deployments. MySQL/MariaDB works but PostgreSQL offers better performance at scale.
• PHP version: PHP 8.2 or 8.3, depending on your Nextcloud version. Always check the Nextcloud admin documentation for supported versions.
• Caching: Redis for both local cache and file locking. APCu as the local memcache. This is non-negotiable for production deployments.
• SSL/TLS: Let's Encrypt for certificates, or your organization's existing CA. Nextcloud requires HTTPS.

Essential Apps to Install

Before migration, install and configure the Nextcloud apps that replace Microsoft 365 functionality:

1. Nextcloud Office (Collabora Online) or OnlyOffice: Install one of these for document editing. Collabora integrates more natively; OnlyOffice offers higher Microsoft format compatibility.
2. Group Folders: For shared team workspaces that replace SharePoint document libraries.
3. Nextcloud Talk: For chat and video conferencing (Teams replacement).
4. Calendar and Contacts: These are bundled apps; ensure they are enabled.
5. Nextcloud Mail: If you plan to use Nextcloud as your email client.
6. Deck: For task and project management (Planner replacement).
7. Forms: For surveys and data collection (Microsoft Forms replacement).

Phase 3: Data Migration

OneDrive File Migration

OneDrive migration is typically the largest and most time-consuming part of the process. There are several approaches, each with different trade-offs:

Method 1: Rclone (Recommended for Large Migrations)

Rclone is an open-source command-line tool that can sync files between OneDrive and Nextcloud (via WebDAV). It handles large volumes efficiently and can resume interrupted transfers.

# Configure OneDrive remote
rclone config
# Select "Microsoft OneDrive" and follow OAuth setup

# Configure Nextcloud remote
rclone config
# Select "WebDAV" and enter your Nextcloud URL

# Sync files from OneDrive to Nextcloud
rclone sync onedrive: nextcloud:/migrated-files/ \
  --transfers 4 \
  --checkers 8 \
  --progress \
  --log-file=/var/log/rclone-migration.log

# For a dry run first:
rclone sync onedrive: nextcloud:/migrated-files/ --dry-run

Run rclone with the --dry-run flag first to verify what will be transferred. For organizations with multiple users, script the process to iterate through each user's OneDrive.

Method 2: OneDrive Desktop Sync + Upload

For smaller teams, the simplest approach is to let OneDrive sync all files to a local machine, then upload them to Nextcloud. This is straightforward but slow for large datasets and does not scale well beyond 10-20 users.

Method 3: Microsoft Graph API Export

For programmatic control, use the Microsoft Graph API to enumerate and download files. This is useful when you need to transform file structures during migration or apply custom logic for file placement. Requires Azure AD application registration with appropriate permissions.

SharePoint Migration

SharePoint sites require more careful planning than personal OneDrive folders. For each SharePoint site, decide whether it becomes a Group Folder, a regular shared folder, or is archived. Document the permission structure of each site since SharePoint permissions are often more granular than what you will replicate in Nextcloud.

Use rclone with the SharePoint remote type to download site content. Note that SharePoint metadata (custom columns, content types, workflows) does not migrate. If your organization relies heavily on SharePoint metadata, plan for manual reorganization after migration.

Email Migration Options

Email is the most complex part of a Microsoft 365 migration because Nextcloud is not primarily an email server. You have three options:

Option A: Nextcloud Mail with External IMAP Server

Deploy a mail server (such as Mail-in-a-Box, Mailcow, or iRedMail) alongside Nextcloud, then configure Nextcloud Mail as the web client. This gives users a unified interface but requires maintaining a separate mail infrastructure.

Option B: Keep Email Separate

Migrate email to a dedicated email service (Fastmail, Proton Mail, or your own mail server) and use Nextcloud only for files, calendar, contacts, and collaboration. Many organizations find this approach cleaner because email is a specialized workload.

Option C: Hybrid Approach During Transition

Keep Microsoft 365 email running during the transition period while migrating everything else to Nextcloud. This reduces risk but means maintaining Microsoft licenses longer. Use IMAP sync tools like imapsync to migrate mailboxes when you are ready to cut over email.

# Example imapsync command for mailbox migration
imapsync \
  --host1 outlook.office365.com --user1 user@company.com --password1 "password" --ssl1 \
  --host2 mail.company.com --user2 user@company.com --password2 "newpassword" --ssl2 \
  --automap --exclude "Junk Email|Deleted Items"

Calendar Migration (CalDAV)

Outlook calendars can be exported and imported into Nextcloud Calendar:

1. In Outlook, go to Calendar > Share > Email Calendar, or use the Outlook desktop client to export as .ics files.
2. Alternatively, use the Microsoft Graph API to export calendar events programmatically.
3. Import .ics files into Nextcloud Calendar through the web interface or via CalDAV.
4. For shared calendars, designate one person to export and reimport each shared calendar, then re-share with the appropriate groups in Nextcloud.

Important: Recurring events, especially those with exceptions and modifications, are the most fragile part of calendar migration. Test a sample of complex recurring events before migrating everything. Some recurrence patterns may need manual adjustment.

Contacts Migration (CardDAV)

Contacts migration is relatively straightforward:

1. Export contacts from Outlook as a .csv file or use the People section of Outlook on the web to export as .vcf (vCard).
2. Import the .vcf file into Nextcloud Contacts.
3. For shared contact lists, export from the shared mailbox or distribution list and import into a shared Nextcloud address book.

Phase 4: User Account Setup

Authentication and User Provisioning

If your organization uses Azure Active Directory, you have several options for user management in Nextcloud:

• LDAP/AD integration: If you maintain an on-premises Active Directory or plan to deploy one, Nextcloud can authenticate directly against it. This is the most seamless option for organizations already using AD.
• SAML/SSO: Configure Nextcloud as a SAML Service Provider with Azure AD (or any other IdP) as the Identity Provider. This allows single sign-on and automatic user provisioning.
• Manual creation: For smaller teams, create accounts directly in Nextcloud. Use the occ command for batch creation from a CSV file.

# Batch create users from a CSV (username,password,displayname,email)
while IFS=, read -r username password displayname email; do
  sudo -u www-data php occ user:add --password-from-env --display-name="$displayname" --group="employees" "$username"
done < users.csv

Group and Permission Structure

Map your Microsoft 365 security groups and Teams to Nextcloud groups. Create groups before migration so you can assign Group Folder permissions immediately:

• Create a Nextcloud group for each Microsoft 365 security group or Team that needs shared file access.
• Set up Group Folders with appropriate permissions (read, write, create, delete, share) for each group.
• Configure quota limits per user or group to match your storage allocation plan.

Phase 5: Parallel Running Period

Never perform a hard cutover. Run both systems simultaneously for a defined period, typically two to four weeks. During this period:

• Week 1: Deploy Nextcloud to a pilot group of 5-10 enthusiastic users. These become your internal champions and first-line support. Gather feedback aggressively.
• Week 2: Expand to department leads and power users. Address any issues discovered by the pilot group. Begin onboarding training for the broader organization.
• Week 3-4: Roll out to all users. Set OneDrive to read-only (if possible) to prevent data divergence. New files should be created exclusively in Nextcloud.

During the parallel running period, designate Nextcloud as the "source of truth" for new documents as early as possible. The biggest risk in dual-running environments is data divergence, where two versions of the same file exist in different systems.

Phase 6: Cutover Strategy

Pre-Cutover Checklist

1. All user accounts are created and tested in Nextcloud.
2. All OneDrive and SharePoint data has been migrated and verified (spot-check file counts and sizes).
3. Calendar and contacts have been imported and tested for all users.
4. Nextcloud desktop clients are installed on all workstations.
5. Nextcloud mobile apps are installed on managed devices.
6. Collabora Online or OnlyOffice is functional and tested with sample documents.
7. Backup procedures are in place for the Nextcloud server.
8. DNS records are updated (if applicable, for custom domains).
9. IT support team has been trained on Nextcloud administration.

Cutover Day

Schedule the cutover for a Friday afternoon or a weekend to give users the buffer of a non-working day. On cutover day:

1. Run a final rclone sync to catch any last-minute file changes.
2. Set Microsoft 365 to read-only or disable new file creation (via compliance policies).
3. Send the cutover announcement email with links to Nextcloud, client download pages, and the internal help guide.
4. Have IT support on standby for the first Monday after cutover.

Post-Cutover Monitoring

For a realistic view of what the first three months look like, including common challenges and optimization tips, read our guide on the first 90 days after replacing Google Workspace with Nextcloud. While that guide focuses on Google Workspace, the post-migration dynamics are remarkably similar for Microsoft 365 migrations.

• Monitor Nextcloud server logs daily for the first two weeks.
• Track sync client errors through the admin dashboard.
• Watch for storage consumption spikes (users uploading new content plus migrated content).
• Schedule weekly check-ins with department leads for the first month.

Common Migration Challenges and Solutions

File Format Compatibility

Microsoft Office formats (.docx, .xlsx, .pptx) open natively in Collabora Online and OnlyOffice. However, complex formatting, macros, and advanced Excel features may not render perfectly. Test your most critical documents before migration and identify any that need special handling.

Outlook Add-ins and Plugins

If your organization relies on Outlook add-ins (CRM integrations, scheduling tools, etc.), identify alternatives before migration. Many popular tools offer web-based or standalone versions that are not tied to Outlook.

Large File Handling

OneDrive supports files up to 250 GB. Nextcloud's maximum file size depends on your PHP and web server configuration. Ensure your upload_max_filesize, post_max_size, and web server timeout settings accommodate your largest files. For very large files, configure Nextcloud's chunked upload settings.

External Sharing Links

OneDrive and SharePoint sharing links will break after migration. Inventory all externally shared links before cutover, recreate them as Nextcloud public shares, and notify external recipients. There is no automated way to preserve existing links.

Microsoft 365 License Wind-Down

Do not cancel Microsoft 365 licenses on cutover day. Maintain licenses for at least 30 days post-cutover to ensure you can access historical data if needed. After 30 days, downgrade to a lower-tier plan (such as Exchange Online Plan 1 for email-only access) if you have not migrated email yet. Fully cancel only when you are confident all data has been migrated and verified.

Security Considerations

Your Nextcloud deployment inherits security responsibilities that Microsoft managed for you. Ensure you address these areas:

• Server hardening: Firewall configuration, SSH key-only access, automated security updates.
• Nextcloud security scan: Run the Nextcloud Security Scan (scan.nextcloud.com) to verify your configuration.
• Brute-force protection: Enable and configure Nextcloud's built-in brute-force protection.
• Two-factor authentication: Enable TOTP or WebAuthn for all users, especially administrators.
• Encryption: Enable server-side encryption if required by your compliance framework. Note that server-side encryption has performance implications.
• Audit logging: Install and configure the Nextcloud audit log for compliance tracking.

Conclusion

Migrating from Microsoft 365 to Nextcloud is a multi-week project that touches every aspect of your organization's digital workflow. The technical migration (files, calendars, contacts) is the straightforward part. The real challenge is organizational: changing habits, training users, and maintaining productivity during the transition. Plan thoroughly, run systems in parallel, and invest in user training. The payoff is complete control over your data, predictable costs, and freedom from vendor lock-in.

For a comprehensive understanding of how Nextcloud replaces the full Microsoft and Google ecosystem, revisit the pillar guide on replacing Google and Microsoft with Nextcloud. And when you are ready to help your team adapt to the new platform, the team onboarding playbook provides a structured approach to user adoption. For a detailed comparison of the cost and sovereignty implications, see our Microsoft 365 vs Nextcloud infrastructure comparison.