1. Define your migration vision. Before you proceed, consider why you want to migrate content to Box in the first place.
- What are you trying to accomplish?
- What is the specific goal of the migration?
- How will you define success?
- When do you need access to the content?
- Will you focus on shared drives and content or individually owned content?
- Your project goals might include objectives such as decommissioning aging file shares, enabling collaboration outside the firewall and enhancing the ongoing value of relevant business content.
2. Understand your backup needs. Box is a platform for sharing and collaborating on content and is not the best tool for backing up things like .PST files, databases or other blobs of data. Traditional backup systems are often better for those types of files.
3. Understand the best practices for creating files, folders and permissions in Box. The traditional file system-centric rules and permissions are different in Box.
4. Keep things simple. Setting up a new Box system allows you to have a fresh start on your content. Resist the urge to move all of your old content to your new system just because you can. Make sure there is a business case for all content you migrate.
5. Establish a migration team. This team should include individuals from IT, people who share and access files and know what is valuable, your Box administrator and an executive sponsor. Creating a cross functional team
6. Plan a timeline for the migration. Just as it took more than a few days to build up your digital repository, it will take time to curate and migrate content to Box. A timeline can be as simple as start and end dates on your calendar or as detailed as a Gantt chart with milestones.
Previous: Executive Summary - Content Migration
Next: Sample Migration Plan