Skip to content
BestCoding
pl

Move your PrestaShop store to a new server

We move your PrestaShop store to new hosting, a VPS, or a dedicated server with pre-cutover testing, an agreed data-sync and cutover window, and a tested rollback plan. The work covers the database, files, images, configuration, cron jobs, and key integrations. We plan the migration to minimize downtime and protect orders around the cutover.

Ask about store migration
PrestaShop Expert

The problem

Migrating PrestaShop involves more than copying files and importing a database. The store also depends on PHP, server configuration, permissions, cache, cron jobs, transactional email, SSL certificate provisioning and HTTPS verification, plus modules and integrations. We identify these dependencies before work starts and check the following risks on the new server:

  • Unplanned downtime — without a cutover plan, DNS preparation and a rollback scenario, the store can be unavailable longer than necessary
  • Broken URLs, HTTPS or redirects — changing servers can cause certificate errors, mixed content, an incorrect store URL or lost redirects
  • Configuration and permission errors — differences in PHP, the web server, environment variables, file ownership or write permissions can block cache, uploads and modules
  • Database issues — incompatible encoding, collation, MySQL versions or an unchecked import can corrupt data or affect queries
  • Missing media and store files — omitted product images, upload directories or module files can cause missing photos and page errors
  • Stopped external processes — cron jobs, transactional email, payments, couriers, feeds or syncs can fail if their configuration is not checked
  • Orders and performance after cutover — orders placed during the change need a synchronization plan, and an unsuitable PHP, MySQL or web-server setup can slow the store
Old server serving traffic New server preparation Testing Cutover Rollback
The new server is prepared and tested in parallel with the live store. Traffic switches in one agreed window, with a rollback path back to the old server.

When you should consider this

  • Your current hosting is overloaded or too slow, or its limits make store development harder
  • You are moving the store from shared hosting to a VPS or changing provider because the current service is ending or no longer meets your needs
  • Your current host limits the PHP version, memory, process configuration or administrative access needed to maintain the store safely
  • You want to put optional Cloudflare in front of the store and need to assess whether its CDN and cache suit the specific configuration
  • You are consolidating several stores or services in one environment and want to organize their dependencies and maintenance approach
  • You are preparing the store for a campaign, a season or growth, and want a stable infrastructure base first
  • You need one person who understands both PrestaShop and the server, database, DNS and store integrations

Scope of work

  • Migration audit and plan: reviewing the PrestaShop version, modules, integrations, database, files, configuration, cron jobs, email, DNS and dependencies, with the work sequence and cutover data plan
  • Environment choice: an optional VPS or hosting recommendation suited to the store, or work on the server you have chosen — we do not require a particular provider
  • New server preparation: configuring PHP, MySQL and the web server for the specific PrestaShop store, creating a stable foundation for later optimization
  • Store data migration: moving and verifying the database, code, modules, configuration, product images, uploads and other files required to run PrestaShop
  • Pre-cutover testing: checking the storefront, back office, purchase path, transactional email, cron jobs, key integrations, URLs and redirects, plus SSL certificate provisioning and HTTPS verification
  • Optional Cloudflare: configuring CDN and cache in front of the store when justified by the environment; the related Cloudflare for PrestaShop article explains its benefits and limits
  • Post-migration upkeep: scheduled backups with a test restore path and monitoring for availability, errors, resources and cron jobs

What you get

  • A migration plan with dependencies, work sequence, test scope, cutover approach and rollback conditions
  • A prepared new-server environment, with PHP, MySQL and web-server configuration matched to the agreed store requirements
  • A migrated and verified database, store files, images, modules and configuration required to start PrestaShop
  • A list of pre-cutover tests carried out, covering the store's key paths and any limitations found
  • Configured backups and a confirmed test restore path, where supported by the target environment
  • A post-migration summary: work completed, monitoring set up and further optimization recommendations

What we can do at the same time

Store file and database cleanup

Removing orphaned images, unused modules and themes, old logs, and unnecessary or obsolete database data (carts, guest data, logs) — always after a backup.

Offsite backups

Setting up regular backups sent off the store server, with a tested restore path so the copy actually protects your data.

Clean VPS or dedicated server

Setting up the environment from scratch — OS, PHP, MySQL, web server and security basics — tuned for PrestaShop.

Server management panel

Optional installation of a control panel when operational requirements justify it. In managed or automated environments, we may recommend a panel-free stack.

Cloudflare in front of the store

An optional CDN and cache, configured correctly for dynamic pages, the cart and checkout, plus tidying up DNS.

PHP/MySQL update and caching

Moving to a supported PHP and MySQL version and configuring OPcache and application cache, where the store and modules are compatible.

HTTPS, email and security

