<aside>

Dear Tembo Cloud Friend,

Thank you for choosing Tembo and believing in our vision. We're now in the process of sunsetting Tembo Cloud, as we take a bold step toward the future. We’d love to walk through your current setup and support your transition to another managed Postgres provider.

Everything we’ve learned running a managed Postgres platform is fueling what’s next for us: a superhuman junior developer (AI Agent) that opens pull requests to fix the issues it discovers in your software, autonomously.

We’re incredibly grateful to have had your support on this journey. While we’re closing one chapter, we’re opening an even more ambitious one—and we’d love for you to be part of it.

Talk soon, The Tembo Team

For more information on Tembo V2, or sunsetting Tembo Cloud, contact [email protected].

**

</aside>

Timeline

Migration Guide

There are two options for moving your data from Tembo Cloud to a new PostgreSQL instance: Logical Replication and Backup and Restore. Either way, the basic steps are to set up a new PostgreSQL cluster, install any extensions you require, copy the data to the new database, and move clients to the new host. Read on for details.

Preparation

Before migrating your databases to a new home, you'll need to set up that new home and ensure it includes all the necessary dependencies. In addition to PostgreSQL itself, of course, if you rely on extensions you'll need to install them and their dependencies, as well.

Run this query in a database to get a list of extensions loaded into the database:

SELECT e.extname AS "Name", e.extversion AS "Version", n.nspname AS "Schema",
       c.description AS "Description"FROM   pg_catalog.pg_extension e
LEFT   JOIN pg_catalog.pg_namespace n ON n.oid = e.extnamespace
LEFT   JOIN pg_catalog.pg_description c ON c.objoid = e.oid
       AND c.classoid = 'pg_catalog.pg_extension'::pg_catalog.regclass
ORDER  BY "Name";

Be sure to run this query in all of the databases you plan to migrate. Use these list to install what you need.

The following extensions are part of the PostgreSQL core distribution's contrib modules, usually available in a package named postgresql-contrib or similar, and available for install by all the Postgres cloud providers:

adminpack auto_explain btree_gin btree_gist citext cube dblink dict_int dict_xsyn earthdistance fuzzystrmatch hstore

intarray jsonb_plpython3u ltree ltree_plpython3u moddatetime pg_buffercache pg_stat_statements pg_trgm pgcrypto pgrowlocks pgstattuple plperl

plperlu plpgsql plpython3u pltcl pltclu postgres_fdw tablefunc tsm_system_rows unaccent uuid-ossp xml2

These extensions are readily available via the PGDG APT, PGDG Yum, and Trunk packaging registries for Linux:

hypopg mobilitydb mysql_fdw ogr_fdw orafce pg_cron pg_partman

pg_track_settings plpgsql_check pgsodium pgtt postgis postgis_raster postgis_tiger_geocoder

postgis_topology rdkit semver tds_fdw timescaledb vector

These extensions are available for AMD64 Linux from Trunk and some other registries and may require additional dependencies to be installed (the trunk CLI will list them):

citus citus_columnar clerk_fdw clickhouse_fdw collection columnar emaj http multicorn orb_fdw parquet_s3_fdw pg_analytics pg_duckdb pg_graphql pg_hashids pg_ivm

pg_jsonschema pg_lakehouse pg_later pg_net pg_parquet pg_proctab pg_search pg_smtp_client pg_stat_monitor pg_surgery pg_tier pg_tle pg_uuidv7 pgbouncer_fdw pgbson pgjwt

pgml pgmq pgroonga pgroonga_database plprofiler plv8 prometheus_fdw redis_fdw system_stats temporal_tables timeseries vectorize vectorscale wrappers zson