Univik Google Workspace Email Backup

It means taking a copy of the mail inside your Google Workspace tenant and storing it somewhere your organization controls, so a deletion, a departure or a compromised account never costs you the record.

Univik Google Workspace Email Backup connects once as an administrator, lists every user on the domain and downloads the mailboxes you select to local or network storage as PST, PDF, MBOX, EML and other formats.

Business. This page covers Google Workspace: company mail on your own domain, managed from the admin console, where one connection reaches many users. A free personal address ending in @gmail.com belongs to whoever created it, signs in differently and gets backed up with the Univik Gmail Backup Tool. Other platforms such as Microsoft 365, Zoho or any IMAP host are covered by the Univik Email Backup Software.

Google keeps the service running and protects it against their own failures. What happens inside your tenant stays with you: a user emptying a folder, an offboarding done in a hurry, a compromised account, an admin deleting the wrong person. Google's own documentation is direct about this, stating that Vault is not an archive or backup tool. Native recovery windows are also short, roughly 25 days for a user's deleted Gmail data and about 20 days to restore a deleted user. Google states it removes customer-deleted data from its systems within a maximum of 180 days, so waiting is not a strategy. A backup exists for the request that arrives in month seven.

As an administrator, using a Google Cloud service account with domain-wide delegation authorized in your admin console for the mail scopes. Once that trust is in place, the tool lists your users and reaches their mailboxes without anyone handing over a password. In-app guidance walks through creating the service account and pasting the client ID and scopes into the console. You can withdraw the delegation at any time and access stops immediately.

Yes. Fetch the domain user list and tick the accounts. Very large tenants can load a CSV of addresses instead. Mailboxes run several at a time rather than one after another, each with its own progress line and result row. Suspended accounts are included, which matters because those are usually the ones holding a departed employee's mail.

Yes. Tenants that host several domains or domain aliases show all of their users in the same list, so accounts on a secondary domain are not quietly missed. Users can also be filtered by organizational unit when a policy only applies to one department.

This tool backs up user mail. Drive files, Shared Drives, Google Chat, Meet recordings and Groups archives are outside its scope. Saying so plainly beats discovering the gap mid-incident. Contacts and calendars sit outside the mailbox too and export separately from Google as vCard and ICS files. Plan Drive protection alongside this rather than assuming it comes bundled.

Vault is a retention and eDiscovery service. Google describes it as not being a backup tool. It prevents deletion inside the tenant and lets you search and export, but it makes no independent second copy and it cannot restore mail back into a mailbox. It also depends on licences and on the account still existing: delete a user and the data associated with that account is removed from Google, holds included. Many organizations run both, using Vault for legal holds and a local backup for recovery.

The usual workflow: back the mailbox up to PST on the day the person leaves, verify the count in the report, then release or delete the seat. The archive stays readable in Outlook for as long as your policy requires. You also stop paying to keep an inactive account or an archived user licence alive purely for records.

The first run is the long one and depends on total mailbox size and how fast Google will release the data, since heavy pulls get throttled on purpose. A 100-user tenant typically means an overnight window or a weekend for the first pass. Every run after that is incremental and usually finishes inside the scheduled window, which is why the first backup is the only one anyone plans around.

No. Access is read-only. Nothing is deleted, moved or marked, users see no change in their mailboxes and storage quotas are unaffected. Removing old mail to reclaim quota is always a separate decision you make in the admin console after the backup report confirms the copy is complete.

Yes. The tool uploads a backup into a Workspace mailbox with the folder structure intact. The destination can be the original user or a different one, which is how a leaver's mail reaches the colleague who took over the role. Moving an entire mailbox from one live account into another live account is a migration rather than a restore. The Univik Email Migration Software handles that job.

Wherever you point them: an internal drive, an attached disk or a NAS share on your network. The job runs from a Windows machine inside your environment and the mail goes straight from Google to that destination. No copy passes through Univik and no third-party cloud sits in the path. Most teams write to a NAS and let their existing backup routine take it from there.

Both approaches protect a tenant and they suit different organizations. Worth being straight about it before you spend anything.

• A cloud-to-cloud service runs on someone else's infrastructure, backs up on its own schedule and bills per user every month. Good when nobody wants to own hardware and the budget is operational.
• This desktop tool runs on a machine you own, writes to storage you own and costs one payment. Good when the mail must stay inside your network, when a subscription per seat is hard to justify or when policy says the archive cannot sit with a third party.

Choose the cloud service if you want a hosted dashboard and continuous automated coverage across Drive and Chat as well. Choose this if sovereignty, one-time cost and PST output matter more.

Read the report, then test a restore. Every run produces per-user counts of folders found, messages saved and anything skipped, so the first check is that the numbers agree with the tenant. The second check is the one most teams skip: once a quarter, restore a single folder into a test account and open it. A backup nobody has ever restored from is an assumption. Twenty minutes a quarter turns it into a fact.

Cloud backup services charge per user per month, so the bill grows with headcount and never stops. This is a one-time licence per machine covering as many mailboxes as your domain holds, plus whatever storage you already own or buy once. For a stable team the arithmetic usually favours the licence within the first year or two. For very large tenants that want continuous hosted coverage, a subscription service may still suit better. Pricing for multi-tenant use is available on request.

Runs on any Windows desktop from 7 up to 11 in either bit depth, though most admins schedule it on Windows Server (2012 through 2022 are supported). Allow 4 GB RAM with 8 GB recommended for concurrent mailbox runs, 250 MB for the program and enough destination space for the tenant. .NET Framework 4.8 or higher is required and current Windows 10 and 11 builds already include it. Outlook is not needed for PST output.

The full application with one limit: the first 25 emails per folder. That is enough to connect a real tenant, confirm the user list loads, run a mailbox end to end and read the per-user report before any money changes hands. A one-time licence removes the limit and nothing renews.