Files
dbx/docs/content/docs/data-transfer.mdx
T
t8y2 89fa8c02be docs: add landing page and upgrade all documentation with advanced components
- Add product landing page with hero section, stats, feature cards, database badges, comparison table, and screenshots
- Register Fumadocs MDX components (Tabs, Steps, Callout, Cards, Accordions) globally
- Rewrite all 17 doc pages (CN + EN) with richer content, use cases, and advanced components
- Add competitive comparison table (vs DBeaver/Navicat/TablePlus)
- Add ~300 lines of responsive landing page CSS
2026-05-07 14:53:35 +08:00

48 lines
1.5 KiB
Plaintext

---
title: Data Transfer
description: Cross-engine data migration with automatic type mapping. MySQL to PostgreSQL, SQLite to SQL Server.
---
<Callout type="info">
Cross-engine data migration with automatic type mapping and syntax adaptation. MySQL to PostgreSQL, SQLite to SQL Server — it just works.
</Callout>
## Use Cases
- **Cross-engine migration** — MySQL → PostgreSQL, SQLite → SQL Server
- **Environment sync** — Pull production data into your dev environment
- **Data consolidation** — Merge data from multiple sources into one database
## Workflow
<Steps>
<Step>
### Select Source and Target
Choose the **source** and **target** connections. They can be different database engines.
</Step>
<Step>
### Choose Tables
Transfer all tables at once, or pick a subset.
</Step>
<Step>
### Start Transfer
Click "Start Transfer". DBX handles type mapping and syntax differences automatically.
</Step>
</Steps>
## Progress Tracking
During the transfer, a progress indicator shows:
- Which table is currently being transferred
- How many rows have been transferred so far
- The overall progress across all selected tables
## Error Handling
If an error occurs during transfer (type incompatibility, constraint violation, etc.), DBX:
- Logs the error with details about which table caused the problem
- Continues transferring other tables without stopping the entire job
- Shows a summary of all errors after the transfer completes