Server Migrations

We have a number of workflows to help perform different types of migration tasks, which help adjust where Posit Connect runs and where its data is stored. Do not combine these migration procedures. Each workflow should be performed separately.

Do not upgrade Connect while performing any of these migration tasks. Perform a software upgrade first, then begin your migration.

We strongly recommended that you back up your Connect data before following any of these workflows.

Server to Server migration

You may need to migrate your Connect installation when moving from one environment to another (e.g., physical to virtual or on-prem to cloud).

For server migrations, refer to the How to Upgrade and/or Migrate Posit Team guide.

Server architecture migration

These procedures cover changing architectural components of a Connect implementation.

  1. SQLite to PostgreSQL

    Shift from the default SQLite database to PostgreSQL.

  2. Local file system to NFS

    Shift from using server-local storage to a networked file-system.

  3. Server-to-Container

    Shift from a server or virtual machine (VM) into a container.