Dropbox to Google Drive: What Switching Actually Costs

For a 30-person team, moving files into Google Workspace can pay back in month 13 or fail to pay back within three years. In the example below, the migration work is identical. The difference is whether the team already pays for enough Google storage, needs an upgrade, or must buy a new subscription.

Start with the bill that changes

A team using Dropbox for files and Google Workspace for email already has two subscriptions. Moving the files might eliminate one, but the existing Workspace bill belongs on both sides of the comparison. Counting that whole bill as a new migration cost understates savings. Calling Drive free when the move requires an upgrade overstates them.

Build the comparison from your current invoice and a destination quote covering the same users and required features. List any Dropbox seats that must remain for client work, specialist workflows or an archive. Our software license audit guide helps distinguish seats you can cancel from seats you merely stop using.

This article covers a Dropbox business account moving into Google Workspace, using Google's native import route. It is based on official documentation and an original planning example. We have not performed a customer migration or measured transfer speeds. The example's Dropbox cost, labor and timeline are assumptions; the Google price inputs are identified separately below.

Storage capacity can turn consolidation into an upgrade

Google's US Workspace pricing page, checked November 15, 2026, lists the regular annual-commitment rates at $7 per user per month for Business Starter and $14 for Business Standard, before tax. Starter includes 30 GB of pooled storage per user; Standard includes 2 TB. We use regular rates and exclude introductory offers.

For 30 licenses, those allowances contribute 900 GB and 60 TB respectively to the organization's pool. They are total allowances, not an estimate of remaining space. Check actual storage consumption, what will be copied and the growth allowance your team requires. An upgrade is only one possible response; compare any suitable storage add-on or alternative quote before choosing it.

If an upgrade is required, count the billable population that must upgrade, which may be larger than the Dropbox user group. The example below assumes the same 30 people for both products and a whole-team Starter-to-Standard upgrade. It makes no assumption that a customer can mix editions on demand.

What Google's importer covers

The official setup guide requires a Workspace super administrator, a Dropbox team administrator, destination user licenses and prepared shared drives. It allows up to 150 Dropbox personal or team folders per import. Folder destinations and user identities are supplied through separate CSV mappings; Google Groups and their memberships must be prepared when mapping Dropbox groups.

Before copying data, give each team folder a destination and an owner who can approve the result. Separate that folder map from the list of people and groups permitted to use it. A designer, a finance employee and a client should each have a clear access outcome. Time spent fixing mappings is part of migration labor, even when the transfer itself runs unattended.

Google's supported-data list says files retain their existing format. Personal folders map to My Drive; team folders map to shared drives or folders within them. This is a copy operation, so do not treat completion as evidence that Dropbox has been retired.

Budget for the material that needs another route

The same supported-data list excludes Dropbox Paper, previous file versions, items with blocked-download policies, items owned by external users or applications, and items last modified by external users. Permissions for internal users or groups missing from the identity CSV are also excluded. These are limitations of this import route, not a claim that no other migration method can handle the material.

Build an exception register before approving the savings estimate. For every required item that the native route cannot carry, record who owns the decision, what preservation or replacement method will be tested, the expected effort and the acceptance check. Keep an unsupported item out of the planned deletion scope until its owner accepts the alternative.

For an active customer project, test the files the customer actually edited, not just an internally authored sample. For an archive, test whether you need prior versions and whether the proposed preservation method retains them. Neither a matching folder count nor a successful opening of the newest file answers that question.

Sharing also needs a functional test. Google documents that multiple public or team share links can consolidate under the most restrictive sharing setting, while invite-only sharing is represented as user permissions. Don't infer that all sharing behavior is unchanged. Test the resulting access as the intended recipient and budget time to distribute replacement addresses wherever your workflow needs them.

Three budgets for the same 30-person move

Planning assumptions: the current Dropbox invoice is assumed to average $18 per user per month, or $540 for 30 people. This is a hypothetical invoice input, not a claim about Dropbox's current list price. The old contract remains payable for three months after the migration starts. Seats and prices stay flat, and every Dropbox seat can be removed afterward.

