Migrating data from MS Access(.mdb; .accdb) to PostgreSQL

This guide walks you through migrating data from MS Access to PostgreSQL in a few simple steps using ESF Database Migration Toolkit. Simplify complex migration tasks and save valuable time with our streamlined approach.

MS Access vs. PostgreSQL:

Microsoft Access is a robust database management system (DBMS) that combines the relational Microsoft Jet Database Engine with a graphical user interface and software development tools. As part of the Microsoft Office suite, MS Access provides users with an easy-to-use platform for creating and managing databases, enabling efficient data entry, query execution, and report generation. It supports various data formats, allows integration with other Microsoft applications, and is ideal for small to medium-sized databases used in business and personal applications.
PostgreSQL is a powerful, open-source relational database management system known for its reliability, robust feature set, and extensibility. It offers support for a wide range of data types, indexing techniques, and advanced features such as full-text search, JSON support, and geospatial data processing. With a strong emphasis on standards compliance and ACID compliance, PostgreSQL is widely used across various industries for handling complex data management tasks, from small-scale projects to large-scale enterprise applications. Its active community, frequent updates, and ecosystem of extensions contribute to its popularity and ongoing development.

Prerequisite:

Software Required:

DMToolkit_x64.zip (63.5 MiB)	64-bit Windows application for ESF Database Migration Toolkit 12.2.07 (2025-07-01). (md5: 0750355677f7108916a6c1f2bc0d4d87)
DMToolkit_win32.zip (58.9 MiB)	32-bit Windows application for ESF Database Migration Toolkit 12.2.07 (2025-07-01). (md5: a9ba6351d787ff958b4ff2d9ca888576)

System Supported:
- Windows 7 or higher.
- MS Access 97 or higher.
- PostgreSQL 7.x or higher.

Step by Step Wizard:

Configure Microsoft Access Data Source
- In the "Choose a Data Source" dialog:
  - Select "Microsoft Access (*.mdb;*.accdb)"
- Browse for database file:
  - Click the "..." button
  - Select your .mdb or .accdb file
- Configure workgroup security (for system databases):
  - Click the lock icon
  - Set workgroup settings in the security dialog
Fig. 1: Microsoft Access data source configuration
Configure PostgreSQL Destination
- In the "Choose a Destination" dialog:
  - Select "PostgreSQL"
- Enter server connection details:
  - Server name: localhost (default)
  - Port: 5432 (default)
- Provide authentication credentials:
  - Username: postgres (default)
  - Associated password
- Configure character encoding:
  - Select database character set (default: UTF8)
  - Required for non-ASCII characters (e.g., German, French, Japanese)
- Database selection/creation:
  - Select existing database or enter new database name
  - Click the Refresh button to list available databases
  - New databases are automatically created during migration
- Schema configuration:
  - Enter or select target schema name (default: public)
  - Click the Refresh Schema button to list available schemas
Fig. 2: PostgreSQL destination configuration
In "Select Source Table(s) & View(s)" Dialog
- Select migration objects: Choose tables or views to include in the migration.
  
  Fig. 3: Select tables and views
- Modify table structure: Click the ellipsis (...) button to access table options and schema adjustments.
  
  Fig. 4: Do transform
- Configure field mapping: In the Field Mapping options:
  - Customize destination fields (name, data type, default value, comments)
  - Select data transfer method:
    - Overwrite Table (replace existing data)
    - Empty Data (truncate before insert)
    - Append Data (add to existing data)
    - Skip Table (exclude from transfer)
  - Apply data filters before transfer
Execution Dialog
- Start migration: Click "Submit" to initiate automated data transfer from MS Access to PostgreSQL.
  
  Fig. 5: Execute migration
- Monitor progress: Click "Browse Log" for real-time migration tracking, including issue resolution details.
- Save configuration: Click "Save as job" to store settings for:
  - Quick reloads of migration jobs
  - Command-line execution (use: dmtc.exe --help for parameter options)
Finished!

After migration completes, the toolkit generates a comprehensive report for verifying migration accuracy. You can monitor progress as the automated process runs efficiently. For any questions or feedback, contact us – our team is ready to assist.