Direct Migration
PetaByte Migration Bridge
Move large Google Drive and Gmail libraries directly into PetaByte without routing each file or message through Base44 integration-credit operations.
Zero-credit bulk transfer lane
Google access is read-only. Migration copies source data first and does not delete anything from Google.
Google Drive → Vault
Google file streams move directly into private PetaByte FTPS storage, then only lightweight Vault metadata is registered.
Gmail → PetaByte Mail
Raw RFC822 messages are copied into PetaByte Mail over parallel IMAP connections with message contents preserved.
Resumable state
Completed source IDs and job progress are checkpointed in the dedicated bridge database so restarts skip completed items.
Bulk Migration
Use this for full-account Google migrations. The old per-file Base44 integration route is no longer used here.
Your current PetaByte session is handed off securely. If Google authorization is needed, you will see Google's own consent screen once; the migration then continues automatically.
Transfer safeguards
Built for large libraries and interrupted connections.
Read-only Google scopes; source deletion is not part of migration.
Parallel streaming workers for Drive and Gmail, with no temporary full-file staging for Drive.
Resume support prevents starting over after a restart.
Destination capacity preflight runs before the Drive copy proceeds.
Do not remove Google data until the bridge reports completion and the migrated content has been verified in PetaByte Vault and PetaByte Mail.