Migrate data to MatrixOne

Migration includes compatibility assessment, full copying, consistent/incremental handoff, reconciliation, cutover, and backout. MySQL protocol compatibility in v4.2.5 helps tools connect; verify types, DDL, collation, program objects, and transaction behavior separately.

Select a path

Path

Conditions

Acceptance boundary

DBeaver/JDBC batch transfer

Small trial or a write-suspension window

Table reads alone do not guarantee cross-table consistency or continuous CDC

SQL export/import

Reviewed target DDL and consistent source export

Check session SQL, errors, committed batches, and object support

Files + LOAD DATA

Explicit format, paths, and batch recovery plan

Match CSV dialect, NULL/empty strings, encoding, time, and accessibility

DataX/batch tools

Pinned reader/writer/driver and column mappings

No automatic snapshot/log-position handoff; job exit status is not reconciliation

Full copy + source CDC

Verified source log reading, positions, and catch-up

Bind snapshots to binlog/GTID, LSN, or SCN; test replay and recovery

A full copy and validation during write suspension is an explicit offline strategy. With source writes continuing, establish consistent snapshots and reliable incremental handoff. A GUI “online copy” is not a zero-write-interruption migration guarantee.

Phases and evidence

  1. Assess source/MO/tool versions, keys, types/ranges, encoding/collation, timezones, constraints, indexes, programs, identities, and privileges.

  2. Trial real boundary values and generated DDL on an isolated target; retain conversion differences rather than silently stripping constraints with global text replacement.

  3. Full copy at a consistent point or write-suspension window; record table/shard ranges, counts, checksums, batches, errors, and retries.

  4. Incremental bind source positions and test inserts/updates/deletes, DDL, ordering, duplicates, and checkpoint recovery. Retain logs across copy, outage, and catch-up.

  5. Validate key sets, critical values, NULLs, amounts/watermarks, Unicode/bytes, time, privileges, and business queries at one consistency boundary.

  6. Cut over suspend old writes, capture the final position, catch up and reconcile, then switch. Prevent old pools/Tasks/jobs from continuing to write the old database.

  7. Back out according to the plan before target writes. Once target writes exist, reconcile those changes instead of merely changing a connection string back.

Tools and direction

LOAD DATA reads a specified file location: distinguish MO-server files, client LOCAL files, and object storage. SOURCE is a MySQL CLI file-execution command, not server SQL sent through JDBC/PyMySQL.

The documented mo_cdc reads from MatrixOne and can write to MySQL/MatrixOne. Its mysql:// protocol does not establish support for inbound CDC from a MySQL source. Select and verify source-specific log connectors for MySQL/PostgreSQL/Oracle/SQL Server.

Entry points

This review targets v4.2.5 and executes a small MySQL 8.0.44 copy, mysqldump/client import, target type boundaries, and negative reconciliation controls. Oracle/SQL Server/PostgreSQL sources, complete DataX/DBeaver/CDC pipelines, and production zero-downtime migration are unverified.