Data Migration from Dixa
Last updated: December 16, 2025
This guide will help you migrate from Dixa to Pylon. Talk to your AE about a data migration to make sure that we cover what you are looking for.
This migration will bring over the tickets in a closed state, meaning neither you or the customer can reply on these tickets from Pylon.
For the overall process, see 📄 Migrating your Data to Pylon
What we'll need from you
To get started with your migration, we’ll need the following:
Admin access to your Dixa Instance
Your users should already be invited to Pylon
An idea on what you want to bring over, we recommend only bringing over custom fields that you are going to use going forward.
Definitions for which tickets/ objects you want to migrate
Supported fields
Dixa | Pylon |
Customers | Contacts |
Conversations | Issues |
Groups | Teams |
Agents and admins | Users |
Custom Fields | Custom Fields |
Knowledge Base | |
Articles | Articles |
Categories | Collections |
Dixa doesn't support Accounts, so when we migrate over your Dixa Customers, we will try and create accounts based off of their email domains.