SharePoint to kDrive Migration: Complete Guide

SharePoint is often at the heart of collaboration for businesses using Microsoft 365. Migrating to kDrive is a more complex project than a simple OneDrive migration. Here is our guide for a successful transition.

Discover kDrive

SharePoint vs kDrive: Understanding the Differences

Before migrating, it\'s important to understand what sets these two solutions apart:

What Can Be Migrated

• Document libraries – All your files and folders
• Folder structure – Directory hierarchy preserved
• Basic metadata – Creation/modification dates
• Shared files – Shares need to be manually recreated

What Cannot Be Migrated Directly

• SharePoint sites – No equivalent in kDrive
• SharePoint lists – Use an alternative (Notion, Airtable, etc.)
• Workflows – Need to be recreated with other tools
• Custom metadata – SharePoint columns are not transferable
• Complex permissions – Need to be reconfigured in kDrive
• Version history – Only the latest version is migrated

Migration Strategy

Phase 1: Audit and Inventory

Start by documenting your SharePoint environment:

1. List all sites – Team sites, communication sites, etc.
2. Identify the libraries – Data volume, number of files
3. Document permissions – Who has access to what
4. Identify dependencies – Workflows, connected applications
5. Assess actual usage – Some sites may be inactive

Phase 2: Planning the kDrive Structure

Define how to organize your data in kDrive:

Phase 3: Exporting SharePoint Data

Method 1: OneDrive sync then copy

1. Sync SharePoint libraries with the OneDrive client
2. Wait for all files to download locally
3. Copy files to kDrive (via the kDrive client)

Advantages: Simple, no third-party tools needed
Disadvantages: Requires significant local disk space

Method 2: Export via the SharePoint interface

1. In SharePoint, select the files/folders
2. Click "Download" (creates a ZIP)
3. Unzip and upload to kDrive

Advantages: No synchronization needed
Disadvantages: Limited for large volumes, loss of metadata

Method 3: Third-party migration tools

For large volumes, specialized tools can help:

• rclone – Command-line tool, free
• MultCloud – Cloud-to-cloud service
• Custom PowerShell scripts

Phase 4: Import into kDrive

1. Create the folder structure in kDrive
2. Upload files (web interface, desktop client, or mobile app)
3. For large volumes, use the desktop client which handles transfers more efficiently

Phase 5: Configuring Shares

Recreate access in kDrive:

1. Identify folders to share
2. Invite users or groups
3. Set permissions (read, write)
4. Configure public share links if needed

Phase 6: Training and Transition

1. Train users on kDrive
2. Install the kDrive client on workstations
3. Communicate about the changes
4. Set a switchover date

Handling Non-Migratable Features

SharePoint Sites / Intranet

If you use SharePoint as an intranet, consider:

• Notion – Team wiki and documentation
• Confluence – Collaborative documentation
• A traditional website – Hosted with Infomaniak

SharePoint Lists

To replace SharePoint lists:

• Airtable – Flexible database
• Notion – Built-in databases
• Collaborative spreadsheet – In kDrive (OnlyOffice)

Workflows

For automation:

• Zapier – Multi-application automation
• Make (Integromat) – Complex workflows
• n8n – Self-hostable open source alternative

Migration Checklist

Conclusion

Migrating from SharePoint to kDrive is a transformative project that goes beyond simple file transfer. It\'s an opportunity to simplify your environment, clean up obsolete data, and regain control of your information.

For businesses with heavy SharePoint usage (intranet, workflows), plan for complementary solutions. For those primarily using SharePoint as shared storage, kDrive is a direct and simpler replacement.

Discover kDrive