Skip to content

migration

1 post with the tag "migration"

Moving Out of Box: Graduation, Job Change, or a Closing Account

Move out of Box when the account closes

Box accounts disappear more often than people expect. A university closes graduating students' accounts.[1] A job hands you a departure date. A business stops paying for Box and the admin deletes the account on a schedule. One day the files are there, the next they are a support ticket.

The shape is consistent. Someone with a few hundred gigabytes in Box gets the deadline, asks around for the easiest way out, and the advice comes back as sign up for Google Drive or buy an external drive.[2] Both answers assume a manual download and re-upload, and neither one moves a folder tree. The tooling for the actual job is missing, and that is the job Blober is built for.

The manual route is a download-and-reupload chore

Section titled "The manual route is a download-and-reupload chore"

To move a Box account by hand you download each folder from the web client, then upload it to the new home. Box's web downloads are the hard part: select several files and Box builds a zip that takes a long time to prepare and can time out.[3] Then you are re-uploading the same data, which doubles the bandwidth you spend and the time you lose.

An external drive only helps if you have one, if it is big enough, and if you do not mind the data passing through it before it reaches its real destination.

Blober moves the folder tree, not a flat pile

Section titled "Blober moves the folder tree, not a flat pile"

Blober reads Box through the API and writes each file to the destination you choose, so the structure you see in Box is recreated where the files land:

  • pick Box as the source and pick the destination, which can be Google Drive, pCloud, a local disk, an external drive, a NAS, or an S3-compatible bucket;
  • the folder tree is rebuilt at the destination, so you are not left with one flat pile of files;
  • you can preview the selection and the destination paths before you run anything;
  • transfers resume on their own, so a dropout does not restart the account;
  • no browser zips, no temporary external drive, no script.

Connect Box, connect the destination, and run a workflow with Box as the source.

If your account has a deletion date

Section titled "If your account has a deletion date"

Give yourself room to check the result. The practical sequence is:

  1. run the transfer with the account still open;
  2. open a sample of files at the destination, especially the folders that matter most, and compare file counts between the two sides;
  3. only then close or forget the Box account.

Keep the old account until you have confirmed the copy. A deadline is exactly the situation where a resumable, per-file transfer beats a browser session.

Do I need an external drive to move out of Box?

No. Blober sends files from Box to the destination directly. A local or external drive is just one of the destination options, not a required stop.

Does the folder structure survive the move?

Yes. The folders you select in Box are recreated at the destination.

Can I go from Box to Google Drive, pCloud, or a NAS?

Yes. Any of those can be the destination in the same workflow.

What about Box file size limits?

You can transfer the files your Box account can hold. The limits that apply are your plan's terms, not a Blober restriction.

What if the transfer drops partway through?

Resume the task. Files already transferred stay done and the rest continue.

How do I verify the move before the account closes?

Open a sample of files at the destination and compare file counts for the folders you care about. Keep the Box account until you are satisfied.

Is there a subscription or per-GB fee?

No. Blober is a one-time purchase with a lifetime license.

Blober runs on Mac, Windows, and Linux. No subscription, no transfer fees, no per-GB cap.

Download Blober at blober.io