Google Workspace Backup Tool Prerequisites, Supportability & Limitations

author Written By Deep Sikha
author Approved By Sonika Rawat
Updated on 5th Nov 2026
Reading Time 8 minutes

Carefully evaluate system requirements, account permissions, and supported data before using the Google Workspace Backup Tool. This article aims to help IT Administrators understand backup planning requirements, system compatibility, supported requirements, and limitations to prepare for the backup process. Each type of Google Workspace data that can be backed up, the access that is required, and some factors that might block backup are also mentioned in the article. Knowing this helps administrators detect possible problems in advance and decide whether their environment is prepared for the backup process.

Google Workspace Backup Tool Prerequisites

A large portion of mistakes made during backups, or their delays, can be linked to inaccurately fulfilled tasks before the backup procedure. Please check the following items before starting your work:

  • Operating System: Please use either the Windows or Mac operating system that fulfils the requirements of the software. That you’ll use for your backup.
  • Account status: Your Google Workspace account must be active and approved to use with compliant Google Workspace services.
  • Sign-in options: The sign-in method can be OAuth 2.0, application password, or domain admin credentials based on the archive requirements. You can also visit this blog for How to Log in to a Google Workspace Account: Explained in Depth.
  • API availability: Each application in the network must be allowed to access the respective Google services and enabled Google API permissions.
  • Admin credentials: For a domain-wide backup, prepare a Google Cloud project, download the JSON or P12 key file, and configure domain-wide delegation.
  • CSV mapping file: Use the official CSV file provided by the tool for simultaneous processing of various accounts at the same time.
  • Access to the destination: When transferring data directly to another Google account or external platform, verify that the requisite permissions and licenses have been activated on the receiving end.
  • Storage on a local level: The target directory must be open and writable. This is one of the Google Workspace Backup Tool System Requirements.
  • Internet: Have a stable connection, enabling the tool to get to Google servers without interruptions.
  • License: Before downloading heavy data or processing accounts in bulk, consider reviewing the license or demo limits given before proceeding.

Google Workspace Backup Tool Supportability

The core supportability criteria, user scopes, and technical specifications are summarized below:

Criteria Supported Details
Target Users IT Administrators, Managed Service Providers (MSPs), Individual Users
Authentication Modes OAuth 2.0 (Modern), IMAP + App Password, Workspace Admin Domain-Wide Delegation (DWD via JSON/P12 keys)
Backup Scale Single-user mailboxes or large domain-wide bulk processing using a CSV mapping template
Source Data Scopes Gmail (messages, labels, metadata), Google Drive (My Drive, Shared Drives, Shared with Me), Google Chats/Spaces (DMs, threads, attachments), Contacts, Calendars, Tasks, and Notes
Local Export Formats PST, PDF (with Tabular, Bubble, or Transcript chat layouts), MBOX, CSV, EML, EMLX, MSG, HTML, VCF (Contacts), ICS (Calendars)
Auto-Conversion Google Docs, Sheets, and Slides automatically convert to Microsoft Office formats (DOCX, XLSX, PPTX)
Cloud Destinations Migrate Your Organization’s Data to Google Workspace, Microsoft 365 (Single-user or full Tenant mode), On-premises Exchange Server (Primary, Shared, Public Folders, Online Archive)
API Integration Direct, secure connection via official Google APIs and Microsoft Graph APIs (No Google Takeout or custom scripts required)
Trial Version Limits Evaluates all features but caps downloads at 500 emails/folder, 100 contacts/calendars, 50 chat messages/spaces, and 20 MB/file from Drive

Google Workspace Backup Tool Limitations

You will at least get an understanding of your limitations, and knowing them allows you to plan the project properly to avoid trouble when it comes to the backup or migration process.

  1. Demo capability: The demo process consists of a maximum of 500 email messages per folder, 100 contacts and appointments, 50 messages per DM or Space, and 20 MB of data uploaded from Google Drive. You can test the service on real data before making a final decision.
  2. Permission-bound access: The tool can only reach what your credentials and enabled APIs allow. If Gmail authorizes but Drive does not, the Drive API or its scope usually isn’t enabled.
  3. Template dependency: Multi-account jobs work only with the official CSV template. A custom layout can fail validation.
  4. Connection sensitivity: The tool pulls data over the internet. An unstable connection can interrupt long jobs.
  5. Destination readiness. Direct migration depends on valid licenses and permissions at the target account.

Authentication and Permission Requirements with Working Steps

SysInfo presents three ways to authenticate with Google Workspace using the Google Workspace Backup Tool. Modern Authentication (OAuth 2.0), IMAP with App Password, and Workspace Admin with Domain-Wide Delegation (DWD) are the options available. Depending on the method chosen and the data in Google Workspace to be processed, different permissions will be needed. The software can also import multiple user accounts from a CSV file for bulk processing. To migrate a Google Workspace Domain to Microsoft 365 in 2026, visit this blog to learn about planned migration using the mentioned tool.

  • A valid Google Workspace account with access to the data selected for backup.
  • OAuth 2.0 consent or supported Client ID and Secret ID credentials, depending on the authentication workflow.
  • IMAP access and an app password for supported IMAP connections.
  • A Google Cloud project, service account credentials (JSON/P12), and DWD configuration for domain-wide access.
  • The required Google APIs and OAuth scopes authorized by a Google Workspace super administrator, where applicable.
  • A correctly formatted CSV file when processing multiple accounts through bulk authentication.

