This article serves as a comprehensive reference guide for migrating data from Dropbox to Google Workspace or Microsoft 365 using CloudM Migrate. It details expected behaviors, connection requirements, and mapping logic necessary for a successful transition.
Important: CloudM Migrate supports Dropbox Business and Enterprise accounts only. Individual / Personal Dropbox accounts are not supported.
Planning & Strategy
Successful Dropbox migrations require a clear understanding of the mapping between Dropbox’s architecture (including Team Spaces and user folders) and the destination's structure.
Feature Compatibility
The following table outlines the data types and features supported during the transition, alongside those that are proprietary to Dropbox or unsupported by the migration engine.
| ✅ Supported | ❌ Not Supported |
|---|---|
|
|
Data Discovery
Before initiating a migration, it is critical to perform a discovery scan. This identifies your total item count, folder depth, and ownership structures to help prevent API throttling or path-length issues.
- For detailed instructions, see: Dropbox Data Discovery.
Configuration
Follow our general Migration Guide as your primary workflow. The links below provide the Dropbox-specific details required to complete the Source configuration steps.
Source Connection & Authentication
The connection to Dropbox requires proper API configuration to authenticate and access the data correctly.
- Dropbox - Source Connection Setup: General requirements and authentication workflow.
- Dropbox - Source Settings: Detailed explanation of source-specific configuration options.
Permission Mapping & Address Replacement
To ensure file and folder access is maintained, CloudM Migrate maps Dropbox roles to the nearest destination equivalent.
- Permission Mapping: Review the Dropbox Permission Mapping Guide for critical details on how roles are translated.
- Address Replacements: If users are changing email domains, you must configure address mapping. See the Domain and Email Address Mapping Guide.
Microsoft 365 Watchpoints
If your destination is OneDrive or SharePoint, the following automated adjustments may occur:
- Character Truncation: File or folder names exceeding destination path limits will be truncated.
-
Illegal Character Renaming: Characters unsupported by Microsoft (e.g.,
" * : < > ? / \ |) will be renamed or replaced.
Destination Configuration Guides
Once the source is configured, refer to these platform-specific guides to complete your setup:
Troubleshooting
If you encounter issues accessing specific files or directories, consult our troubleshooting resources: