Gmail — Migration Reference

Gmail — Migration Support Overview

Role in migrations

• Staff (HD): supported as source.
• Contact (HD): supported as source.
• Ticket (HD): supported as source.

Field-level support migrating FROM Gmail (Ticket)

Field-level support migrating FROM Gmail (Contact)

Migration options available for Gmail

• No specific migration options documented.

Gmail — Setup & How-To Guide

How to Set Up a Custom Demo

Open the email thread, right-click on the subject, and select Inspect (Chrome). In the code, look for data-legacy-thread-id and id — this is the correct ID to use for a custom demo.

Connection Issues

If the client can't connect their G-Suite account, the following can help:

1. An article explaining how to let other users on the same domain manage their access to apps that aren't verified as secure: https://support.google.com/a/answer/6260879?hl=en&ref_topic=7558663
2. A guide on adding an app to the list of trusted apps: https://support.google.com/a/answer/7281227?hl=en

If that doesn't help, apply the settings from the article above and, in the Domain-Wide Delegation section, add the Client ID and the scope we use for Gmail OAuth. Have the client copy these values:

• Client ID: 775234461020-m0tdnl9ib2sntinu4v5tdh4s7bks10u5.apps.googleusercontent.com
• OAuth scope: https://www.googleapis.com/auth/gmail.readonly

If nothing else works to connect Gmail, the client can import their emails from Gmail into Outlook and migrate from Outlook instead. Guide on importing Gmail to Outlook: https://support.microsoft.com/en-us/office/import-gmail-to-outlook-20fdb8f2-fed8-4b14-baf0-bf04b9c44bf7

Filtering Capabilities

Clients may ask to filter emails by subfolders (labels). This is possible, but should be confirmed with developers beforehand.