Allow 80 staff-hours at $60 an hour, plus $200 for incidental setup or assistance: $5,000 upfront. One possible allocation is 18 hours for inventory, 18 for mapping and transfer administration, 20 for exception repair and validation, and 24 for training and support. These are assumed planning allowances, not measured averages or a fee charged by Google's importer.

Costs below are the expenses relevant to this decision. Existing subscriptions that remain identical under both choices are excluded from both totals. All amounts are USD, before tax, with no discounts, refunds, price increases, seat growth or financing. Costs are allocated monthly; this is not an annual-prepayment cash-flow forecast.

Illustrative 36-month cost comparison
Destination situationAdded Google cost / monthSwitch cost, 36 monthsSavings vs. stayingBreak-even month
A. Workspace already sufficient$0$6,620$12,82013
B. Upgrade all 30 from Starter to Standard$210$14,180$5,26021
C. Buy 30 new Standard licenses$420$21,740−$2,300None within 36

Staying costs $540 × 36 = $19,440 in all three comparisons. Switching costs $5,000 upfront, plus three months of Dropbox at $540, plus 36 months of the incremental Google bill. The upfront work and remaining old contract together total $6,620.

Scenario A: the team already has the capacity and features it needs. With no added Google bill, $6,620 ÷ $540 rounds up to month 13. This depends on having sufficient capacity and no additional recurring service or archive cost.

Scenario B: the upgrade adds ($14 − $7) × 30 = $210 a month. Savings after Dropbox ends are $330 a month. The $6,620 hurdle divided by $330 rounds up to month 21. The existing Starter bill is common to staying and switching and is excluded from both totals.

Scenario C: purchasing Standard adds $14 × 30 = $420 a month, leaving only $120 in monthly savings. At month 36 the move is still $2,300 behind. Keeping prices and users fixed beyond the table would put the crossover in month 56; that extrapolation is outside the calculator's 36-month horizon. No savings from changing email or other services are assumed.

To reproduce the scenarios in our switching cost calculator, enter 30 seats, $18 current cost per seat, $200 onboarding, 80 migration hours, $60 hourly cost, three lock-in months and zero growth or price increase. Set the candidate cost per seat to $0, $7 or $14 for A, B or C. The candidate input here is the incremental cost; do not enter the whole team's monthly total into a per-seat field.

Make the overlap end date achievable

The three-month overlap is an assumption about when the old bill can end, not a promise about transfer duration. Check renewal and cancellation terms before assigning a cutover date. Our contract checklist and migration timeline guide explain the distinction between finishing the copy and stopping payment.

Google's delta-import documentation says later runs can copy new or changed material, but deleting an item in Dropbox does not delete its destination copy. It also warns that exact permission imports are not guaranteed and can be delayed, and advises against moving files or folders during or between imports.

Our cutover recommendation is to agree on one editing location, pause folder reorganization during the transfer window, run the final delta and reconcile exceptions before releasing the destination to everyone. If users keep changing both sides, assign someone to resolve conflicting versions; do not count on the delta to make that decision.

Use the import report to investigate warnings and failures. It includes source and target URLs, and can identify sharing failures caused by the destination's external-sharing restrictions. Evaluate those failures against your intended policy rather than opening access solely to clear a warning. Google's setup guide says reports and configuration are no longer accessible after exiting the import, so export the evidence before closing it.

Approve an exit only after the workflow passes

Choose a pilot with a client-edited file, a restricted folder, a large working file and any exception type the team relies on. Have the actual recipients check access, editing, search and the links they use to find the material. Test the desktop and offline workflow if staff need it. These are acceptance recommendations, not claims of performance parity between the products.

Then replace the assumed hours with the pilot's findings. Add paid assistance, retained Dropbox seats, archival costs or a wider Workspace upgrade if required. Recalculate the savings before giving notice. The move is ready when the required work is usable in the destination and the old expense can actually end; a completed transfer job is only one part of that decision.

Sources and method:

Last re-checked November 15, 2026. Product claims were checked against official documentation; no live migration was performed. Google prices exclude promotions and can vary by region or contract. Dropbox cost and project effort are explicitly hypothetical. The three examples were checked with independent arithmetic against the existing calculator. Recommendations about pilots and cutover are editorial judgments.