Help Center / Components
Database Data Migration
Once your database schema is in place, the next step is moving your actual data. The Database Data component handles copying all the rows from your source tables into the destination instance.
What Gets Migrated
When you select the Database Data component, Stack2X transfers:
- Table rows -- Every row across all tables in the migrated schema is copied to the destination.
- Sequences -- Auto-increment counters and sequence values are synced so new rows on the destination continue from the correct number.
- Large objects -- Any large binary objects stored in PostgreSQL are included.
Stack2X streams data in batches to handle databases of any size without running into memory limits. Progress is reported in real time so you can track how much data has been moved.
Plan Availability
Database Data migration is included on all plans, including the Free tier. There are no row count limits enforced by Stack2X -- the only constraint is the storage available on your destination Supabase project.
Tips and Considerations
- Always migrate schema first. The destination needs tables to exist before data can be inserted. When you select both Database Schema and Database Data, Stack2X automatically runs the schema step first.
- Foreign key ordering. Stack2X inserts data in dependency order so that foreign key constraints are satisfied. You do not need to disable constraints manually.
- Downtime window. For production databases, consider planning a short maintenance window. Any rows written to the source after the migration starts will not be included. Stack2X does not perform continuous replication.
- Large databases. Migrations with millions of rows may take longer. Stack2X shows an estimated time remaining once the transfer begins. You can safely close your browser and check back -- the migration runs server-side.
- Test first. If possible, run a trial migration to a staging instance before touching your production destination. This gives you confidence that everything transfers correctly without affecting live users.