Move Existing Project Content to Box



Get Training

1. First decide what you want to keep. Just like moving into a new home, moving to a new content management system requires planning and some housecleaning. Before you dump everything into Box just because you want it off an old server, consider your future productivity and think about what content still has business value. Successful Box customers only migrate the relevant content rather than everything that could potentially have value.

In planning a migration, consider whether or not you have retrieved the file in the last year. Do you really need 30 versions of one file from a completed project? Some Box customers notice that as much as 70 percent of existing content in file stores has no ongoing business value and should not be migrated to Box. Feel free to leave legacy content on your old file server once you move some of it to Box.

2. Consider what you need to have offline. With the increase in solid-state storage and the growing trend of using multiple devices, it’s getting harder to afford the luxury of having every file on hand at all times. As a best practice, sync only your current and active projects for offline use. You should also consider which folders you will need to access while you are offline for an extended period of time.

Figure 1: Sync content you know you'll need when you're offline.

3. How you migrate depends on how many files you need to move. Migrating your content to Box is straightforward as long as you choose the right tool for the job.


How much content do you want to migrate to Box?


Next: Collaborate With Customers And Other Designers

Previous: Define Your Design Folder Structure

Was this article helpful?
0 out of 1 found this helpful