# Migrate From RDS To Guepard

## Overview

Migrating from Amazon RDS to Guepard lets you move to a platform built for instant branching, time-travel, that supports git for your databases.

With Stakpak, you can automate the migration: connect your RDS instance, create snapshots, spin up test branches, and safely roll out changes with minimal manual work.

This guide shows how to migrate your RDS database to Guepard using Stakpak.

### But What is Guepard?

Guepard lets you work with databases the way you work with code. Branch your Postgres, MySQL, or MongoDB database in seconds, test changes safely, roll back when things go wrong. you dont need to wait hours for database copies or stressing about schema migrations breaking production.

### Why Migrate to Guepard?

* **Instant database branching:** branching doesn't duplicate data at the storage level
* **Git workflows:** create snapshots and time travel between database versions
* **Automatic idle detection:** stops databases when not in use, starts when needed
* **Multiple branches:** work on different database versions simultaneously
* **API first:** integrates with CI/CD and DevOps tools
* **Deployment options:** private nodes or on-premise for security

### How Stakpak Helps? <a href="#how-stakpak-helps" id="how-stakpak-helps"></a>

You don't need to memorize any commands or debug anything; you can just ask Stakpak to migrate from RDS to Guepard, and it will do everything for you.

### Step by Step Guide <a href="#step-by-step-guide" id="step-by-step-guide"></a>

#### Architecture <a href="#architecture" id="architecture"></a>

Our current setup uses a single Amazon RDS PostgreSQL instance (db.t3.medium with 250 GB gp3 storage) in us-west-2c (Oregon) as the primary database for our application.

**The problem with this architecture:**

* All environments rely on the same RDS instance or slow manual clones
* Creating realistic staging/test data requires time-consuming snapshots and restores
* Schema changes and migrations are risky with limited rollback options
* Spinning up short-lived environments per feature/PR is painful and expensive

Let's see how we can fix these problems with Guepard

#### Prerequisites <a href="#prerequisites" id="prerequisites"></a>

1. [install-stakpak](https://stakpak.gitbook.io/docs/get-started/install-stakpak "mention")
2. [Install Guepard CLI](https://github.com/Guepard-Corp/guepard-cli)
3. Make sure your AWS credentials are configured

#### Guide <a href="#guide" id="guide"></a>

<figure><img src="https://2684022488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOFDKnFMEMmJjoclGx9Hr%2Fuploads%2F4NMiJGlyBqs6OQyC4fif%2Fimage.png?alt=media&#x26;token=1f1fcd04-c10e-4413-8311-4fb8c3165a95" alt=""><figcaption></figcaption></figure>

1. Just ask stakpak to "Migrate from RDS to a guepard database"
2. First, it made sure that the Guepard is installed and authenticated&#x20;
3. Now created a database in Guepard and got the RDS connection details automatically

![](https://2684022488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOFDKnFMEMmJjoclGx9Hr%2Fuploads%2FknAdVZyhKXtXBFhvRtpE%2Fimage.png?alt=media\&token=be879417-67ad-48fa-a2d0-0e0c677536bc)<br>
