Migration terms to know

Common terms  |  Data migration service terms  |  GWMME terms  |  GWMHN terms

Open all   |   Close all

Common terms

API

Application Programming Interfaces (APIs) are a set of functions and tools that developers can use to access and modify Google Workspace data.

Go to Google Developers.

API quota

API quotas protect the Google infrastructure from excessive API requests. Traffic is blocked when the level of requests reaches the daily API quota level or a per-user rate limit.

Go to Monitor API quotas.

Calendar resource

A calendar resource is anything you schedule that isn't an event or attendee. A meeting room or a projector is common types of calendar resources.

Go to Manage Calendar resources.

CSV file

A comma-separated values (CSV) file stores plain-text data in a comma-separated format. It's used to map information on your legacy environment to your new Google Workspace account. Using a CSV file, you can map data for multiple users or calendar resources in a single file.

Global Address List

The Global Address List (GAL) is a searchable directory in Microsoft Outlook of all the users, groups, shared contacts, and resources defined for your Google Workspace domain. Global addresses are shared with everyone in your organization.

IMAP

Internet Message Access Protocol (IMAP) is a protocol that allows an email client to access email on a remote mail server. Using IMAP, you can access email data from Gmail or any RFC 3501-compliant IMAP server, including Exchange and Novell GroupWise.

Legacy environment

Your legacy environment (sometimes called "legacy account") is where you're migrating from, for example Microsoft Office 365.

MSI

An MSI is a Microsoft Windows installer package that's in a .msi format. It can be used to deploy applications from a server.

PST files or folders

Personal Storage Table (PST) is a type of file format that contains data in Microsoft Outlook, such as email, calendars, or contacts.

Top-level folders

A top-level folder is any folder in an email service that's at the same level as the inbox.

Data migration service terms

Domain migration report

A domain migration report contains the status of all migrating users. The report is in CSV file format.

Go to Monitor a migration.

EWS

Exchange Web Services (EWS) provides access to email, calendar, and contact data stored in a Microsoft Exchange server.

Impersonation rights

Impersonation rights allow you to use the permissions associated with another user's Exchange account, instead of using the permissions associated with your own account.

Item error report

An item error report provides details about any items that failed to migrate. The report is in a CSV file format.

Go to Monitor a migration.

Role account

A role account is an account on the mail server that you’re migrating from. You specify the role account when you’re setting up the migration. For example, when transferring data between Google Workspace accounts, the role account is the administrator's email address and password for your old Google Workspace account.

Its purpose depends on where you’re migrating from:

  • If you're migrating from an Exchange Web Services (EWS) server (Exchange 2010, Exchange 2013, Exchange 2016, or Exchange Online), the role account must have impersonation rights over all accounts being migrated so that the data migration service has access to the data.
  • If you're migrating from an IMAP server, the role account is only used to test connectivity to the mail server.

Go to Set up the data migration service.

TLS

Transport Layer Security (TLS) is a protocol that provides secure communication on the internet for web browsing, email, and other data transfers. To use TLS with the data migration service, your legacy server must have a TLS certificate.

Note: TLS and its predecessor, Secure Sockets Layer (SSL), are often both referred to as SSL.

Go to Set up your TLS certificate.

GWMME terms

Delta migration

A delta migration is performed after the bulk migration, but before all users become active and begin using Google Workspace accounts for daily activities. The purpose of a delta migration is to migrate email received in your users’ legacy inbox during the bulk migration period.

Public Folders

Public Folders in Exchange are used to share information with all or groups of users in your organization. Users can use Public Folders to post messages, calendar events, contacts, and so on.

Google Workspace does not support Public Folders in the sense that Exchange uses them. However, you can implement similar functionality by using Google Groups to create a collaborative inbox, or by using shared files and folders in Google Drive.

GWMHN terms

Admin database

An admin database is an HCL Notes database that’s part of the Google Workspace Migration for HCL Notes (GWMHN) application. A migration administrator uses the admin database to configure a migration for an HCL Domino domain.

Domino directory

Administrators use a Domino directory to manage a Domino system. It contains information about users, servers, and groups, as well as any custom entries you added.

If you register a user or server in a domain, the directory automatically creates the corresponding person and server documents in the Domino directory for the domain. These documents contain detailed information about each user and server.

Feeder database

A feeder database is a Notes database responsible for all migration tasks. A scheduled agent runs in each feeder database, extracts data, and migrates it to the Google Workspace account.

Notes template file (NTF)

A Notes template file (NTF) is a skeleton file that contains design elements, but no documents. Notes Storage Facility (NSF) files are created from NTFs. GWMHN is distributed as a set of NTFs.

Scheduled agents

Scheduled agents are tasks that are executed on the Domino server at specific intervals or times. Scheduled agents run inside a Notes application (or database). GWMHN uses scheduled agents to migrate data from HCL Notes to Google Workspace.


Google, Google Workspace, and related marks and logos are trademarks of Google LLC. All other company and product names are trademarks of the companies with which they are associated.
Was this helpful?
How can we improve it?

Need more help?

Sign in for additional support options to quickly solve your issue