AccuWeb.Cloud migrated Mavalan Software’s PostgreSQL, Java, and NGINX application stack from Jelastic to CloudStack while maintaining uninterrupted application availability.
Our cloud engineers migrated and validated the PostgreSQL database, rebuilt JDBC connectivity and NGINX routing, planned the DNS cutover around Mavalan’s Spain-based users, and load-tested the database connection pool on the new cloud infrastructure before completing the migration.
Mavalan’s environment was built across three separate layers: a PostgreSQL database, a Java application engine, and an NGINX reverse-proxy node. Each layer had its own migration requirements, and the entire stack had to be rebuilt in the correct sequence for the application to function properly on CloudStack.
The migration required a logical PostgreSQL dump and restore, validation of schema and row counts, reconfiguration of JDBC connection strings, and reconstruction of the NGINX reverse-proxy setup. Any mismatch between these layers could have caused database connectivity issues, routing failures, or application downtime during cutover.
Because Mavalan’s users are primarily based in Spain, the DNS cutover was also carefully timed to minimize disruption during active usage hours and ensure a smooth transition to the new cloud environment.
Mavalan’s Java application was still using Jelastic-internal JDBC addressing instead of a portable database endpoint. That kind of environment-specific dependency can easily break after migration if it is not identified before cutover.
Our cloud migration team has encountered similar stale internal references in other Jelastic-to-CloudStack migrations, including Synergistic Technologies, Reliva, Bharat Property, and Akilanews. In Mavalan’s case, the issue was inside the Java application configuration rather than the web-server layer.
That is why our migration process checks application configuration, database connections, reverse-proxy settings, and internal service references across the full stack before the final cutover.
Migrating a live three-tier application environment without downtime requires careful sequencing, validation, and application-level testing. Here is how our cloud engineering team migrated Mavalan’s PostgreSQL, Java, and NGINX stack from Jelastic to CloudStack.
The PostgreSQL database was migrated using a full logical dump and restore. Before the Java application was connected to the new database server, our engineers validated the schema and row counts against the source database.
This ensured the migrated PostgreSQL environment was complete before any new application writes were directed to it.
pg_dump -Fc --dbname=mavalan_prod --file=mavalan_prod.dump pg_restore --dbname=mavalan_prod --verbose mavalan_prod.dump
The Java application was still using JDBC connection details tied to the original Jelastic environment. Our engineers updated the JDBC connection strings and related environment variables to point to the new CloudStack PostgreSQL endpoint.
This removed the Jelastic-specific dependency before final cutover.
# before — Jelastic-internal jdbc:postgresql://db-env-xxxxx.jelastic.example-region.net:5432/mavalan_prod # after — CloudStack database endpoint jdbc:postgresql://10.30.x.x:5432/mavalan_prod
NGINX was rebuilt on the new cloud infrastructure as the reverse proxy in front of the Java application.
The existing routing and header-forwarding behavior—including headers used by the Java application to identify the original client and protocol—was recreated and verified rather than simply copying the old configuration and assuming it would work unchanged.
Because Mavalan’s users are primarily based in Spain, the DNS cutover was scheduled to reduce the impact of DNS propagation during active usage periods.
This helped move users to the new CloudStack environment in a controlled manner while minimizing the risk of application disruption during the transition.
After the migration, our engineers load-tested the Java application’s PostgreSQL connection pool under realistic usage patterns.
This was important because an application can start successfully while still experiencing database connection exhaustion or timeouts under heavier traffic. Load testing confirmed that the application and database connectivity remained stable on the new CloudStack infrastructure before the migration was considered complete.
Mavalan Software’s complete PostgreSQL, Java, and NGINX environment was successfully migrated from Jelastic to CloudStack with zero application downtime.
Our cloud engineering team validated each layer independently — database, application, JDBC connectivity, and NGINX reverse proxy — before final cutover. The PostgreSQL connection pool was also load-tested after migration to confirm stable performance under the new infrastructure.
The result was a controlled cloud migration with no service interruption, verified database integrity, and stable application connectivity.
“Migrating our PostgreSQL, Java, and NGINX environment required careful planning and coordination. The AccuWeb.Cloud team handled the migration smoothly, kept our application available throughout the cutover, and thoroughly validated the new environment before it went live. The entire transition was well managed and gave us confidence at every stage.”
Please ask your queries. We are available 24/7
Our cloud migration experts carefully plan the cutover, validate every layer of your application stack, and test database, application, and proxy connectivity before the new environment goes live.
