Supabind

Databases

Export your transformed files directly to MySQL, PostgreSQL, or MongoDB tables and collections.

Overview

DB Export Transform Files sends a transformed file straight into a connected database. It has three tabs-Create Export Profile, Export Data, and Export Monitoring-covering the three database types: MySQL, PostgreSQL, and MongoDB.

Connect a Database

Before you can export, add a database connector under Data Adapters → Databases → Configure. The fields differ slightly by database type.

MySQL / PostgreSQL Export Configuration

Configure your database to export transformed files directly to tables

Host *

e.g. localhost, an IP address, or db.example.com

Port

Defaults to 3306 (MySQL) or 5432 (PostgreSQL)

Database Name *

The name of your target database

Username *

Needs write access, e.g. root or postgres

Password *

Password for the account above

Use SSL Connection

Recommended for remote servers-required by most cloud providers for PostgreSQL

MongoDB Export Configuration

Configure your MongoDB connection to export transformed files directly to collections

Connection String *

Full MongoDB URI, including credentials, e.g. mongodb+srv://user:[email protected]

Database Name *

Target MongoDB database name

Steps

  1. Choose MySQL, PostgreSQL, or MongoDB and fill in its connection fields.
  2. Click Test Connection to confirm the database accepts the credentials before saving.
  3. Click Save Configuration, or Cancel to discard the changes.

You can save more than one connector per database type-for example, a MySQL export for staging and another for production-and pick between them when creating an export profile.

Create an Export Profile

On the Create Export Profile tab, pair a transformed file with a saved database connector.

Steps

  1. Under Select Source File, choose a file from your completed export jobs and transformations.
  2. Under Select Destination, pick a saved connector from the list-each entry shows the database type and connection name, e.g. "MySQL Export - sql12822669".

Configure the Table

Table Configuration decides whether the export creates a brand-new table or writes into one that already exists.

Two options

Create New Table

Enter a New Table Name; the table is created with columns based on your field mappings.

Use Existing Table

Write into a table that already exists in the destination database.

Map Fields to Columns

Field Mapping pairs each source field with a destination column.

Steps

  1. For each row, choose a Source Field and type its matching Destination Column name.
  2. Click Add Mapping for additional fields, or the trash icon to remove one.
  3. When you're creating a new table, click Create Table once the mapping list shows "Ready to create table with N columns."
  4. Add an optional Profile Name, then click Save as Template to finish.

Save & Reuse Export Profiles

Saved profiles live under the Export Data tab, where each one can be re-run at any time.

What you'll find there

  • Each profile's source → target file, write Method (New Table or Existing), table name, connector, field mapping count, and usage stats.
  • A Start Export button to run the profile immediately, plus preview and delete icons.
  • A search bar to find a profile by name, description, source file, or connector.

A profile flagged Source Deleted points to a source file that no longer exists. Its Start Export button is replaced with Delete-remove the profile or recreate it against a current file.

Monitor Exports

Export Monitoring logs every export run against its file, destination, and outcome.

What each log shows

  • The File Name, Destination connector, Table, and write Method used.
  • Status (Completed or Failed), records processed, and when the run started and completed.
  • Filters to search by file name, or narrow the list by Status or Destination.

Was this article helpful?

Need More Help?

If a connection test is failing, or an export keeps showing as Failed, our support team is here to help.

Contact Support