Dropbox to Sync Canada pilot result
18 November 2026 in Vancouver. The live file transfer, independent recovery, named access checks and single-file rollback passed for this synthetic research dataset. The free accounts cost CAD $0. All 30 original modification times differed on the restored local files. Sync’s folder ZIP remains unverified.
What made the trip
The operator seeded a dedicated Dropbox Basic account from a read-only local baseline. Dropbox reported 30 uploads complete. A fresh Dropbox folder download supplied the files for the Sync upload. The independent restore used a second Sync account, in a separate Chrome session. Both roles were operated for the test. Workload-owner acceptance remains open.
| Measure | Observed result |
|---|---|
| Source and destination | Dropbox Basic and Sync Free. No trial or payment method was needed. |
| File-data region | The signed-in Sync billing page loaded the Free plan, 5 GB quota and usage. It had no Data region section, which Sync documents as the Canadian default. This identifies the account’s file-data region. |
| Completeness and integrity | 30 of 30 files, 58,185 bytes, 23 nested folders. Every relative path, byte length and SHA-256 matched both the sealed originals and the Dropbox export. Zero missing, extra or changed files. |
| File usability | All 9 CSVs, 11 text files, 5 PDFs and 5 PNGs opened. The 24 observations summed to 252. The Mélèze note and rendered field card shared reference MJ-LAR-R2, and its chart’s first bar read 10. |
| Named access | The signed-in outsider received “Folder not found.” After accepting a named invitation with View and Edit, the same account opened and downloaded the files. The member had no invitation permission. |
| Revocation | The owner removed that member and selected removal of the service-side copy. The former member’s previously working folder and journal links returned “Path not found” and “The file is unavailable.” A previously downloaded local journal remained readable. No public link was created. |
| Edit and rollback | The owner uploaded the prescribed 110-byte journal. The member freshly downloaded it and matched the expected SHA-256. The owner restored the 79-byte original, and another member download matched its original SHA-256. A fresh Dropbox export after rollback still matched all 30 sealed originals. |
Source manifest · Sync’s account-region instructions
Transfer and recovery
Dropbox accepted a folder upload and returned a folder ZIP. Sync’s file chooser treated the folder as a single item and reported a source-read error. The operator created the original folders in Sync and uploaded their files into each. The successful target transfer took 5 min 8 sec, from creating the private pilot root to observing all 30 file rows. Dropbox folder download guide
Sync’s folder ZIP control produced no retrievable archive during this run. The invited member enumerated all 24 folders including the root and downloaded the 30 files individually. Recovery took 5 min 56 sec, from the first download attempt to the last file being recorded. Chrome numbered 18 downloads to avoid collisions between matching base names. Each was returned to its recorded folder and independently checked. These elapsed times include operator interaction. Sync export guide
Decision and retained material
The tested route works for ordinary files in a small, editable research share. For a workload that relies on filesystem modification dates, retain the original manifest and agree how those dates will be preserved before migration. An editable collaborator was appropriate for this test. A named read-only folder member requires a different Sync entitlement. Original timestamps · Sync Free sharing limits
The operator retained the sealed baseline and verified that the source journal remained unchanged.
A production decision would need the workload owner’s acceptance of the timestamp behaviour, an appropriate sharing plan, and evidence about versions, retention, backups, logs, support access and key recovery for the proposed accounts. This run covered no production or participant data. Working tasks and expected results · Pilot acceptance record template