The database is the foundation of any Automic Automation environment. Performance, stability, and operating costs depend heavily on it. Many companies traditionally rely on Oracle —an established but license- and resource-intensive product.
In a recent project, setis GmbH helped a customer migrate the Automic database from Oracle to PostgreSQL —achieving several goals at once:
- Reduced costs
- Established cloud readiness
- Delivered on the company’s open-source strategy
Starting Point
The existing Oracle database incurred high license fees, required ever more powerful hardware, and drove up storage needs for backups. At the same time, the company had made a strategic decision to increase its use of open source.
Against this backdrop, setis advised the customer during the decision-making phase: Which alternatives are viable? What impact would a migration have on operations and costs? How can Automic be run in a future-proof way? The analysis led to a clear decision: PostgreSQL as the database platform.
Approach
Implementation followed a structured, multi-stage plan:
- Analysis of the existing Automic environment, dependencies, and data sets
- Migration concept including tools, timeline, and adjustments (e.g., monitoring, SQL scripts, permission model)
- Provisioning of new environments for test and production
- Test migration with validation of all functions
- Production migration in close coordination with the customer’s teams and service providers
- Decommissioning of the legacy environment and documentation updates
Outcome
The migration was seamless and did not interrupt any automation processes. The customer immediately benefited from:
- Elimination of Oracle licenses and a significant reduction in infrastructure costs
- Lower resource requirements with PostgreSQL, especially for storage and backups
- Cloud readiness and improved integration with modern platforms
- Strategic future-proofing through consistent execution of the open-source strategy
Success Factors
Key to success were:
- die Early involvement of setis in the decision-making process
- A thorough test migration to safeguard the production cutover
- sowie die Close collaboration among all stakeholders
This turned a technically demanding task into a smooth step toward modernization.
Conclusion
The migration of the Automic Automation database from Oracle to PostgreSQL shows how echnical modernization can align with strategic goals: lowering costs, reducing complexity, and paving the way for the cloud.
With extensive experience in automation projects, setis supports customers not only during implementation but also in decision and planning phases —ensuring migrations don’t just work, but deliver real value.
About the Author
Christian Böck is a Managing Consultant at setis and a Broadcom Certified Expert für Automic AutomationWith many years of experience in automation projects—particularly in banking and financial services—he supports customers with architecture, migrations, and operating complex environments. He also works as a trainer for Automic Automation and regularly conducts customer trainings.

