Gleap — Migration Reference

Gleap — Migration Support Overview

Role in migrations

• Staff (HD): supported as source.
• Company (HD): supported as source.
• Contact (HD): supported as source.
• Ticket (HD): supported as source.
• Category (KB): supported as both.
• Folder (KB): supported as both.
• Article (KB): supported as both.

Field-level support migrating FROM Gleap (Ticket)

Field-level support migrating FROM Gleap (Company)

Field-level support migrating FROM Gleap (Contact)

Field-level support migrating FROM Gleap (Article)

Field-level support migrating TO Gleap (Article)

Migration options available for Gleap

• Migrate content translations - applies > to: both (Article)
• Migrate the newest records first - > applies to: source (Ticket)
• Select records for Demo - applies to: > source (Ticket)
• Inline images in tickets - applies to: > source (Ticket)
• Skip ticket attachments - applies > to: source (Ticket)

Gleap — Setup & How-To Guide

For more information: https://help-desk-migration.com/help/gleap-migration-guides/

How to Get the API Key in Gleap?

To migrate your data from Gleap to another help desk platform, you’ll need an API key. Each API key is generated per project. Follow these steps:

1. Open your project window in Gleap and click Settings.
2. Go to the Security tab → API keys.
3. Click Generate API key.
4. Enter a name and (optionally) select an avatar.

Note: Every API key is tied to a service account that makes API requests.