HTTPS enforcement and redirects, plus verification of transactional email delivery through the existing or newly configured SMTP/API provider. This includes DNS authentication such as SPF, DKIM and, where applicable, DMARC, reverse DNS when mail leaves the server directly, and test messages, alongside basic server and permission hardening.

A base for performance optimization

A correctly configured environment as a starting point for later measuring and removing the real bottlenecks.

How the process works

  1. 1

    Migration audit and plan

    We identify the required access and migration scope across the store, hosting, domain, database, modules, integrations and scheduled tasks. We agree the risks, cutover method and, if needed, a VPS or hosting recommendation without requiring a specific provider.

  2. 2

    Preparing the new server

    We configure PHP, MySQL and the web server for the store, then prepare access, SSL certificate provisioning and HTTPS verification, DNS and backup storage. The result is a stable foundation for later optimization, not a promise of a specific performance outcome.

  3. 3

    Migration and pre-cutover testing

    We move the database, files, media, modules and configuration, then test the store before sending regular traffic to the new server. We check the purchase path, transactional email, cron jobs, key integrations, URLs and redirects, plus SSL certificate provisioning and HTTPS verification.

  4. 4

    Low-downtime cutover

    In the agreed window, we complete the final data synchronization, switch traffic and check the store. A tested rollback plan is ready if a material problem occurs.

  5. 5

    After migration: upkeep and next steps

    We set up or verify backups and monitoring for availability, errors, resources and cron jobs, then identify possible next optimization steps.

Why this works

Migrating a store calls for combined knowledge of PrestaShop, PHP, MySQL, Linux, server configuration, DNS and, optionally, Cloudflare. We take one integrated view, checking how modules, the database, media, cron jobs and integrations operate with the new environment. This avoids gaps between the developer and hosting provider.

Conditions for a reliable result

The cutover window depends on the store size, database write activity, integrations, the final synchronization method, and the DNS TTL configured before cutover. We therefore do not promise “zero downtime” or a fixed number of minutes. We test the store on the new server before directing traffic to it and prepare a tested rollback plan for the agreed cutover. A reliable migration needs access to the old and new servers, the database and DNS configuration; the test scope depends on the available data and environment. We can recommend an environment or work with the provider you have chosen — we do not require a particular host.

Related services

PrestaShop performance optimization

Once the environment has a clean, correctly configured base, we can measure and optimize the store's actual bottlenecks.

PrestaShop store maintenance

After migration, ongoing care helps keep updates, monitoring, backups and subsequent changes in an organized process.

Backups and restore

A backup is useful when it covers the data you need and a tested route exists to restore it.

Monitoring and alerts

Availability, error, resource and scheduled-task monitoring helps observe the new environment after migration.

Related articles

Frequently Asked Questions

Does a PrestaShop migration require downtime?

The cutover needs a controlled work window. Its length depends on store size, database write activity, integrations, the final synchronization method, and the DNS TTL set before cutover. We test the store, plan the synchronization and prepare rollback; zero downtime cannot be promised before reviewing the environment.

Will URLs, SSL and redirects work after migration?

We verify the store URL, required redirects and HTTPS before and after cutover. This includes SSL certificate provisioning and HTTPS verification, usually by issuing a certificate for the target server, rather than assuming it will transfer automatically.

Will I lose orders placed during the cutover?

The migration plan covers changing data, including orders. We agree the final synchronization point, check its result and keep rollback available if a material issue occurs.

Can you recommend a server or hosting provider?

Yes. After the audit, we can recommend a VPS or hosting suited to the store requirements, traffic, integrations and administrative needs. We can also migrate to a server you have selected. We do not require a particular provider.

Do you configure Cloudflare in front of the store?

Yes, when it makes sense for the specific store. Cloudflare is an optional CDN and cache layer that needs correct configuration for dynamic pages, cart and checkout. It does not replace server tuning, module control or monitoring; the related article covers the details.

Do you configure backups and test restores?

We can set a backup schedule and confirm a test restore path in the new environment, where supported by the target environment.

Which PrestaShop versions can you migrate?

We assess migration feasibility from the PrestaShop, PHP and MySQL versions, as well as modules, customizations and integrations. An older store does not rule out migration, but it may need extra tests or a staged change plan when the new environment does not match its requirements.

Can you optimize performance after migration too?

Yes. We first establish a stable PHP, MySQL and web-server base and confirm the store works after migration. Later optimization starts with measurement and a diagnosis of specific bottlenecks, rather than assuming the server change alone produced an outcome.

Let’s plan your store migration

Send the store URL, PrestaShop version, and details of the current and target hosting or server. Also tell us whether the store uses important integrations, cron jobs, Cloudflare or custom modules. From that, we will identify the required access and migration scope, then decide where to start.

Ask about store migration Get in touch: contact@bestcoding.net