How to Migrate MySQL Databases

sudo nano /etc/mysql/mysql.conf.d/mysqld.cnf

Locate the `bind-address` setting in the file that opens:

```bash
bind-address            = 127.0.0.1

bind-address            = *

sudo systemctl restart mysql

Revert this change after migration to restore the original security posture.

### Enable GTID

Enable GTID on the source database to support logical replication (GTID creates a unique identifier for each transaction). To set up GTID, see the MySQL article [Enabling GTID Transactions Online](https://dev.mysql.com/doc/refman/5.7/en/replication-mode-change-online-enable-gtids.html).

Open the MySQL configuration file (`/etc/my.cnf` or `/etc/mysql/my.cnf`) and ensure it includes:

```text
[mysqld]
gtid_mode=ON
enforce_gtid_consistency=ON

If the file is in a different location, refer to the MySQL article [Using Option Files](https://dev.mysql.com/doc/refman/8.0/en/option-files.html) for OS-specific information.

Restart MySQL to apply the changes:

```shell
sudo systemctl restart mysql

### Grant Replication Privileges

Grant replication privileges to the user used for migration. To do this, log in to the database with an admin level user and grant the following permission to the target user:

```sql
GRANT ALL ON <database-name>.* TO 'username'@'%';
FLUSH PRIVILEGES;

Revert these permissions after migration.

Control Panel migrations require replication access across all databases. You can exclude databases in the [**MySQL migration** window](#using-the-control-panel) or by changing the [parameter `ignore_dbs`](/reference/api/reference/databases/#databases_update_onlineMigration) using the DigitalOcean API. In this case, only databases selected with the parameter need replication permissions.

{{__hugo_ctx pid=218}}
## Migrate a Database Using the API


    
How to Migrate a Database Using the DigitalOcean API
Create a personal access token and save it for use with the API.
cURL
    
        
    

Send a PUT request to https://api.digitalocean.com/v2/databases/{database_cluster_uuid}/online-migration.
Using cURL:

curl -X PUT \
-H "Content-Type: application/json" \
-H "Authorization: Bearer $DIGITALOCEAN_TOKEN" \
-d '{"source":{"host":"source-do-user-6607903-0.b.db.ondigitalocean.com","dbname":"defaultdb","port":25060,"username":"doadmin","password":"paakjnfe10rsrsmf"},"disable_ssl":false,"ignore_dbs":["db0","db1"]}' \
"https://api.digitalocean.com/v2/databases/9cc10173-e9ea-4176-9dbc-a4cee4c4ff30/online-migration"
Python
    
        
    

Using PyDo, the official DigitalOcean API client for Python:

import os
from pydo import Client

client = Client(token=os.environ.get("DIGITALOCEAN_TOKEN"))

req = {
  "source": {
    "host": "source-do-user-6607903-0.b.db.ondigitalocean.com",
    "dbname": "defaultdb",
    "port": 25060,
    "username": "doadmin",
    "password": "paakjnfe10rsrsmf"
  },
  "disable_ssl": False
  "ignore_dbs": ["db0","db1"]
}

update_resp = client.databases.update_online_migration(database_cluster_uuid="a7a8bas", body=req)


{{__hugo_ctx/}}


## Migrate a Database Cluster Using the Control Panel

To migrate a MySQL database using the [Control Panel](https://cloud.digitalocean.com/databases), select the target cluster on the **Databases** page.

On the cluster's **Overview** page, click the **Actions** button, and then select **Set Up Migration**.



In the **MySQL migration** window, select a connection type (**Hostname**, **Connection string**, or **Private IP address**) and enter the corresponding connection information. Enter the source database name, any databases you want to exclude, and your username and password. Then, click **Start Migration**. A status banner appears on the **Overview** page while data transfers.



You can stop the migration at any time by clicking the **Stop Migration** button in the status banner. Any data already transferred remains in the target cluster.


    
Warning
    
Migrations stop automatically after two weeks. We do not recommend using ongoing migration to keep clusters in sync. For read scaling, add a read-only node.
During migration, you can still write to the target database, but avoid actions that may result in replication issues:

Do not write to tables currently being migrated.
Do not modify replication or GTID settings on the source.
Do not change connectivity settings (for example, bind_address or trusted sources) in a way that interrupts communication between the source and target.