Clouds Connected · Case study
Delivery studyMedia & advertising

3.3 million files and 2.7 TB moved out of Dropbox for a creative agency, into one searchable archive that was live on the Monday after a single weekend cutover.

A Dropbox to SharePoint migration of a creative agency’s entire working history, 2.7 TB, 3.3 million files and 585,000 folders, into a hybrid Microsoft 365 and on-premises archive where the whole corpus is searchable in one place.

Client
Creative production agency
Sector
Media & advertising
Engagement
2.7 TB Dropbox migration to a hybrid Microsoft 365 / SharePoint archive with faceted search
Period
January – December 2024
Anonymised

The client is anonymised, and every figure on this page traces to dated project correspondence. Quotes are verbatim, with their clearance status shown against each one. Named references are available on request. Nothing here has been estimated or rounded up.

In brief

Dropbox to SharePoint migration: what this engagement covered

The challenge

The agency’s entire working history lived in Dropbox: 2.7 terabytes, 3.3 million files, 585,000 folders. For a creative production business that archive is the asset: every campaign, every shoot and every version of every deliverable.

The problem was not storage. After 585,000 folders, finding anything depended on whoever created the folder having named it sensibly, and on the searcher knowing what that person was thinking. Retrieval had quietly become an oral tradition.

Two constraints made the obvious fix awkward. The agency runs on Macs, so any answer had to include working desktop sync rather than a web portal people would resent. And the archive was already tiered in practice: a small body of active work, a larger body of recent but idle material, and a very large cold archive that must stay findable and almost never changes.

The solution

The content took two hops on purpose. Dropbox to SharePoint Online first, then SharePoint Online to an on-premises SharePoint farm. That looks like a detour and it is the entire architecture. Microsoft 365 gives the agency Mac desktop sync, sharing and collaboration; the on-premises search service gives it what Microsoft 365 could not: a full-corpus index across all three storage tiers with custom facets, on hardware sized for the crawl rather than metered by it.

Search was built as two products for two needs. Hot content got faceted search with three custom filters on top of the standard set; warm and cold storage got out-of-the-box search. That split was priced separately in the original estimate, 8 hours for the hot experience and 4 for the rest, because building that interface across a cold archive nobody browses would have been spending the client’s money on a demo.

Metadata was created during the move, not promised after it. A custom migration script populated enterprise metadata columns as documents landed. Migrations that defer tagging produce a new system with the old system’s findability problem.

A proof of concept ran against the real corpus first. The whole tenant was scanned to establish the true numbers, a subset of warm and cold storage was crawled, and roughly 8,000 documents were pushed through the full two-hop path with unified search over them. Every number in the plan afterwards came from measurement.

The estimate said what it would not do. OS installation, domain joins, ongoing infrastructure maintenance, the Sharegate migration licence and Microsoft licence costs were listed as exclusions in the 120-hour quote. The agency’s existing managed provider kept that work, and the boundary never had to be renegotiated.

The results

2.7 TBscanned, assessed and migrated out of a single Dropbox tenant, as 3.3 million files in 585,000 folders
16 to 17 November 2024the cutover weekend; users were working in the new environment on the Monday
16 December 2024the delta since cutover closed through the same two-hop path, so no content was stranded
120 hoursthe original quoted effort, across ten priced deliverables with five stated exclusions
DimensionBeforeAfter
Storagea single Dropbox tenantMicrosoft 365 for live work, on-premises SharePoint for the indexed archive
Findabilityfilename and folder search across 585,000 foldersfaceted search across hot, warm and cold tiers
Metadatafolder hierarchy onlyenterprise columns populated by script during migration
Desktopthe Dropbox clientOneDrive sync on Mac

Finding a three-year-old asset stopped depending on remembering who filed it. Producers search by facet, on client, campaign and asset type, across hot, warm and cold storage in one place, while their Macs sync live work through OneDrive exactly as the Dropbox client used to.

Technologies

Questions we get asked

Dropbox to SharePoint migration: common questions

Can you migrate Dropbox to SharePoint and keep desktop sync on Mac?
Yes, and it drove the architecture here. This agency runs on Macs, so any answer had to include a working desktop sync experience rather than a web portal people would resent. Live work sits in Microsoft 365 and syncs through OneDrive on Mac exactly as the Dropbox client used to.
Why migrate to both SharePoint Online and on-premises SharePoint?
Because neither platform alone did both jobs. Microsoft 365 supplies Mac desktop sync, sharing and collaboration. The on-premises search service supplies a full-corpus index across all three storage tiers with custom facets, on hardware sized for the crawl rather than metered by it. Chaining them meant not compromising on either.
How do you make a 3-million-file archive findable?
Populate metadata during the move, not after it. A custom migration script filled enterprise metadata columns as documents landed, because migrations that defer tagging produce a new system with the old system's findability problem. Search was then built as two products: faceted search with three custom filters for hot content, out-of-the-box search for warm and cold, priced separately at 8 hours and 4.
How long does a 2.7 TB Dropbox migration take?
The bulk moved over a single weekend, 16 to 17 November 2024, with users live on the Monday, and the delta accumulated since cutover was closed by 16 December 2024. The original quote was 120 hours across ten priced deliverables with five stated exclusions, including OS installation, domain joins, ongoing infrastructure maintenance and licence costs, which the agency's existing managed provider kept.
Related work

Other engagements like this one

Work with us

Two ways this usually starts

For consulting partners

SharePoint delivery under your paper

Nine of the ten engagements in this library were contracted through a systems integrator, an ISV or a managed provider, with Clouds Connected as the named SharePoint delivery lead. Your client relationship, your invoice, our platform depth — white-label delivery, escalation cover, or a fixed-scope block of hours.

Every study here is anonymised by default, which is also how we work inside your accounts.

For direct clients

Upgrades, migrations, recovery, patching

SharePoint Server and Microsoft 365 platform work on estates that cannot simply be rebuilt: version upgrades, tenant and content migrations, disaster recovery design and drills, performance root-cause diagnosis, and scheduled security patching on a standing cycle.

Regulated utilities, financial services, aerospace and healthcare. Based in the Greater Toronto Area, Canada; delivery across North America.

Provenance

Where these facts come from

Reconstructed from project correspondence, September 2021 to September 2026. Every figure on this page traces to a dated message, and the source citation for each sits in the accompanying fact sheet. Nothing has been estimated, rounded up, or written on the client’s behalf.

Clouds ConnectedMedia · Dropbox to a hybrid M365 archive