Data migration
Plan and run a one-time data move.
Migration is a one-time data-copy workflow, separate from CDC. Map supported sources to destinations and review targets before the copy starts.
Scroll each list independently and select a connector. Route availability is checked during setup.
Core capabilities
Explicit mappings
Map source schemas to target schemas or datasets and review individual table targets.
Bounded movement
Use controlled readers, destination batching and recorded checkpoints rather than an unbounded browser operation.
Destination safeguards
Fail closed when an automatically managed physical target is occupied or cannot be verified.
Workflow
01Map, review and copy.
Select compatible connections, map schemas and tables, validate the plan and run the copy. Progress stays separate from ongoing CDC pipelines.
Connection and runtime checks
Schema, dataset and table mappings
Parallelism based on available capacity
Provider-specific prerequisites
Configuration and runtime evidence stay attached to the workflow.
Workflow
02Copy data between supported systems.
The illustration previews a source-to-target connector choice. In PipePilot, review the schema and table mappings before copying; use a separate CDC pipeline if changes must continue afterward.
Separate migration and CDC workflows
Stable targets through retries
No overwrite of another pipeline’s generated target
Run history for review
Configuration and runtime evidence stay attached to the workflow.
Next step
Plan your data workflow.
Share your source, destination and network needs. We will confirm the supported workflow and prerequisites.