Cloud storage migration

Box → Google Drive

Move Box folders, files, versions, collaborations, groups, metadata, notes, shared links, and enterprise controls into Google Drive with explicit permission and scale safeguards.

Typical timeline15–40 business days75–145 hours active work

Statusneeds review

Source testedBox documentation reviewed 2026-07-19

Destination testedGoogle Drive documentation reviewed 2026-07-19

Last reviewed2026-07-19

Sources3

Before you migrate

Should you make this move?

Both platforms have a case. Compare what you gain with what you give up before scheduling the cutover.

Current platform

Box

Reasons to stay

Enterprise governance, compliance, and content workflows are unusually deep
Managed sync, sharing, version history, and access controls reduce file-server work

Reasons to leave

Cost and administration can be excessive for straightforward file synchronization
Shared links, permissions, comments, and ownership models do not map cleanly

New platform

Google Drive

What gets better

Docs, Sheets, sharing, search, and collaboration are deeply integrated
Managed sync, sharing, version history, and access controls reduce file-server work

What gets worse

Shared-drive ownership and Google-native formats complicate complete portability
Shared links, permissions, comments, and ownership models do not map cleanly

Best of the move

Google Drive: Docs, Sheets, sharing, search, and collaboration are deeply integrated. This removes a major source-side concern: Cost and administration can be excessive for straightforward file synchronization.

Worst of the move

What you lose: Enterprise governance, compliance, and content workflows are unusually deep. What you inherit: Shared-drive ownership and Google-native formats complicate complete portability.

01At a glance

Know the shape of the move.

Transfer outcome12 features audited

Clean0

Partial8

Manual1

Lost3

Mapping route9 of 9 fields have a destination path

SourceBox9 mapped fields

Automatic2

Transform4

Manual3

Unsupported0

DestinationGoogle Drive9 supported paths

This timeline assumes

Up to 250 users, 2 million objects, and 5 TB of file data
Administrators control both tenants and have approved user and group identity maps.
The source remains read-only and licensed until object, version, link, and access checks pass.
A representative user, shared container, and native-document set are migrated first.
The migration team records evidence for every blocking verification check.

02Loss matrix

What survives the move.

“Partial” and “manual” are not footnotes. They are work that must be scheduled and verified.

Item	Outcome	Impact	What happens	Mitigation
Box files, folders, versions, and collaborations	partial	critical	Google supports these classes, but version depth and collaborator roles depend on settings and mapping.	Pilot every role and the approved revision depth.
Box Notes	lost	critical	Google lists Box Notes as unsupported in Workspace Migrate.	Export Notes separately and convert or archive each one.
Restricted child permissions	lost	critical	Shared drives do not support children that are more restricted than their parent.	Redesign container boundaries before migrating sensitive content.
Box API scale and large owners	partial	high	Version load and per-user object volume can materially extend processing.	Prescan object and version counts, shard where supported, and keep schedule contingency.
Files and folders	partial	critical	Core binaries and folders can move while unsupported names, sizes, paths, or object types are skipped.	Reconcile every source object to a destination object, exclusion, or approved archive.
Ownership and user identity	partial	critical	Ownership depends on a complete identity map and destination licenses.	Provision users first and explicitly assign orphaned content.
Sharing and permissions	partial	critical	Roles, inheritance, restricted children, groups, and external collaborators differ.	Apply and test a signed destination access matrix.
File versions	partial	high	Migration tools may omit versions, cap revisions, or increase duration substantially when versions are enabled.	Choose a retention depth and compare revision counts on a pilot.
Cloud-native documents	partial	critical	Provider-native documents may convert, flatten, export to office formats, or remain unsupported.	Classify and test every native document type before bulk migration.
Comments, tasks, and annotations	lost	high	Collaboration metadata rarely becomes destination-native history.	Resolve active work and archive required evidence.
Shared drives, team folders, and shortcuts	partial	critical	Container and link semantics do not map one-to-one.	Design target containers and detect duplicate or broken shortcut outcomes.
Public and external links	manual	critical	Existing URLs and link permissions do not remain stable.	Inventory critical links and notify owners of replacements.

03Field and feature mapping

Where each thing goes.

Source	Destination	Method	Notes
Box user or owner	Google Drive user or owner	manual	Provision and license identities before content.
Personal root	Destination personal root	transform	Keep source identity and path in the manifest.
Team folder or shared space	Destination shared container	manual	Approve ownership and membership first.
Folder	Folder	automatic	Validate path length, characters, and item limits.
File	File	automatic	Compare size and checksum.
Cloud-native document	Destination native or office document	transform	Record conversions and unsupported features.
Permission or collaboration	Destination access role	transform	Map role and inheritance explicitly.
Version	Destination revision or archive	transform	Apply the approved retention depth.
Shared link or shortcut	Destination link or shortcut	manual	Do not assume URL continuity.

