> ## Documentation Index
> Fetch the complete documentation index at: https://www.octoparse.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# MySQL integration

> Export Octoparse task data to MySQL for structured storage and downstream data workflows.

The MySQL integration sends Octoparse task results to a MySQL database. Use it when extracted data needs to be stored in a structured database for applications, reporting, automation, or internal data workflows.

## When to use MySQL

Use MySQL when:

* Data needs to be queried by applications or BI tools
* Spreadsheet exports are not scalable enough
* You need recurring structured storage
* Teams need a shared database destination
* Data should feed an existing relational workflow

## Setup workflow

<Steps>
  <Step title="Prepare the database">
    Create or identify the target database and table structure.
  </Step>

  <Step title="Confirm network access">
    Make sure Octoparse can reach the database host and port.
  </Step>

  <Step title="Map fields">
    Match Octoparse output fields to database columns.
  </Step>

  <Step title="Test with sample data">
    Export a small result set and verify column mapping, data types, and encoding.
  </Step>

  <Step title="Enable recurring export">
    Use scheduled runs only after the database export is verified.
  </Step>
</Steps>

## Before exporting

Check:

| Area          | What to verify                                             |
| ------------- | ---------------------------------------------------------- |
| Host and port | Database is reachable from the export environment          |
| Credentials   | User has permission to insert or update data               |
| Table schema  | Columns match the task output                              |
| Data types    | Text, numbers, dates, and URLs fit the destination columns |
| Duplicates    | Export behavior does not create unwanted repeated rows     |
| Encoding      | Special characters are stored correctly                    |

<Warning>
  Database exports should be tested carefully. Incorrect field mapping or duplicate handling can affect downstream systems that depend on the database.
</Warning>