Umami v3 Upgrade: MySQL Not Supported

How to fix it

Try these in order — the most common fix is first.

1. 1. Pin to v2 until you migrate

   Copy steps
   1. Change your image tag or git checkout back to v2.19.0 so the instance keeps running
   2. Take a full MySQL backup
   Did this fix it? Yes No

2. 2. Prepare PostgreSQL

   Copy steps
   1. Install Umami v2.19.0 against an empty PostgreSQL database so it creates the tables
   2. Truncate the _prisma_migrations and user tables in PostgreSQL (the import refills them)
   Did this fix it? Yes No

3. 3. Move the data with a dump (under ~1M records)

   Copy steps
   1. mysqldump --no-create-info --default-character-set=utf8mb4 --quick --skip-add-locks -u USER -p DB > dump.sql
   2. sed -i 's/`/"/g' dump.sql to swap backticks for double quotes
   3. psql -U USER -d DB < dump.sql (or pipe into docker exec -i <container> psql)
   Did this fix it? Yes No

4. 4. Move the data with CSV (large databases)

   Copy steps
   1. Export each table with SELECT * INTO OUTFILE as comma-delimited CSV with " enclosures and \\ escaping
   2. Copy the CSVs to a host psql can reach (watch MySQL's secure_file_priv setting)
   3. Import each with \COPY table FROM 'file.csv' CSV NULL '\N' ESCAPE '\'
   Did this fix it? Yes No

5. 5. Upgrade to v3

   Copy steps
   1. Point DATABASE_URL at PostgreSQL
   2. Set APP_SECRET (required since v3.5.0)
   3. Deploy the v3 image and let migrations finish before sending traffic
   Did this fix it? Yes No

Symptoms

After pulling the latest Umami image or code, a MySQL-backed instance fails to build or start, or the docs no longer list a MySQL Docker image.

Why it happens

• Umami v3.0.0 removed MySQL support
• MySQL schema not on the latest v2 version (v2.19.0) before migrating
• Large tables too big for a single SQL dump

This guide also covers

• umami v3 mysql
• umami migrate mysql to postgresql
• umami v3 upgrade
• umami mysql not supported

The same problem in other apps

All storage, upload & download guides →

• Fathom GA4 Import Failed or Stuck (Fathom Analytics)

Other Umami errors

• Umami Not Tracking Visitors (No Data Showing)
• Umami Blocked by Ad Blockers (uBlock Origin, Brave)
• Umami Migration Failed (Prisma P3009 / P3018 Error)
• Umami Docker "Unable to Connect to the Database"
• Umami Default Login and Forgot Password Reset
• Umami Shows Wrong Country or "Unknown" Location
• Umami Custom Events Not Showing
• How to Exclude Your Own Visits in Umami