04Before you begin

Make the move recoverable.

Backup procedure

Create the source-of-truth backup

Preserve Box data, configuration, and operating evidence before any destination write.

Export Box file, folder, owner, permission, link, version, metadata, and shared-container inventories.
Download or archive every cloud-native and otherwise unsupported content class.
Record counts, bytes, versions, owners, collaborators, external links, and legal holds.
Hash raw manifests and representative binaries.

Proof to capture: A signed manifest reconciles every scoped record class, runtime dependency, export file, count, and hash.

Transformation · Official inventory tools and migration workbook

Identity, container, and permission map

Preserve ownership and least-privilege access.

Inventory source values and exceptions.
Define explicit destination mappings.
Reject unmapped critical records.

Proof to capture: Save the input, output, command or tool settings, warnings, and final item counts.

Transformation · Official migration service, checksum tool, and exception ledger

Object and native-document migration

Copy supported files and disposition every exception.

Normalize encoding, dates, identifiers, and blanks.
Run a representative pilot.
Reconcile accepted, rejected, and transformed rows.

Proof to capture: Save the input, output, command or tool settings, warnings, and final item counts.

05Handle with care

The things most likely to hurt.

These are operating limits. Treat every “Stop if” condition as a blocked migration, not a suggestion.

Migration

A completed job hides skipped or converted objects

criticalpossible likelihood

Headline completion masks unsupported files, native documents, versions, or path errors.

Consequence: Users discover missing or altered work after cutover.
Mitigation: Reconcile every source object and exception.

Stop if: Any critical object lacks a destination, exclusion, or archive.

Access

Permissions broaden during container conversion

criticalpossible likelihood

Restricted children or external collaborators inherit unintended access.

Consequence: Confidential files are disclosed.
Mitigation: Apply and test a signed access matrix.

Stop if: An unauthorized test identity can open a restricted file.

Cutover

Both tenants accept edits

criticalpossible likelihood

Users or integrations update source and destination copies.

Consequence: File histories diverge.
Mitigation: Freeze source writers and apply one final delta.

Stop if: An unexplained post-freeze source change appears.

06Precise timeline

Do the work in this order.

Estimate forUp to 250 users, 2 million objects, and 5 TB of file data

Total elapsed15–40 business days

Active work75–145 hours

BufferAdd time for more than 250,000 objects per owner, many versions, Box Notes, metadata templates, or restricted permissions.

Days 1–3Inventory and decisions2–3 days

Days 3–5Backup and reconcile1–3 days

Days 5–12Map and pilot3–8 days

Days 10–20Final delta and switch1–5 days

Days 12–40Observe and close3–10 days

1
Days 1–3 · inventory
Inventory and decisions
6–12 hours active2–3 days elapsedOwner review waiting
- Inventory Box data, features, users, domains, and integrations.
- Approve scope, owners, mappings, and exclusions.
Depends on: Box and Google Drive administrator access
Stop / go checkpoint
Export?
Go when: Every critical item has an owner and disposition.
Stop when: Consent, billing, access, or system ownership is unclear.
2
Days 3–5 · backup
Backup and reconcile
5–10 hours active1–3 days elapsedExport processing waiting
- Create immutable exports and configuration evidence.
- Reconcile counts, totals, and hashes.
Depends on: Approved inventory
Stop / go checkpoint
Transform?
Go when: Source totals and export manifests agree.
Stop when: Any critical dataset or configuration is absent.
3
Days 5–12 · pilot
Map and pilot
10–35 hours active3–8 days elapsedDestination processing and review waiting
- Configure Google Drive and transform representative data.
- Run a pilot containing normal records and every critical edge case.
Depends on: Verified backup
Stop / go checkpoint
Scale?
Go when: Pilot mappings, behavior, access, and evidence pass.
Stop when: Any critical check fails or produces unexplained variance.
4
Days 10–20 · cutover
Final delta and switch
5–25 hours active1–5 days elapsedDNS, import, or sync propagation waiting
- Freeze production writes in Box.
- Apply the final delta, switch ownership, and run blocking checks.
Depends on: Passed pilot and approved rollback
Stop / go checkpoint
Open production?
Go when: Counts reconcile and one destination system owns production.
Stop when: A source writer remains active or a blocking check fails.
5
Days 12–40 · observe
Observe and close
3–18 hours active3–10 days elapsedOperating-cycle evidence waiting
- Monitor one complete operating cycle.
- Sign the verification report and close rollback only after stability.
Depends on: Verified cutover
Stop / go checkpoint
Close rollback?
Go when: No trigger occurs during the agreed observation period.
Stop when: Data, access, delivery, routing, or business results regress.

