Movebot offers a simple and easy way to migrate tens to thousands of users. This is designed for more complex migrations that require user and drive mappings, versions and permissions.
Step 1: Create a new migration
- Click Create New Migration at the top of your screen
- Then select Organization/Project Migration
Step 2: Name your Project
- Provide your project a name, then click Save and Next
Step 3: Select your Source Platform
- Select your source platform from the drop down
- Authenticate or connect to your platform (this differs based on your chosen platform, see here how to configure all platforms)
- Click Next Step
Step 4: Select your Destination Platform
- Select your destination platform from the drop down
- Authenticate or connect to your platform (this differs based on your chosen platform, see here how to configure all platforms)
- Click Next Step
Step 5: Select your Users, Shared Drives and Folders
- Select the means you would like to discover, map and configure your users, shared drives and folders
- When ready, click Next Step
| Auto-discover users and drives | Movebot will automatically scan both the source and destination platforms and compare names, based on these names it will map users and shared drives between the source and destination. If it cannot find a mapping you will be able to manually map this later. |
| Import user and drive mapping from CSV file | Upload a CSV of your desired source and destination mappings providing you full autonomy to create many migrations with a single CSV upload, or enabling you to upload stages of migrations. |
| Add User/Drive Mapping | Manually map a user or shared drive between source and destination using Movebots intuitive selector. |
Step 6: Persist Permissions and Modtime
- Select whether you would like to preserve permissions based on:
- Individual Owned Shared Folders
- Individual Owned Shared Files
- Note: If your usernames or emails are not identical at both the source and destination, there is the option to manually input the users source and destination username. Additionally, contact our team for assistance.
- Enable or Disable the preservation of modified time
- Enable or Disable the migration of file versions
Step 7: File Settings
- You can now choose to include/exclude files within the migration, or use REGEX to filter further. By default Movebot will attempt to migrate all files.
- You can also tweak additional settings as below:
| Filename Sanitization | Some providers such as OneDrive don't allow certain characters in file names, we will make amendments so that all your files make it across. |
| Doctype Conversion | Google file types such as .gdoc, .gsheet and .gslide aren't readable from other providers, we will automagically convert the files to .docx, .xlsx and .pptx during the migration. |
| Duplicate Santization | Google Drive allows multiple files and folders with the same name, with this enabled and if there are two or more files with the same name, we only move the most recently updated file. |
We recommend leaving the above as default to ensure you migration performs optimally.
- Click Next when you are ready
Step 8: Migration Settings
-
You can configure additional migration settings here to further optimize or tweak your migration
- Click Save
| Delta Enabled | Only move files that have been modified since the last migration |
| Worker Nodes | Improve performance by adding extra Movebots (computes) to process your data |
| Post Upload Check | When enabled, on completion of the migration we will run through and check that the files made it across. Some providers take time to process the files and having this enabled can make it seem that files have not been transferred and cause the migration to fail. |
| Enable Checksum Verification | When enabled, Movebot will check the hash on the source and destination file to ensure the file integrity has not changed. |
| Worker Threads | We highly recommend not touching this unless you know what you are doing. This is set to the best for your cloud provider by default. |
| Worker Region | Choose the region for your migration to run from to maintain data sovereignty governance. |
| Worker Affinity Tag | This feature is only used if the team at Movebot provide you a tag. |
Step 9: Managing your Migration
- You are now taken to your migration dashboard where you can:
| Start/Stop your migrations | You can either select all your migrations and run them or select specific ones and run them one by one. |
| Run a Discovery Scan | This will scan your source platform and see what issues we will attempt to resolve, how much data and other information displayed in our analytics. |
| Delete | You can delete your migrations |
| Copy and Edit (Clone) | If you hover over a migration and click the ellipse menu on the right handside you can effectively clone the migration to then edit the source and destination folder/user/drive |
| Add more users/drives | On the top right when under a project you can add more users via any of the three means previously described. |
| Alter the projects settings or individual migration | You can alter the overall project settings. Each migration will inherit the projects settings. However, you can modify the settings on per a migration basis (i.e. disable file conversion, add more compute, etc.) |
| Overview/Logs | See the real-time logs for the migration, errors, graphs and analytics. |
If you need any assistance or have any questions, please send through an email to support@movebot.io - the team is more than happy to help.