Workspace  /  Content  /  Import content
Supabase connectedCONTENT IMPORTSO
Bring your stories with you

Import your publication.

Read your WordPress MySQL export. Keep your images right where they are.

Large-file import preparation · Your SQL file is analysed in this browser and is not uploaded or executed. Review the results and export a migration JSON file. Large-file processing depends on available browser memory. Sign in as an authorized publication admin to save reviewed posts and taxonomy into Supabase.
1Choose source
2Review content
3Export migration

WordPress database export

.sql · UTF-8 · up to 250 MB

Import preferences

PRESERVE ORIGINAL MEDIA
Used to resolve relative upload paths. Existing absolute media URLs stay unchanged.
If multiple WordPress sites are detected, enter the exact prefix you want.
Keep the original uploads folder available after switching your domain. If the new site uses the same hostname, route /wp-content/uploads/ to the old media host or use a dedicated media domain. DNS changes alone do not preserve old image paths.

Article preview

From SQL file to reviewed content

  1. Export the original WordPress database as UTF-8 SQL from phpMyAdmin. Plain CREATE TABLE and INSERT INTO … VALUES dumps are supported, up to 250 MB. Individual SQL statements must be under 32 MB.
  2. Select the file and confirm the source URL, table prefix and date range. Compressed files, INSERT … SELECT, binary dumps and nonstandard SQL are not supported.
  3. Analyse the file. Review posts, featured image mappings, categories and media paths.
  4. Export the normalized migration JSON. No tables, users, credentials or scripts are executed.
  5. To save posts, sign in as a publication admin and run the database import. Original media URLs must remain reachable; reachability is not checked by this preview.
The SQL file can contain sensitive data. Prefer a content-only export. This tool reads it locally, ignores users/options, and does not send the file to a server.