# Migrating to a new server that has a new DB and new S3 buckets for backup and uploads

**URL:** https://meta.discourse.org/t/migrating-to-a-new-server-that-has-a-new-db-and-new-s3-buckets-for-backup-and-uploads/395948
**Category:** Self-hosting
**Tags:** backups, install
**Created:** [12 februari 2026 om 18:15 UTC](https://meta.discourse.org/t/migrating-to-a-new-server-that-has-a-new-db-and-new-s3-buckets-for-backup-and-uploads/395948 "2026-02-12T18:15:25Z")
**Posts on this page:** 1
**Showing post:** 16

<div class="post-metadata">

### Author: ![supermathie](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/supermathie/32/507518_2.png) [@supermathie](https://meta.discourse.org/u/supermathie)
#### Post date: [13 februari 2026 om 20:38 UTC](https://meta.discourse.org/t/migrating-to-a-new-server-that-has-a-new-db-and-new-s3-buckets-for-backup-and-uploads/395948/16 "2026-02-13T20:38:17Z")

</div>

> [@philh](#):
>
> unsupported installs

Pointing a Discourse container at an external postgresql and redis server using our container image with our tooling is a supported install.

RDS\[1\] is Postgresql, and Elasticache is Redis, this is fine.

> [@stevejr](#):
>
> The old Discourse server is on a pretty old version - by doing the backup/restore in the new Discourse server will that just run all the relevant upgrade commands?

This should be fine we do this for people moving onto our hosting.

My preference is to keep the process as simple as possible, so if you can run a full backup (including uploads) on the old server and restore it to the new, that lets you fully test out the new setup without any impact on the old one.

* * *

1. ok, Postgresql RDS

---

_[View the full topic](https://meta.discourse.org/t/migrating-to-a-new-server-that-has-a-new-db-and-new-s3-buckets-for-backup-and-uploads/395948)._