Built-in tables for applications and major plugins
Introduction
This list explains common handling for built-in tables of applications and major plugins in Migration Manager, version control, and backup/restore. In most cases, users do not need to adjust tables one by one. Use the default strategy.
These mechanisms focus on different concerns:
- Migration Manager: publishes across environments. Common strategies include overwrite, schema-only, and skip.
- Version control: saves and restores key checkpoints during application building.
- Backup/restore: backs up and restores the application runtime state.
The “Data type” column comes from built-in classification. System base data participates in version control; business runtime data does not; runtime temporary data is not backed up.
Built-in table reference
Database
Server
System settings
Client
Multi-space
App monitoring
Main data source
Data source manager
External database connections
Visual data modeling
China region field
Auto-number field
UI Schema
UI templates
Flow engine
Block templates
iframe block
Mobile
Theme editor
Map block
Public forms
Template printing
ACL
Authentication
Two-factor authentication
API keys
Password policy
IP restriction
Users
Departments
User data sync
Workflow
Workflow approval
Workflow manual node
Workflow CC
Notification manager
In-app messages
Verification
Mail manager
AI
AI knowledge base
Environment variables
Migration manager
Backup manager
Audit logs
Async tasks
Record history
File manager
Localization
Localization tester
Custom request
Custom variables
User-defined tables
User-defined tables are treated as business data by default. In most cases, migrate only the table structure and choose schema-only.
If a user-defined table stores business configuration, categories, templates, rules, or other metadata, and those records should be synchronized from development to staging or production with the release, choose overwrite based on the business scenario.
If a user-defined table stores runtime data such as customers, orders, tickets, approval records, messages, or logs, avoid overwriting production records.

