Migrate your website to LJPc: step-by-step guide
Published on July 4, 2026 14 min read
Migrate your website to LJPc with no downtime. Move your files, database and DNS step by step with this complete guide for a smooth switch.
Do you want to migrate your website to LJPc and handle the move yourself, while your site stays online the whole time? This guide walks you through how to migrate an existing website step by step: your files, your database, your DNS and what happens to your email. We cover the manual method with an FTP client and phpMyAdmin, and for WordPress we point you to the faster method with a migration plugin. The goal throughout is a switch with no downtime, so your visitors never notice the move.
What does migrating your website mean?
Migrating your website means copying the contents of your site from your current hosting provider to the servers of LJPc. For most sites that involves three parts: the files (the website itself), the database (where a system such as WordPress stores your text and settings) and the DNS (which decides where your domain points).
Note that migrating your website is not the same as transferring your domain name. A domain transfer moves the registration of your domain to another party. If you want to do that as well, read how to transfer your domain to LJPc. This article is all about your website: the files, the database and the DNS change that brings your visitors across.
LJPc provides hosting based on Plesk. That is the control panel where you manage your files, databases and certificates. If your current host uses cPanel, the article what is Plesk? explains what is different. You open Plesk with a single click from the customer portal, so you do not need a separate password. Read how in opening Plesk from the customer portal.
Before you start: what you need
Make sure you have the following to hand before you begin migrating:
- An active hosting plan with LJPc, so that you have access to Plesk.
- The FTP or SFTP login details for your current host.
- Access to the database of your old site, usually through phpMyAdmin.
- Access to the DNS management of your domain at your current provider, so you can change the nameservers or records later on.
- A recent backup of your files and your database, to be safe.
- An FTP client such as FileZilla, or you can use the built-in file manager in Plesk.
A useful bit of preparation: lower the TTL of your DNS at your current provider a day or two in advance, to 300 or 3600 seconds for example. The TTL sets how long internet providers remember a DNS answer. A low TTL means your later DNS change is picked up more quickly.
Migrate your website to LJPc: step by step
The steps below work for almost any website with files and a database, such as WordPress, Joomla or a custom-built site. If you run a WordPress site and want to finish sooner, also read migrating WordPress with a plugin.
Step 1. Order your hosting plan with LJPc
Choose a hosting plan that suits the size of your site and order it on the order page in the customer portal. For your domain, choose I already have one at another registrar, enter your domain name and choose Keep domain elsewhere, connect hosting here. Then pick your hosting plan and complete your order.
After you order, the portal sets up your hosting plan automatically; if you pay in advance, that happens as soon as your payment comes in. On the page of your order you follow the progress and see which nameservers you will set later. You do not need to change your DNS yet: you first build up your site calmly on the new server and move your visitors across later.
Moving your domain to LJPc too? Order your plan this way all the same and transfer the domain last, once your website and email are ready with us. How that works is explained in moving your domain, website and email in one go.
Step 2. Download the files from your old host
Connect to your current host and download all of your website files to your computer. You usually do this using FTP or SFTP with a program such as FileZilla. Choose SFTP if your host supports it, because the traffic is then encrypted over a secure connection.
Download everything from the web folder of your old host. It is often called public_html, httpdocs or www. For WordPress that also includes the folders wp-content, wp-admin and wp-includes, plus separate files such as wp-config.php and the hidden file .htaccess. Make sure hidden files are visible in your FTP client, otherwise you will miss them.
Step 3. Export the database
If your site uses a database, you export it separately. Log in to the control panel of your old host and open phpMyAdmin.
- Select the database that belongs to your site on the left.
- Click the Export tab at the top.
- Choose the Quick export method and the SQL format.
- Click Go and save the
.sqlfile on your computer.
If you have a static site with no database, only HTML files for instance, you can skip this step.
Step 4. Upload the files to Plesk
Open Plesk from the customer portal and click Files in the menu on the left. That is the Plesk file manager (File Manager). Open the httpdocs folder there. That is the web folder your site is served from.
The quickest approach is to upload a ZIP file. Compress your files into a ZIP on your computer, upload it to httpdocs and then choose Extract Files to unpack it. You can also copy the files to your LJPc space with an FTP client: over FTPS with your username and password, or over SFTP if you use a fixed IP address and an SSH key. Read how to set that up in uploading files with FTP, FTPS and SFTP. Check that your files sit directly in httpdocs and not in an extra subfolder.
A new httpdocs already contains an index.html file with a default page. If your site uses an index.php, as WordPress and Joomla do, delete that index.html. The server picks index.html first, so otherwise you see the default page instead of your site.
Step 5. Import the database into Plesk
First create an empty database on your new hosting. In Plesk, click Databases in the menu on the left, choose Add Database and create a database user with it straight away. Note down the database name, the username and the password, because you will need them in a moment. You will find more help in creating a database in Plesk.
- Go to Databases in Plesk.
- Choose Import Dump for your new database and upload your
.sqlfile, or open phpMyAdmin and use the Import tab there. - Wait for the import to finish and check that your tables are present.
Step 6. Update the configuration file
Your site needs to know where the new database is and which details it may use to log in. In WordPress you update the file wp-config.php for this. Open it in the Plesk file manager and set these values to the new details from step 5:
DB_NAME: the name of your new database.DB_USER: the new database user.DB_PASSWORD: the password for that user.DB_HOST: almost alwayslocalhost.
If you use another system, it has a similar file, such as configuration.php in Joomla. Because your domain name stays the same, you do not need to change the website URL.
Step 7. Test your site before you change the DNS
This is the most important step for a switch with no downtime. Test your site on the LJPc server while your old site is still online for everyone. That way you spot mistakes before your visitors do.
The most reliable method is the hosts trick: make your own computer point your domain to the IP address of your LJPc hosting temporarily, by adding a line to your hosts file, for example 203.0.113.10 yourdomain.com www.yourdomain.com. You find the IP address in Plesk in the DNS check of your domain, in the Expected column. Only you then see the new server, while the rest of the world still sees the old one. Go through your pages, images, forms and the database connection, and fix any problems now. Remove the line again when you have finished testing. How to edit the hosts file on Windows, macOS and Linux and what to test is explained in testing your website before changing DNS.
Your certificate only arrives after the DNS change (step 10). So if your browser shows a certificate warning during this test, that is normal.
Step 8. Prepare your email and your other DNS records
If you choose the LJPc nameservers in step 9, not only your website moves, but also your email and the rest of your DNS. Your domain then uses the DNS zone of your hosting plan in Plesk, with the LJPc mail servers (mx1.ljpc.email and mx2.ljpc.email). So get everything ready before the switch:
- Your email moves to LJPc. Create your mailboxes first, for example in the customer portal (see creating an email address in the customer portal), and move your messages across. If you see the Migrate email button for your site in the portal, you move your mailboxes with it for free. If you work with a sub-account and do not see the button, ask your main account for the Migrate email permission under Sub-accounts. You can also move your email yourself over IMAP, as described in migrating email to a new server.
- Your email stays with another provider, such as Microsoft 365 or Google Workspace. Then add that provider's MX records to the DNS of your domain in Plesk, and add their SPF entry to the SPF record that is already there, so you keep a single SPF record. Read how to change records in managing DNS records.
- Other records. Also copy the records you still have at your current DNS provider, such as subdomains or TXT records you used to verify a service.
- DNSSEC. If DNSSEC is on at your current DNS provider, have the DS record removed there first and wait for the TTL to pass before you change the nameservers. Read why in what is DNSSEC.
If you choose the route with only the A records in step 9, your email and your other DNS stay where they are. Does your website send email on behalf of your domain, such as a contact form or order confirmations? Then add include:_spf.ljpc.network to the SPF record of your domain. With that entry, our mail server sends email on behalf of your domain.
Step 9. Change your DNS to LJPc
Once the site works on the new server and your email and DNS records are ready, you point your domain to LJPc. You have two options.
- Nameservers: at the party where your domain is registered, set the nameservers (NS records) of your domain to
ns1.ljpc.network,ns2.ljpc.networkandns3.ljpc.network. This is the route the portal shows you with your order. LJPc then manages your DNS and points your website and your email to your hosting plan automatically. The step-by-step guide is in changing your nameservers. Transferring your domain to LJPc? Then the transfer takes care of this: once it completes, the nameservers point to LJPc automatically. - The A records only: keep your current DNS management and point the A record of your domain and of
wwwto the IP address of your LJPc hosting. If your domain also has an AAAA record (IPv6) pointing to your old host, change it to the IPv6 address of your site, which you also see in Plesk, or remove it. Changing only the A records is more targeted and often quicker.
A DNS change is not visible everywhere at once. It takes time to propagate, usually a few hours up to a maximum of 48 hours, depending on your TTL. Keep your old hosting active during that time, so that visitors see a working site through both the old and the new address.
Step 10. Check your SSL certificate
As soon as your domain points to the LJPc server, LJPc requests a free Let's Encrypt certificate for you automatically. We check this every fifteen minutes, so the certificate follows shortly after your DNS change becomes visible. So you do not have to request the certificate yourself. The certificate also covers the www version of your domain and is renewed automatically before it expires.
For the certificate, your domain and www must already point to your LJPc hosting, with the A record and, if you have one, the AAAA record. Any CAA record must allow letsencrypt.org; with the LJPc nameservers this is already set correctly. You can see the status in Plesk under SSL/TLS Certificates. After that, check that your site loads over https:// with a valid padlock. If you see a warning about insecure content, read fixing mixed content and HTTPS errors. Still no certificate after a few hours? Then contact support.
Migrating WordPress with a plugin
If you run a WordPress site, you can migrate the files and database in one go with a migration plugin such as Duplicator or All-in-One WP Migration. That saves you the manual work with FTP and phpMyAdmin. Read how to go about it in migrating WordPress with a plugin.
Because your domain name stays the same, these plugins do not need to rewrite any addresses. After that you still prepare your email as in step 8 and change your DNS as in step 9, and the SSL certificate follows automatically as in step 10.
Migrating with no downtime: the key tips
- Lower the TTL of your DNS 24 to 48 hours in advance, so the change comes through quickly later.
- Set everything up on the new server and test your site first, before you change the DNS.
- Create your mailboxes and prepare your DNS records before you change the nameservers.
- Keep your old hosting active for at least 24 to 48 hours after the DNS change.
- Choose a quiet moment for the switch, in the evening or at the weekend for example.
- Only cancel your old hosting once the new site works for everyone and your email arrives in its new place.
Common mistakes and how to fix them
| Problem | Cause | Solution |
|---|---|---|
| Error about the database connection | wp-config.php still points to the old database details | Set DB_NAME, DB_USER, DB_PASSWORD and DB_HOST to the new values from Plesk. |
| You see a default page instead of your site | The default index.html file is still in httpdocs | Delete index.html if your site runs on index.php. |
| The old site still appears | The DNS has not propagated yet | Wait until the TTL has expired and check with a propagation checker. Keep your old host active. |
| No padlock, no valid SSL | Your domain or www does not point to LJPc everywhere yet, or an AAAA record still points to your old host | Make sure the A records (and any AAAA record) of your domain and of www point to LJPc. After that, LJPc requests a certificate automatically. |
| Images or pages are missing | Not all files uploaded, or in the wrong folder | Check that all files sit in httpdocs, including hidden files such as .htaccess. |
| Email no longer arrives | Your nameservers point to LJPc, but your mailboxes do not exist here yet, or the MX records of your own mail provider are missing from the DNS in Plesk | Create your mailboxes in the customer portal, or add the MX records of your mail provider to the DNS of your domain in Plesk (step 8). |
| Email from your website does not arrive | Your SPF record is missing include:_spf.ljpc.network, or your email is with another provider while your domain also has a mail service on our server, so email from your site to your own addresses stays on our server | Add include:_spf.ljpc.network to your SPF record. If email to your own addresses still does not arrive, contact support. |
Would you rather not migrate your website yourself? LJPc helps you with the migration for free and moves your site across with no downtime. Send us the login details for your current host through a one-time link, as described in our guide on sharing passwords securely. Stuck somewhere during the move? Contact support at support@ljpc.nl or 085 130 6429, and we will think along with you.
Frequently asked questions
Will my website go offline during the migration?
No, not if you keep to the right order. Move your files and database first, test everything, and only change your DNS after that. Keep your old hosting active for another 24 to 48 hours. That way your site stays reachable the whole time.
How long before the migration is visible?
The move itself is often done within an hour. The DNS change then needs time to propagate, usually a few hours up to a maximum of 48 hours, depending on your TTL.
Do I have to transfer my domain name as well?
No, you do not. You can migrate your website to LJPc and leave your domain name with your current registrar. You then only adjust the DNS. If you want to move your domain too, that is a separate step. If you move your domain, website and email together, transfer the domain last, once your website and email are ready with us.
What happens to my email when I migrate my website?
That depends on how you point your domain to LJPc. If you change the nameservers, your email moves to LJPc too: so create your mailboxes first and move your messages across, or add the MX records of your current mail provider to the DNS of your domain in Plesk. If you only change the A records, your email stays where it is.
Do I have to request the SSL certificate myself?
No. As soon as your domain and its www version point to the LJPc server, LJPc requests a free Let's Encrypt certificate automatically. You check the status in Plesk.
Can LJPc do the migration for me?
Yes. LJPc offers free migration help and can move your website across with no downtime. If you would rather not do this yourself, get in touch with support.