Standard Tables
Data Mission Sync can synchronize most standard Dataverse tables that have Change Tracking enabled. Common tables include:
| Category | Tables | Notes |
| Core CRM | account, contact, lead, opportunity | Most commonly synchronized |
| Sales | quote, order, invoice, product, pricelevel | Full sales pipeline data |
| Service | incident (case), knowledgearticle | Customer service data |
| Marketing | campaign, list, campaignresponse | Marketing automation data |
| Activity | email, phonecall, appointment, task | Activity history |
| System | systemuser, team, businessunit, audit | Organizational structure |
This is not an exhaustive list. Any Dataverse table that supports Change Tracking can be synchronized, including tables from Dynamics 365 applications (Sales, Service, Marketing, Field Service, etc.).
Custom Tables
Custom tables you create in Dataverse are fully supported for synchronization, provided they have Change Tracking enabled. Custom tables follow the same synchronization process as standard tables.
Custom table naming conventions:
• Publisher prefix is preserved (e.g., cr123_customtable becomes cr123_customtable in SQL)
• Column names retain their logical names from Dataverse
• Primary key columns follow the pattern {tablename}id
| 💡 Tip: When creating custom tables in Dataverse, enable Change Tracking from the start. This avoids having to enable it later and ensures the table is immediately available for synchronization. |
Unsupported Tables
The following table types cannot be synchronized:
| Table Type | Reason |
| Virtual Tables | Virtual tables don't store data in Dataverse — they connect to external data sources. Since there's no underlying Dataverse data, Change Tracking is not available. |
| Elastic Tables | Elastic tables use Azure Cosmos DB storage and don't support the standard Dataverse Change Tracking API. |
| Tables without Change Tracking | Change Tracking must be enabled on a table before it can be synchronized. Some system tables don't support enabling Change Tracking. |