PostgreSQL
Access

PostgreSQL to Access Converter

Export PostgreSQL-compatible data into Microsoft Access .mdb or .accdb files for reporting, local analysis, or Office workflows with type-mapping review and optional DBSync.

PostgreSQL → Access migration usually means copying selected PostgreSQL tables into a Microsoft Access .mdb or .accdb file for reporting, local analysis, or Office workflows.

DBConvert connects to PostgreSQL, Amazon RDS / Aurora for PostgreSQL, Azure Database for PostgreSQL, Google Cloud SQL for PostgreSQL, or Supabase and writes a Microsoft Access .mdb or .accdb file with tables, fields, indexes, primary keys, foreign keys, and supported views mapped for review. Access file size, generated keys, long text and binary values, Unicode text, timestamps, arrays, JSON, and UUIDs are where the review work sits.

  • DBConvert saves the job as a rerunnable session, and DBSync keeps PostgreSQL and Access aligned while both sides remain active.

Which tool: DBConvert or DBSync?

DBConvert for PostgreSQL → Access

One-time migration or repeatable exports. Use it when Access is the target file for reporting, local analysis, QA samples, or a lightweight Office workflow.

DBSync for PostgreSQL ↔ Access

Recurring exchange. Use it when PostgreSQL remains active and the Access file needs periodic inserts, updates, or deletes. Review synchronization concepts.

Need more context? Compare DBConvert and DBSync side by side →

How DBConvert handles the PostgreSQL → Access differences

DBConvert handles connection, object selection, type mapping, Access file creation, row transfer, and validation. PostgreSQL server-side code and Access application design remain separate work.

Source and target shape

DBConvert reads local, hosted, or cloud PostgreSQL sources and writes an Access .mdb or .accdb. Access is capped at 2 GB, so large sources should be filtered or split.

Generated keys

PostgreSQL serial, identity columns, and sequences need an Access AutoNumber or Number policy. Confirm next values before new Access inserts begin.

PostgreSQL-only types

Arrays, ranges, enums, jsonb, UUIDs, network types, and extension-backed types need an Access storage policy: text, Long Text, lookup tables, or flattened columns.

Timestamp behavior

PostgreSQL timestamptz and infinity values are not Access defaults. Normalize timezone assumptions and sentinel values before the export becomes a workflow.

Application SQL boundary

DBConvert migrates tables, fields, supported views, indexes, and foreign keys. PostgreSQL functions, triggers, rules, extensions, grants, row-level security, and application SQL are not converted into Access forms, reports, macros, or VBA.

Type mapping checkpoints

PostgreSQL Access Notes
integer / bigint / identity Number / Large Number / AutoNumber Large Number requires modern Access .accdb.
numeric(p,s) Decimal / Number Review precision and scale before reports use the Access file.
varchar / text Short Text / Long Text Check Access text length limits and Unicode behavior.
bytea OLE Object / attachment policy Validate with real binary values, not only row counts.
timestamp / timestamptz Date/Time Normalize timezone and infinity values first.
jsonb, arrays, UUIDs, enums, ranges Short Text, Long Text, lookup table, or flattened fields Pick a storage policy that matches reporting needs.

PL/pgSQL objects and PostgreSQL security - out of scope

DBConvert's migration covers tables (with their fields, types, defaults, and indexes), views, and foreign keys. PL/pgSQL functions, triggers, rules, extensions, grants, and row-level security stay in the source - Access has no server-side execution layer, so that logic is reimplemented as Access queries and VBA, or left running against PostgreSQL.

Choosing the PostgreSQL → Access route

Most projects are either an Access reporting export, a recurring local copy, or a temporary compatibility bridge.

Route Where it fits Where it falls short
DBConvert / DBSync You need a GUI workflow, Access file output, filters, type mapping review, saved sessions, or recurring synchronization. PostgreSQL server-side code and Access application objects remain outside the row-copy workflow.
Access linked tables through ODBC Users only need to browse or report against live PostgreSQL data from Access. This is not a conversion; it depends on drivers, network access, permissions, and live PostgreSQL availability.
CSV export and Access import A few flat tables need to be moved once and relationships are not important. You lose schema metadata, constraints, type nuance, indexes, and repeatability unless you script them separately.
Custom ETL The Access file is only one output of a larger reporting or archival pipeline. You own driver setup, data shaping, Access size limits, retries, and validation.

Supported versions and services

PostgreSQL

  • PostgreSQL 8.x through 17.x
  • Amazon RDS / Aurora for PostgreSQL, Azure Database for PostgreSQL, Google Cloud SQL, Supabase
  • PostgreSQL schemas (public, custom schemas)

Access

  • MS Access .mdb (Jet) and .accdb (ACE) files
  • WorkGroups credentials and linked tables
PostgreSQL

All PostgreSQL Tools

Other directions and pairs
Access

All Access Tools

Migration & sync options

Reverse Conversion

Access to PostgreSQL

DBConvert Studio

30+ databases · cloud · scheduled sync

Need more directions or unattended sync? One tool covers them all.

How to migrate PostgreSQL to Access

When launching the DBConvert or DBSync application in GUI mode, it guides you through the steps to start database migration or synchronization:

1

Connect to PostgreSQL source database

Specify the username/password and host/port parameters if your source database requires login credentials.

Connect to PostgreSQL source database from DBConvert

PostgreSQL source

Read from self-hosted PostgreSQL, Amazon RDS / Aurora for PostgreSQL, Azure Database for PostgreSQL, or Google Cloud SQL.

2

Connect to Access destination database

Choose where the Access file goes. DBConvert creates it, or writes into the one you point at.

Connect to Access target database from DBConvert

Access target

Write a fresh .mdb or .accdb file. Microsoft caps the file at 2 GB; pre-filter the export if the source is larger.

Steps 3-6: the same for every database pair

Source and target are connected - steps 1 and 2 above. What follows is identical whichever two databases you picked, so it lives in one place. Each step below opens at its own section.

Open the full guide

All four steps in one page, plus software features, command-line mode, scheduler, and system requirements.

See all features

More guides for PostgreSQL ↔ Access