Case Study Box to ShareFile

GS RichCopy 360 Enterprise Case Study

Tech company migrated 11,000 users from Box to ShareFile — on deadline, with a lean team.

A growing technology company needed a cloud-to-cloud migration from Box to Citrix ShareFile — 11,000 user accounts and roughly 300 TB of data. Before reaching out to us, they had already spent two months working with external consultants on a different solution that simply couldn't keep up at enterprise scale.

11,000
User accounts migrated
300 TB
Total data moved
6 mo.
End-to-end timeline
1 team
Lean internal staff
The Situation

A hard deadline. A stalled migration.

The company had a hard internal deadline tied to a contract renewal cycle. Two months in, the original Box to ShareFile migration tool and consulting team were running into one issue after another: failed transfers, no clean way to track which user accounts had completed, and no realistic path to finishing on time.

The consulting bill kept growing, the data wasn't moving, and leadership was losing confidence in the project.

That's when they called us.
Why the first approach stalled

11,000 one-off problems instead of one pipeline

The original plan had been to migrate everything as one large effort, account by account, with consultants manually building and tracking jobs. At 11,000 accounts, that approach broke down quickly.

Box API throttling

Box's aggressive rate limits kept derailing long-running transfers, with no built-in retry or resume logic to recover gracefully.

No central job orchestration

Every account was being treated as a one-off, leaving no visibility into what had finished, what had failed, and what hadn't started.

Manual job setup overhead

Building and configuring each user's migration by hand was eating up consultant hours faster than data was actually moving.

No phased rollout plan

Any failure put the whole timeline at risk instead of being contained to a single wave of users.

The Solution

How GS RichCopy 360 Enterprise solved it

We worked with the customer to flip the approach. Instead of treating 11,000 accounts as 11,000 separate problems, GS RichCopy 360 Enterprise — a purpose-built enterprise file migration software — turned the entire effort into a single, structured pipeline.

1

User List in a CSV

The customer pulled a complete list of every Box user and their associated folders into a CSV — a format their team could review, verify, and refine before any data moved.

2

Bulk Job Import

GS RichCopy 360 Enterprise imported the CSV and automatically built every migration job — one per user, plus separate jobs for department and company shares — with source, destination, and scheduling pre-configured.

3

Phased Execution

Smaller divisions went first as a controlled rollout, validating the workflow end-to-end. Each successful wave added confidence, scaling up to larger divisions and finally company-wide shares.

Throughout the migration, RichCopy 360's built-in retry logic, throttling controls, and detailed per-job logging handled the Box API rate limits gracefully and gave the team real-time visibility into every wave. And when questions came up — tuning concurrency for a particular wave, interpreting a log, validating a job before kicking off a larger batch — the customer had direct access to our support team.

Unlike a custom script or a one-off consultant engagement, this was a supported product with engineers behind it, and that backing was a key reason a small internal team was able to run a migration of this scale with confidence. The customer's IT staff handled access provisioning on the ShareFile side in parallel, so users came online as each wave completed.

The Results

A project plan instead of a crisis.

Real numbers, real deadline met, real customer.

300 TB
11,000 user accounts migrated from Box to ShareFile, in full — files, folders, and entire user data sets.
6 Months
End-to-end cloud-to-cloud migration completed — roughly half the timeline a manual migration at this scale typically requires.
On Time
Internal deadline met, despite the two-month head start the project had lost on the previous solution.
Lean Team
A small internal IT team ran the entire migration, backed by direct access to GS RichCopy 360 support — no large dedicated team, no extended consulting engagement.
The Takeaway

When migrations fail, it's rarely the data's fault.

Large cloud-to-cloud migrations don't fail because the data is too big. They fail because the work isn't structured — and because teams get stranded the moment something unexpected happens. Once the customer had a clean inventory, an automated job pipeline, a tool built for the realities of cloud APIs at scale, and a vendor support team they could actually pick up the phone and call, 11,000 users and 300 TB stopped looking like a crisis and started looking like a project plan.

Planning a cloud-to-cloud migration?

Replace stalled migrations and brittle scripts with GS RichCopy 360 Enterprise — trusted by IT teams worldwide to move data between Box, ShareFile, OneDrive, SharePoint, Dropbox, Google Drive, AWS, Azure, and on-prem servers.