Working Steps for Google Workspace Backup Tool

  1. Launch the Google Workspace Backup program and connect, authenticate, and save your backup using one of three modes: OAuth 2.0, IMAP + app password, or Google Workspace using Workspace Administrator (DWD).
  2. Back up your workspace data securely and consistently by properly configuring users, data types, general and advanced filters, export formats or email clients, destinations, and authentication.
  3. Back up your entire data and view the live dashboard and real-time progress report to track completed, skipped, failed data items, source, destination, and other important backup details.
  4. Verify reports and carefully review logs for review or compliance purposes. Access the saved data from the intact folder hierarchy in the desired destination as needed.

Note: The detailed guide with screenshots can help you better. And if you need it, check this latest Google Workspace Backup Tool Guide to help with migration.

Common Issues and Troubleshooting

  • Drive data missing or keeps filling: Enable the Drive API and confirm the scope. And for fixing the drive data filling issue, use Why Google Drive Keeps Filling Up: The Hidden Cost of Duplicate Files.
  • Authentication failure: Recheck the Client ID, the key file, and the admin email used for impersonation.
  • CSV rejected: Google Workspace Backup Tool limitations. If the CSV is rejected, then rebuild the file from the official sample template.
  • Backup stops midway: Verify the connection, free disk space, and folder write permissions.
  • Demo shows partial data: This is the demo capability, not a fault. Activate the license for a full export.

Key Considerations Before You Begin Google Workspace Backup

Firstly, follow the Google Workspace Backup Tool Prerequisites, and then follow the following practices that should be followed to set up your Google Workspace environment to ensure backup errors are kept to a minimum.

  • Access Permissions Validation: Make sure that the account being used and the type of authentication possess the appropriate permissions for access to the appropriate Google Workspace data.
  • API Configuration Validation: Check twice that all the necessary Google APIs and scopes are enabled before starting the backup procedure.
  • Perform a Test Backup: If possible, firstly take advantage of the trial version of the software. And make sure it’s configured properly before trying out larger workloads.
  • Supported Data: Check that the software supports the required type of data, the type of emails, the attachments in emails, and the type of files where the data will be exported.
  • Select the Right Destination: Make sure that you have the desired folder or account with enough space to download backup data.
  • Check Backup Results: Check reports and exported documents to find possible anomalies, items that have not been added or unsuccessful processes of backing up.
  • Keep Backup Copies: Place the backup documents in the right place and keep other copies as required by your company’s regulations about maintaining data.
  • Write down Backup Settings: Formulate procedures for authentication, accounts, filters, and errors in the context of making the next backup successful.

Why Choose SysInfoTools for Your Migration Partner

SysInfo’s migration services may be an option for companies that do not have the time or skills to handle their Google Workspace migration. For IT vendors and MSPs, White-Label Email Migration for IT Vendors and MSPs services provide another option. With managed migration services, the migration strategy, evaluation of source and target environments, and scope of work can be defined.

Conclusion

Now, we are at the end of the blog, so before backing up data, check account access, the API permissions, system requirements, and destination. Reviewing the Google Workspace Backup Tool’s prerequisites, supported data types, and limitations, that can helps administrators identify compatibility issues before starting the migration. Where available, use the demo version to test the setup and understand tool features. These checks help you prepare the environment, address potential problems early, and plan the backup process based on your organization’s needs.

Frequently Asked Questions

Q1. What are the prerequisites for using a Google Workspace Backup Tool?

Ans. You need a supported Windows or Mac system, at least 4 GB of RAM (8 GB recommended), and 1 GB of free disk space. You also need an active Google Workspace account with permission to access the data, the right APIs enabled, a writable destination folder, and a stable internet connection.

Q2. How do I check Google Workspace Backup Tool prerequisites before installation?

Ans. Compare your computer’s operating system, RAM, and free space against the requirements. Then confirm the account is active, the sign-in method is chosen, the APIs are enabled, and the destination folder is writable.

Q3. Does a Google Workspace Backup Tool require administrator access?

Ans. Not for a single-account backup with OAuth 2.0. For a domain-wide backup, you need admin credentials and domain-wide delegation.

Q4. Do I need a service account and P12 file for Google Workspace backup?

Ans. Only for organization-wide jobs. You prepare a Google Cloud project, download a JSON or P12 key file, and set up delegation. Single-user backups don’t need it.

Q5. Can a Google Workspace Backup Tool preserve file permissions and metadata?

Ans. Email backups keep their structure and message details. How far file permissions carry over for Drive items depends on the output format. Test a sample first to confirm what your workflow needs.

Q6. Are there limitations when backing up Google Shared Drives?

Ans. Access depends on your credentials, the enabled Drive API, and the delegated scopes. If those are missing, shared drive data will not appear. The demo also caps Drive data at 20 MB.

Q7. How can I fix Google Workspace Backup Tool API permission errors?

Ans. Check that the required APIs are enabled in your Google Cloud project. Make sure the Client ID is authorized with the right scopes in the Admin console. Verify the key file and the admin email, then retry.

Q8. What should IT administrators evaluate before selecting a Google Workspace Backup Tool?

Ans. Look at supported data types, output formats, authentication options, bulk-account handling, destination support, demo limits, and licensing. Test it against real data before buying.