Databases
Import and clone data
Move an existing PostgreSQL database or create a controlled copy.
8 minute read ยท Updated September 2026Import an existing database
- 1Create an empty target database in the correct project and region.
- 2Open Import & clone and select Import.
- 3Provide a source PostgreSQL URL that the migration worker can reach.
- 4Run preflight validation, then begin the import.
- 5Review row counts, extensions, sequences, and application smoke tests before cutover.
Plan the cutover
- Reduce source write activity or schedule a maintenance window.
- Take a final source backup.
- Update the application secret only after validation.
- Keep a documented rollback endpoint and decision time.
- Monitor errors, latency, and connection count after cutover.
Clone a Renviq database
A clone is an independent database copy for testing, investigation, or migration rehearsal. Treat cloned production data as production-sensitive and apply masking before broad developer access.
Sensitive data follows the copy
Cloning changes infrastructure, not data classification. Access, retention, deletion, and breach controls still apply.
Was this guide useful?
Get helpIf anything is unclear or incorrect, tell the support team.