The migration had to be completed without data loss and without putting existing functionality at risk.
At the same time, it was critical to preserve the existing SEO structure, URLs and proper WordPress functionality.
The new infrastructure also had to support the continued development of both projects without requiring another major architectural overhaul in the near future.
Delante’s DEV team designed and implemented a dedicated production environment for the Gratka and Morizon blogs.
The project included data migration as well as the full preparation, optimization and testing of the new infrastructure.
We implemented Docker-based environments, Nginx, automated backups, service monitoring, performance optimization, dedicated environments for each blog.
The objective was not simply to move two WordPress websites to another server.
Our task was to design and implement a complete production environment that would provide:
A key requirement was to create an infrastructure capable of supporting further project development without requiring another major architectural change.
Gratka and Morizon are among the best-known online classified platforms in Poland and belong to the Morizon-Gratka Group.
Morizon.pl is one of Poland’s major real estate platforms, while Gratka.pl has been operating in the online classifieds market for more than 20 years and is associated with categories including real estate, automotive and jobs. The blogs of both platforms are an important part of their content ecosystems. They support organic visibility, answer user questions and generate Search traffic.
Instead of moving the blogs to another standard hosting environment, we decided to design the infrastructure from the ground up.
This allowed us to migrate the existing applications while eliminating many limitations typical of traditional shared or standardized hosting environments.
The new environment was built around containerization and the full separation of individual infrastructure components.
Using Docker provided several operational advantages:
Each infrastructure component was deployed as a separate service, allowing individual parts of the environment to be managed independently.
We prepared a separate application environment for each blog.
This provided:
Databases were separated from the applications. The database migration was performed with full data-integrity verification.
This architecture provided:
The new environment was configured using Nginx. The server configuration included:
As a result, some requests can be handled without directly engaging WordPress and PHP.
One of the project’s main objectives was to increase infrastructure resilience and reduce the impact of potential failures.
The production migration was launched only after the test environment had been fully verified.
Stage 2Production MigrationThe blogs were then transferred to the new production environment. The migration was completed:
✓without data loss✓without service downtime
The Results
One of the primary project goals was to improve infrastructure performance.Monitoring conducted before and after the migration showed a significant improvement in server response time.
229 msBefore40 msAfter82%faster server response time
Importantly, the improvement was not temporary. Monitoring confirmed that the new performance levels remained stable during the following weeks of operation.
The new infrastructure also eliminated several potential points of failure typically associated with traditional hosting environments.
The biggest challenge in this project was combining a safe migration with a real performance improvement. The objective was broader than simply moving WordPress. We wanted to build an environment that would be stable, predictable and easier to maintain. That is why architecture, testing, backups, monitoring and rapid recovery capabilities played such an important role throughout the project.
The Gratka and Morizon migration shows that infrastructure is not merely the technical backend of a website.
For large content projects, it directly affects:
The blogs of both brands are important sources of organic traffic, so the new environment needed to provide more than faster response times. It also had to be easier to maintain, continuously monitored and ready to support further growth.
The client also gained greater control over backups, monitoring and environment recovery.
This is an example of a project where properly designed infrastructure became the foundation for the continued development and stable operation of business-critical content platforms.
Planning a WordPress Migration?
Move your website to a faster, more stable environment without compromising data, functionality or future scalability.
