Migrating from Box to a Google Shared Drive is more than downloading files and re-uploading them. It involves reviewing your existing folder structure, deciding how that structure should map into Google Workspace, understanding how file ownership and permissions change between the two platforms, and choosing a Google Drive Migration method that fits the size and complexity of your data.
This guide walks through how Box-to-Shared-Drive migration works, what to prepare beforehand, why some files and folders can’t simply be dragged into a Shared Drive, and how to decide between a manual transfer and a tool-assisted or professionally managed migration.
Table of Contents
Can You Migrate Box Data to a Google Shared Drive?
Yes. Box data can be migrated into a Google Workspace Shared Drive, but the right approach depends on several factors:
- How much data you’re moving
- How many users and folders are involved
- How your Box folder and permission structure is organized
- What file types you’re working with
- Whether you’re moving into a new or existing Shared Drive
- Whether the migration needs to happen with minimal disruption to active users
A single user moving a personal folder of files is a very different task from an organization moving shared team folders, external collaborator access, and years of historical data. The first is often manageable as a simple transfer. The second is closer to a structured cloud migration project, with planning, mapping, and validation steps.For organizations moving business data into Google Workspace, this becomes a structured Google Workspace migration involving planning, mapping, and validation.
Box to Shared Drive Migration at a Glance
A typical migration follows this general workflow:
Assess Box → Prepare the Shared Drive → Map the Data → Migrate → Validate → Cut Over
- Assess Box: Review what data exists, who owns it, and how it’s organized.
- Prepare the Shared Drive: Create the Shared Drive, add members, and decide on roles.
- Map the data: Decide how Box folders and users correspond to Shared Drive folders and members.
- Migrate: Move the data using a manual, tool-assisted, or managed process.
- Validate: Confirm the data arrived intact and is accessible to the right people.
- Cut over: Transition day-to-day use to the new Shared Drive and retire the Box source once you’re confident in the results.
What Is a Google Shared Drive?
A Google Shared Drive is a shared storage space within Google Workspace that belongs to a team or organization rather than to any single person. Unlike a folder in someone’s My Drive, a Shared Drive isn’t tied to one user’s account.
Key characteristics:
- Organizational ownership: Files in a Shared Drive are owned by the organization, not by the individual who uploaded them.
- Membership-based access: Shared Drive members receive access through their assigned Shared Drive roles. Individual files or folders may also have additional sharing permissions depending on your organization’s configuration.
- Defined access roles: Google Workspace provides different levels of access for Shared Drive members (such as the ability to manage the drive, edit content, comment, or only view). The exact role names and permissions are managed through Google Workspace and can be reviewed in Google’s Shared Drives documentation.
- Continuity: Because the Shared Drive itself owns the content, files remain in place even if a member leaves the organization or is removed—unlike files owned by an individual’s My Drive account.
This is different from a general tutorial on Google Drive as a whole; the distinction that matters for migration purposes is ownership and membership, which directly affects how your Box data should be mapped in.
Shared Drive vs. Shared Folder: What’s the Difference?
Many organizations coming from Box are used to shared folders rather than a dedicated shared-storage structure. Here’s how the two compare in Google Workspace:
| Factor | Shared Folder (in My Drive) | Google Shared Drive |
| Ownership | Owned by the individual user who created it | Owned by the organization |
| Access | Granted per file/folder by the owner | Granted through Shared Drive membership and roles |
| Administration | Managed by the individual owner | Can be managed by designated Shared Drive managers and Workspace admins |
| Team collaboration | Works for small, informal sharing | Designed for structured team or department-wide collaboration |
| Continuity | Content risk if the owning user’s account is disabled or removed | Content stays with the organization regardless of individual membership changes |
| Typical use case | Personal files shared with a few collaborators | Department, project, or company-wide file storage |
For business data organized around departments, projects, or teams, Shared Drives can provide a more suitable organizational destination than individual My Drive accounts, which is why most Box migrations target Shared Drives rather than individual My Drive folders.
What to Prepare Before Migrating Box to a Shared Drive
Box assessment
- Number of active users and their current Box roles
- Folder structure and how deep/complex it is
- Total file volume and any unusually large files
- Folders shared externally or with guest collaborators
- Existing permission levels (owner, editor, viewer, uploader)
- Inactive, duplicate, or obsolete content that doesn’t need to migrate
Google Workspace preparation
- Create the destination Shared Drive(s)
- Decide on Shared Drive membership and roles for each team
- Plan folder structure inside the Shared Drive
- Confirm any Workspace admin policies that affect Shared Drive creation, external sharing, or storage
- Confirm the destination has sufficient capacity for the incoming data
Migration planning
- Map each Box user to their corresponding Google Workspace account
- Map Box folders to their destination Shared Drive folders
- Decide how Box permission levels will translate to Shared Drive roles
- Set a migration schedule (especially important if users need continued access to Box during the transition)
- Define how you’ll validate the migration once it’s complete
- Plan the cutover date and communicate it to affected users
Skipping this preparation is one of the most common reasons business migrations run into permission mismatches, missing folders, or confused users after the fact.
What Should You Check in Box Before Migration?
Before mapping anything to Google Workspace, take inventory of what’s in Box. This step is what separates a clean migration from one that surfaces problems weeks later.
- Users and groups: Who has active Box accounts, and what Box groups exist?
- Folder owners: Who owns each top-level and department folder?
- Collaborators: Who has been added to specific folders, and at what permission level?
- Shared folders: Which folders are shared broadly versus restricted to a small team?
- External collaborators: Which folders include people outside your organization, and what access do they have?
- Permission levels: What mix of owner, co-owner, editor, viewer, uploader, and previewer roles exists across your folders?
- Inactive users: Are there Box accounts tied to former employees or contractors that still own or hold access to content?
- Archived data: Is there content that’s rarely accessed and could be excluded or moved separately?
- Duplicate or obsolete content: Are there old file versions, abandoned drafts, or redundant copies that don’t need to migrate?
- Nested folder structures: How deep does your folder hierarchy go, and are there naming or structure inconsistencies to clean up first?
- Files that shouldn’t migrate: Are there files that should be archived, deleted, or handled separately instead of moved into the Shared Drive?
Each of these directly affects your folder mapping and permission plan. An inactive user who still owns a shared folder, for example, needs to be reassigned before migration—not discovered after the Shared Drive is already in use.
How to Migrate Box to Google Shared Drive
Step 1: Analyse the Box environment
Use the checklist above to build a clear picture of what exists: active users, folder hierarchy, total data volume, and any folders with complex or externally shared permissions. This assessment is what your folder mapping and migration schedule will be based on.
Step 2: Create and configure the Shared Drive
Set up the destination Shared Drive (or drives, if you’re splitting by department). Add members and assign roles that reflect how each person should be able to interact with the content—managing, editing, commenting, or viewing only.
Step 3: Map Box folders to Shared Drive folders
Plan out how your existing structure will translate. For example:
Box → Sales → Documents
becomes
Google Shared Drive → Sales → Documents
For a small Box account, this mapping might take a few minutes. For a business with dozens of teams and years of nested folders, this step deserves a spreadsheet and a review before migration starts, since it’s much easier to fix mapping mistakes on paper than after files have already moved.
Step 4: Choose a migration method
Manual migration
Downloading files from Box and uploading them into the Shared Drive can work for small amounts of data with a simple folder structure and few users. A manual copy generally does not reproduce the original Box permission structure automatically—users, groups, and access rules may need to be recreated in Google Workspace by hand. Its limitations show up quickly at scale: no automated permission mapping, no batch processing, no error logging, and a real risk of missing files or breaking folder structure on larger datasets.
Cloud migration software
Migration tools built for cloud-to-cloud transfers can automate folder mapping, run migrations in batches, and provide logs of what did and didn’t transfer successfully. Capabilities vary by tool, so confirm what a specific product supports for Box-to-Google Shared Drive migrations—including how it handles permissions and large file volumes—before relying on it for production data.
Managed migration service
For organizations with large datasets, many users, complex permission structures, or limited internal IT bandwidth, a managed migration service can plan, execute, and validate the migration on your behalf. This is generally the more practical option when downtime needs to be minimized and the migration is business critical.
Step 5: Run the migration
Larger migrations are usually run in batches rather than all at once, with monitoring to catch failures early and retry logic for files that don’t transfer on the first attempt. Whether you’re doing this manually or with a tool, keep a record of what has and hasn’t been migrated.
Step 6: Validate the migrated data
Before considering the migration complete, check:
- File and folder count match between source and destination
- Folder structure reflects your intended mapping
- Permissions and Shared Drive roles are correct
- Important business files are present and accessible
- Failed or skipped items are identified and re-migrated
- File integrity (spot-check that files open correctly and aren’t corrupted)
Step 7: Complete the final cutover
For many businesses, migration happens in stages rather than as a single cutover moment:
- Initial migration: The bulk of existing Box data moves to the Shared Drive while users continue working in Box.
- Final (delta) migration: Any files created or changed in Box since the initial migration are transferred over, bringing the Shared Drive fully up to date.
- Cutover: Users stop working in Box and begin working directly in the Shared Drive.
This staged approach minimizes disruption, since users aren’t forced to stop working during the bulk of the migration. Once validation is complete and users have confirmed access, communicate the cutover date clearly, and only decommission the Box account once you’re confident nothing critical was left behind.
What Happens to Your Box Data After Migration?
Migrating data to a Shared Drive doesn’t mean your Box account needs to be shut down immediately. Most organizations move through a few stages:
- Keep Box temporarily: Useful during validation, so you still have a working source to compare against if something looks off in the destination.
- Make Box read-only: Useful during cutover, since it prevents new changes in Box while final migration and validation are wrapping up.
- Retire Box: Reasonable only after migration validation is complete, users have confirmed access and accepted the new environment, important files have been verified, permissions have been reviewed, any final/delta changes have been migrated, and your organization’s data retention requirements have been considered.
Don’t delete Box data immediately after files appear to have transferred. Treat retirement as the last step in the process, not an assumption you make partway through.
Why Can’t I Move Files or Folders to a Shared Drive?
This is one of the most common issues people run into, whether they’re migrating from Box or reorganizing existing Google Drive content. Common causes include:
- Insufficient permissions: You need the appropriate Shared Drive role (not just view or comment access) to move files or folders into it.
- Not a Shared Drive member: You generally need to be added as a member of the destination Shared Drive before you can move content into it.
- Shared Drive restrictions: Some Shared Drives are configured to limit who can add or move content, depending on Workspace admin settings.
- Google Workspace admin policies: Organization-wide policies can restrict certain move or sharing actions.
- Ownership or access mismatches: Files owned by an account outside your organization, or files with restrictive sharing settings, can block a move.
- External users: Files shared by or with external (non-organization) accounts sometimes can’t be moved the same way as internally owned files.
- Unsupported movement scenarios: Certain move actions (for example, moving between two different Shared Drives, or moving into a Shared Drive from outside your organization) can have additional restrictions.
Not every cause applies in every situation—if you hit this error, it’s worth checking your role, Shared Drive membership, and file ownership first, since those account for most cases.
These restrictions are especially relevant when preparing or reorganizing the Google destination—for example, moving files within Google Drive once they’ve already arrived. They’re separate from the mechanics of transferring data directly from Box using a migration method, which follows the process described above rather than Google Drive’s internal move rules.
What Happens to File Ownership After Moving to a Shared Drive?
In an individual’s My Drive, each file has a single personal owner. When content moves into a Shared Drive, that changes: the Shared Drive itself—representing the organization—owns the content, not any individual member.
Access is then determined by Shared Drive membership and role rather than by personal file ownership. This is a meaningful shift for organizations coming from Box, where ownership and sharing are typically tied to individual accounts. It’s worth reviewing this ownership model with your team before migrating, so nobody is surprised that files they “own” in Box behave differently once they’re inside a Shared Drive.
What Happens to Permissions During Box to Shared Drive Migration?
Box and Google Workspace use different permission models, and permissions do not automatically transfer exactly as they existed in Box. Points to plan for:
- Box permission levels (owner, co-owner, editor, viewer uploader, previewer, and similar) don’t map one-to-one onto Shared Drive roles.
- User accounts need to be mapped between the two platforms so access follows the right people.
- Group-based access in Box may need to be recreated using Google Groups or Shared Drive membership groups.
- Differences between the platforms mean some permission structures will need to be reviewed and manually rebuilt rather than assumed to carry over automatically.
A simplified example of what this mapping looks like in practice:
| Box | Google Workspace |
| Sales Team → Editor | Sales Team → Shared Drive member (appropriate role) |
| John → Viewer | John → appropriate access level, reviewed individually |
| External Partner → Previewer | External Partner → access reviewed and recreated, not assumed |
The point isn’t that these permissions map automatically—they don’t. It’s that every access level in Box needs a deliberate decision about its Google Workspace equivalent.
Treat permission mapping as a planning task, not an automatic outcome of the migration itself.
Manual vs. Tool-Assisted Box Migration
| Factor | Manual Transfer | Migration Software/Service |
| Small amount of data | Practical | Often unnecessary |
| Large datasets | Time-consuming and error-prone | Built to handle scale |
| Folder mapping | Done by hand | Can be automated or templated |
| Permission handling | Manually recreated | Often supports structured mapping |
| Batch migration | Not built-in | Typically supported |
| Monitoring | Manual tracking | Usually includes progress tracking |
| Error reporting | Limited visibility | Typically includes logs of failed items |
| Validation | Manual spot-checks | Often includes reporting to support validation |
| IT effort | Higher for anything beyond small transfers | Reduces hands-on effort, especially for managed services |
Common Problems During Box to Shared Drive Migration
- Files not transferring: Often caused by permission issues, unsupported file states, or interrupted transfers—check logs (if using a tool) or re-attempt affected files.
- Folders not appearing as expected: Usually a mapping issue; confirm your folder plan against what actually landed in the Shared Drive.
- Permission mismatches: Expected if permissions weren’t explicitly mapped beforehand; revisit your permission plan and correct roles as needed.
- Unsupported file types: Some file types may need conversion or special handling—identify these during the initial Box assessment rather than during migration.
- Duplicate files: Can occur from repeated migration attempts or overlapping folder structures; deduplicate before or after migration depending on your workflow.
- Incomplete transfers: Large migrations are more prone to partial failures; batch and monitor rather than attempting everything at once.
- Shared Drive access problems: Usually a membership or role issue—confirm the affected user is a member with appropriate permissions.
- Storage or capacity issues: Confirm your Google Workspace plan has sufficient capacity before migrating large volumes of data.
- Migration interruptions: Network issues or large batch sizes can interrupt transfers; smaller, monitored batches reduce this risk.
How to Verify a Box to Shared Drive Migration
A migration isn’t finished just because files appear in the destination. Before sign-off, confirm:
- Source and destination file counts match
- Folder structure matches your intended mapping
- Important business files are present and open correctly
- Affected users can access the Shared Drive with correct permissions
- Permissions and roles have been reviewed, not just copied over
- Failed or skipped items have been identified and resolved
- File sizes look correct where that’s a meaningful check
- Collaboration features (commenting, sharing, editing) work as expected
- Stakeholders have signed off before the Box source is retired
Should You Manually Migrate Box to Google Shared Drives?
There’s no universal answer—it depends on your situation.
Manual migration may be reasonable when:
- You’re moving a small amount of data
- Only a few users are involved
- The folder structure is simple
- Permissions are minimal or easy to recreate by hand
Tool-assisted or managed migration is often more practical when:
- You’re moving large datasets
- Many users and teams are affected
- Permissions are complex or involve external collaborators
- The files are business-critical and downtime needs to be minimized
- You need structured validation and reporting rather than manual spot-checks
If you’re unsure which category your migration falls into, a quick internal assessment of data volume, user count, and permission complexity (Step 1 above) will usually make the answer clear.
Frequently Asked Questions
Can I migrate Box data to a Google Shared Drive? Yes. Box data can be moved into a Google Workspace Shared Drive through manual transfer, migration software, or a managed migration service, depending on the size and complexity of your data.
How do I move Box files to a Shared Drive? Download files from Box and upload them into the Shared Drive for small amounts of data, or use migration software or a managed service for larger, more complex migrations that need folder mapping, permission handling, and validation.
Why can’t I move folders to a Shared Drive? Common causes include insufficient permissions, not being a member of the destination Shared Drive, Workspace admin restrictions, or ownership/access issues tied to the files themselves.
Who owns files in a Shared Drive? Files in a Shared Drive are owned by the organization rather than by an individual user. Access is based on Shared Drive membership and role rather than personal ownership.
Can I move files between Shared Drives? In general, moving files between two different Shared Drives can be more restricted than moving within a single Shared Drive, and may depend on your role and Workspace admin settings. If you hit restrictions, check your permissions in both the source and destination Shared Drive.
Why won’t Google Drive let me move files? This is usually a permissions or membership issue—either you lack the necessary role in the destination location, or the file’s ownership and sharing settings are blocking the move.
Does a Shared Drive use Google Drive storage? Shared Drives use your organization’s Google Workspace storage rather than an individual’s personal storage allotment. For current storage details specific to your plan, check your Google Workspace admin console or official Google documentation, since storage allocations can vary by plan.
Is manual Box-to-Google migration suitable for a business? It can work for small, simple migrations, but most businesses with meaningful data volume, multiple users, or complex permissions are better served by tool-assisted or managed migration to reduce risk and ensure a complete, validated transfer.
What replaced Box Sync? Box Sync was retired and succeeded by Box Drive as Box’s desktop application. Box Drive handles desktop file synchronization, which is a different task from a cloud-to-cloud migration to Google Workspace—syncing keeps files updated on a local device, while migration moves data permanently to a new platform. Box’s current product names and capabilities can change, so verify this against current Box documentation before publishing or acting on it.
Is Box safer than Google Drive? Security depends on how each platform is configured, administered, and used. Both platforms provide security and administrative controls, so organizations should compare the specific requirements, policies, and controls relevant to their environment rather than treating one platform as universally safer.
Need Help Migrating Box to Google Shared Drives?
SkyMigrate can help with Box-to-Google Workspace migration, including migration planning, folder and user mapping, migration execution, validation, and post-migration support.
