Migrating data from InterSystems Cache to PostgreSQL
This guide walks you through migrating data from InterSystems Cache to PostgreSQL in a few simple steps using ESF Database Migration Toolkit. Simplify complex migration tasks and save valuable time with our streamlined approach.
InterSystems Cache vs. PostgreSQL:
InterSystems Cache is a high-performance object database management system and rapid application development environment designed for transactional applications. It offers a powerful database engine coupled with a robust set of development tools, making it suitable for building scalable, data-intensive applications in healthcare, finance, and other industries. Cache excels in handling complex data structures and large volumes of data while providing real-time analytics and seamless integration capabilities. Its advanced features include support for SQL, object-oriented programming, web services, and interoperability with various programming languages, making it a versatile solution for modern application development needs.
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.
32-bit Windows application for ESF Database Migration Toolkit 12.2.08 (2025-07-11). (md5: bd34cb7f73c88c6d0c7a44069ad756d6)
System Supported:
Windows 7 or higher.
InterSystems Cache 2015.1 or higher.
PostgreSQL 7.x or higher.
Step by Step Wizard:
Connect to InterSystems Cache
In the "Choose a Data Source" dialog:
Select "InterSystems Cache"
Enter connection parameters:
Server name: localhost (default)
Port number: 1972 (default)
Provide authentication:
Username: _system (default)
Password associated with the account
Load database options:
Click the Refresh Database button
Select target database from the list
Load schema options:
Click the Refresh Schema button
Choose desired schema
Fig. 1: InterSystems Cache 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 InterSystems Cache 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.