07The point of change

Cut over with a way back.

Go live

Cutover

Make Google Drive the only production system without losing the final Box delta.

Recommended window: A low-volume weekday morning with platform, data, DNS, and business owners available.

Freeze production writes and scheduled actions in Box.
Export, transform, and reconcile the final delta.
Apply the approved delta to Google Drive.
Switch domains, forms, integrations, sending, or sync ownership as applicable.
Run every blocking verification check and keep the source intact.

Proof to capture: Google Drive owns production, totals reconcile, and every blocking check has durable evidence.

Return to safety

Rollback

Return production ownership to Box without losing destination-era changes.

Deadline: Within seven days and before source data, plans, credentials, domains, or billing are changed.

Stop new writes and scheduled actions in Google Drive.
Restore the prior Box routing, forms, integrations, sending, or sync ownership.
Export the Google Drive post-cutover delta.
Review and apply safe destination-era changes to Box.
Run the same blocking checks against the restored source.

Proof to capture: Box again owns production with current data and no duplicate destination action.

Rollback immediately when

Unexplained critical count or value variance
Missing or exposed critical data
Duplicate production action
Failed access, routing, delivery, or integration check
A critical feature has no safe destination replacement

08Verification report

Prove the migration worked.

Every blocking check must pass. Capture the evidence before cleanup begins.

ID	Check	Method	Expected result	Evidence
`V-01`Blocking	File and folder reconciliation	Compare source, accepted, skipped, failed, and destination counts and bytes.	Every scoped object is accounted for.	Object ledger.
`V-02`Blocking	Binary parity	Compare checksums and sizes for a stratified and critical-file set.	Every tested binary matches.	Checksum report.
`V-03`Blocking	Conversion fidelity	Open every source-native type and exercise required features.	Meaning and critical behavior are preserved or archived.	Conversion matrix.
`V-04`Blocking	Revision coverage	Compare approved version counts and timestamps.	Retention depth matches the signed policy.	Version report.
`V-05`Blocking	Ownership mapping	Query active, inactive, group, and orphaned owners.	Every object has an approved owner.	Ownership ledger.
`V-06`Blocking	Internal and external permissions	Test representative identities and shared links.	Least privilege matches the signed matrix.	Access evidence.
`V-07`Blocking	Shortcut and embedded-link behavior	Exercise critical links from documents and integrations.	Every critical reference resolves or has a replacement.	Link report.
`V-08`Blocking	Single file authority	Inspect sync clients, integrations, and source changes.	Google Drive alone accepts approved edits.	Cutover checklist.

09Post-migration cleanup

Remove the scaffolding safely.

Safe after: One complete operating cycle, at least seven stable days, and owner sign-off on every blocking check.

Create final Box exports and archive verification evidence.
Revoke temporary credentials, API keys, webhooks, and elevated roles.
Remove obsolete embeds, forms, jobs, integrations, and DNS records.
Keep the source intact through the approved retention window.
Cancel paid plans only after billing, legal, and recovery review.
Schedule the next Google Drive backup, access, and migration-playbook review.

Sources and maintenance

Built to be reviewed.

Tested 2026-07-19. Next scheduled review: 2026-10-19.

Google Workspace Migrate: Box support matrixAccessed 2026-07-19
Google Workspace Migrate: Box monitoring pointsAccessed 2026-07-19
Google Workspace Migrate: Box settingsAccessed 2026-07-19

Know the shape of the move.

This timeline assumes

What survives the move.

Where each thing goes.

Make the move recoverable.

Create the source-of-truth backup

Identity, container, and permission map

Object and native-document migration

The things most likely to hurt.

A completed job hides skipped or converted objects

Permissions broaden during container conversion

Both tenants accept edits

Do the work in this order.

Inventory and decisions

Export?

Backup and reconcile

Transform?

Map and pilot

Scale?

Final delta and switch

Open production?

Observe and close

Close rollback?

Cut over with a way back.

Cutover

Rollback

Prove the migration worked.

Remove the scaffolding safely.

Built to be reviewed.