Review the destination
Choose the objects to move. Check table names, field types, primary keys and relationship mappings before approving the plan.
Migrate
Move your data.
Review every step.
Bring existing databases and files into OriginChainDB. Review the mapping, check your data and verify the move before you switch your application.
Illustrative migration planReview
FromYour sourceExisting records
ToOriginChainDBMapped tables
Field mappingDestination type
record_id
text created_at
timestamp description
text Inspect the plan before you move.
Supported sources
Start with
what you have.
Copy selected data from supported databases or object-storage files. Use live sync with supported PostgreSQL or MySQL sources to keep applying changes until switchover.
Migrate requires a dedicated configuration. File imports support CSV, TSV, JSONL and JSON arrays, including gzip-compressed data.
Read the source requirements| Source | Copy | Live sync |
|---|---|---|
| PostgreSQL | Yes | Yes |
| MySQL | Yes | Yes |
| CockroachDB | Yes | Copy only |
| MariaDB | Yes | Copy only |
| SQL Server | Yes | Copy only |
| MongoDB | Yes | Copy only |
| S3-compatible files | Yes | Copy only |
From source to destination
A move you can inspect.
Make the important decisions before your application depends on the new database.
Check and copy your data
Find values that do not fit the plan before the move. Follow copied and set-aside counts, then resolve anything that needs attention.
Verify, then switch
Review the verification results and test your application. For live migration, pause source writes and complete the documented switchover.
A completed copy can still contain set-aside rows. Review the recorded counts and verification results before treating a table as ready.
More ways to use the data
Prepare for what
you want to build.
Review additional data shapes as part of your migration plan.
Make the connections useful.
Review full-text fields and graph mappings during planning. Supported source relationships can become connections your application can query.
Explore migration mappingsPrepare selected text for similarity.
Use a tested saved embedder to embed selected rows during migration. Choose text fields, row conditions and a maximum row count for the embedding work.
Explore embedding runsPlan your move
Know the next step.
Review the migration guide, then check how your application will connect and query the destination.
Does copying change my source records?
A copy reads the selected source data without changing its rows. Live sync also requires source replication access and setup. Review those prerequisites before starting.
What happens to rows that cannot be copied?
By default, Migrate sets a problematic row aside and continues. You can choose to stop the table instead. A table with set-aside rows is partial; review the reasons, fix the issue and follow the supported retry procedure.
Can live sync run as permanent replication?
Live sync is a migration workflow for supported PostgreSQL and MySQL sources. Pause source writes for switchover, verify the destination and update your application's connection. It is not permanent bidirectional replication.
Where do I begin?
Open your dedicated instance, then choose Platform, Migrations and Data migration. The migration guide walks through source selection, planning and verification.
Build with OriginChainDB