Gladly — 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 Gladly (Ticket)
| Field | Supported |
| Requester | Yes |
| Company | No |
| Assignee | Yes |
| Group | No |
| Attachments | Yes |
| Comments | Yes |
| Tags | Yes |
| Custom fields | No |
| CC | No |
| First Response Time | No |
| Created date | Yes |
| Updated date | Yes |
| Closed date | Yes |
Field-level support migrating FROM Gladly (Contact)
| Field | Supported |
| Tags | No |
| Custom fields | No |
| Phone | Yes |
| Notes | No |
Migration options available for Gladly
- Migrate the newest records first - applies to: source (Ticket)
- Select records for Demo - applies to: source (Ticket)
- Transfer call recordings - applies to: source (Ticket)
Gladly — Setup & How-To Guide
Migrating from Gladly
- By default, migration is performed from a single inbox in one migration. Migrating from all or several inboxes can be done as a custom migration.
- The following comment types are read: EMAIL, CONVERSATION_NOTE, CHAT_MESSAGE, SMS, FACEBOOK_MESSAGE, WHATSAPP, INSTAGRAM_DIRECT, TWITTER.
Comments
0 comments
Please sign in to leave a comment.