AccuWeb.Cloud migrated Xaddwell’s independent client hosting environments from Jelastic to CloudStack, preserving separate databases, backup destinations, NGINX routing, DNS, and SSL configurations for each client.
Our cloud migration engineers rebuilt NGINX upstreams, corrected Jelastic-specific internal references, verified backup writes on the new storage, and completed each cutover sequentially with post-migration DNS and SSL validation.
Xaddwell’s client environments had been built independently on Jelastic, each with its own database, backup destination, NGINX configuration, domain, DNS, and SSL setup. That meant each environment had to be treated as a separate migration rather than assuming one configuration could be reused for the other.
The main technical risk was hidden environment-specific configuration. Some NGINX upstreams and backup settings still referenced Jelastic-internal addresses, which would stop working once the old platform was decommissioned.
Our migration team therefore had to identify and replace those dependencies, rebuild the required routing and backup configurations, and validate each environment individually before completing the move to CloudStack.
Xaddwell’s client environments contained Jelastic-specific internal references that would have failed once the old platform was switched off. In one case, the NGINX upstream still pointed to a Jelastic-internal application address; in another, the backup configuration referenced the old destination.
Migrating reseller-hosted client environments requires more than moving files and databases. Each environment had to be treated independently, with its own application routing, backup targets, DNS, and SSL settings validated before cutover.
Each client kept its own database instance, backup destination, and NGINX configuration on the new infrastructure. Instead of consolidating the setups, our engineers preserved the original separation so each environment could be migrated, tested, and validated independently.
NGINX server blocks, proxy_pass targets, upstream definitions, and SSL certificate paths were rebuilt for the new environment. During this process, our team identified Jelastic-specific internal references that would no longer work after the old platform was decommissioned and replaced them with the correct CloudStack endpoints.
# before — Jelastic internal address
upstream app_backend {
server app-env-xxxxx.jelastic.example-region.net:8080;
}
# after — new application endpoint
upstream app_backend {
server 10.20.x.x:8080;
}Each backup configuration was updated to point to the new storage destination. Rather than relying only on a successful job status, our engineers triggered a manual backup and confirmed that the expected file was actually created on the new target with the correct filename, size, and timestamp before retiring the old backup destination.
The first client environment was fully migrated and validated before work began on the next. Application functionality, backups, DNS, and SSL were checked after each migration. This allowed any issue discovered during the first move to be resolved before the same process was applied again.
After each migration, our engineers confirmed that the domain resolved to the new server, checked for subdomains still pointing to the old Jelastic environment, and validated the SSL certificate chain on the new infrastructure. This post-cutover verification confirmed that the new environment—not just the old one—was configured correctly and ready for production traffic.
Xaddwell’s client hosting environments were successfully migrated from Jelastic to CloudStack while preserving their separate application, backup, DNS, and SSL configurations.
Each environment was migrated and validated independently. Backup jobs were confirmed on the new storage, NGINX upstream references were corrected, and DNS and SSL were checked after cutover before the migration was considered complete.
"We needed each client environment to be migrated carefully without affecting the other. AccuWeb.Cloud handled the transition in a structured way, verified the backups on the new infrastructure, and checked the DNS, SSL, and application configuration after each migration. The process was smooth, well coordinated, and gave us confidence that each client setup was working correctly before the old environment was retired."
Please ask your queries. We are available 24/7
We migrate complete hosting environments—including application routing, backups, DNS, SSL, and server configurations—with careful validation before the old infrastructure is retired.