> ## 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.

# PostgreSQL integration

> Export Octoparse task data to PostgreSQL for structured storage, querying, and downstream analytics.

The PostgreSQL integration lets you export Octoparse task results into a PostgreSQL database. It is useful for teams that need reliable structured storage for extracted web data.

## When to use PostgreSQL

Use PostgreSQL when:

* Data needs to support analytics or reporting
* Your team already uses PostgreSQL as a central data store
* Extracted records need to be joined with other datasets
* Data volume is too large for spreadsheet workflows
* Recurring exports need a database destination

## Setup workflow

<Steps>
  <Step title="Prepare the destination table">
    Define the columns that should receive Octoparse fields.
  </Step>

  <Step title="Check access details">
    Confirm host, port, database name, user credentials, and network access.
  </Step>

  <Step title="Map task fields">
    Match each extracted field to the correct PostgreSQL column.
  </Step>

  <Step title="Run a test export">
    Verify that records are inserted correctly and that special characters display as expected.
  </Step>

  <Step title="Schedule or automate">
    Enable recurring export only after the test output is correct.
  </Step>
</Steps>

## Things to verify

| Check         | Why it matters                               |
| ------------- | -------------------------------------------- |
| Column names  | Prevents mapping errors                      |
| Data types    | Avoids failed inserts or truncated values    |
| Primary keys  | Helps control duplicate behavior             |
| Permissions   | Ensures the export user can write data       |
| Network rules | Allows Octoparse to connect to the database  |
| Encoding      | Preserves non-English characters and symbols |

<Tip>
  For production workflows, coordinate with the database owner before enabling recurring exports.
</Tip>