ArclineIT/docs
1
0
Fork 0
Code Issues 40 Pull Requests Actions Packages Projects Releases Wiki Activity

DOCS-1: Init document work

Browse Source
This commit is contained in:
Blake Ridgway
2026-07-28 07:20:32 -05:00
parent 8f02a3fc8e
commit 0cbcc962f7
66 changed files with 12224 additions and 71 deletions
Download Patch File Download Diff File Expand all files Collapse all files

184
content/migrate/from-bluehost.md Normal file
View File

@@ -0,0 +1,184 @@
---
title: "Migrate from Bluehost"
description: "How to move your website and email from Bluehost to Arcline, including WordPress sites and cPanel-to-cPanel transfers."
section: migrate
order: 2
---
# Migrate from Bluehost
Bluehost runs cPanel on its shared hosting plans, which makes migrating to Arcline straightforward — both platforms speak the same language. The process is: export from Bluehost, set up on Arcline, test, then switch nameservers.
---
## Before you start
- Bluehost cPanel access (log in at your Bluehost dashboard → **Advanced** to reach cPanel)
- Arcline cPanel account
- 30–90 minutes depending on database and file size
- Note your Bluehost PHP version: cPanel → **Software → Select PHP Version**
---
## Step 1 — Back up files from Bluehost
### Full cPanel backup
1. Bluehost cPanel → **Files → Backup** (or search for "Backup Wizard")
2. Choose **Full Backup** and download to your local machine
This gives you an archive with `public_html` and all databases.
### Manual file backup via SFTP
If you only want specific files, connect to Bluehost via SFTP:
- Host: `ftp.yourdomain.com` or your server hostname
- Port: `21` (FTP) or `22` (SFTP) — use SFTP if available
- Username/password: your cPanel credentials
Download `/home/username/public_html/` to your local machine.
---
## Step 2 — Export your database from Bluehost
1. Bluehost cPanel → **Databases → phpMyAdmin**
2. Click your database name in the left sidebar
3. Click **Export → Quick → SQL → Go**
For large databases, use **Custom** export and enable **Add DROP TABLE**. You can also export via SSH:
```bash
mysqldump -u cpanelusername_dbuser -p cpanelusername_dbname > bluehost_backup.sql
```
---
## Step 3 — Set up on Arcline
**Create the database:**
1. Arcline cPanel → **Databases → MySQL Databases**
2. Create a database and a database user
3. Assign the user to the database with **All Privileges**
**Import the database:**
1. cPanel → phpMyAdmin → select your new database → **Import**
2. Upload the `.sql` file from Bluehost
3. Click **Go**
For files over 50 MB, use the command line (see [Back Up and Restore a MySQL Database](/getting-started/mysql-backup/)).
**Upload your files:**
Connect to Arcline via SFTP and upload your site to `/home/username/public_html/`. See [Upload Files via SFTP](/getting-started/sftp/).
---
## Step 4 — Update wp-config.php
WordPress stores database credentials in `wp-config.php`. Update the values to match the new database you created:
```php
define( 'DB_NAME', 'newcpanel_dbname' );
define( 'DB_USER', 'newcpanel_dbuser' );
define( 'DB_PASSWORD', 'your-password' );
define( 'DB_HOST', 'localhost' );
```
Bluehost sometimes uses a custom `DB_HOST` value. On Arcline it is always `localhost`.
---
## Step 5 — Match the PHP version
Bluehost's default PHP version may differ from Arcline's. To prevent compatibility errors:
1. Check the PHP version in Bluehost cPanel → **Software → Select PHP Version**
2. Set the same version in Arcline cPanel → **Software → Select PHP Version**
3. Also check that any PHP extensions your site requires are enabled on Arcline (the **Extensions** tab in MultiPHP Manager)
WordPress 6.x requires PHP 7.4 minimum; PHP 8.1 or 8.2 is recommended.
---
## Step 6 — Test the site before switching DNS
Edit your local `hosts` file to preview the Arcline version without changing DNS.
Find your Arcline server IP in cPanel → **Server Information**.
Add this line to your hosts file:
```
YOUR_ARCLINE_IP yourdomain.com www.yourdomain.com
```
**macOS / Linux:** `/etc/hosts` (requires sudo)
**Windows:** `C:\Windows\System32\drivers\etc\hosts` (open as Administrator)
Visit your domain in a browser and verify:
- Pages and images load
- WordPress admin works
- Forms and any dynamic features work
- SSL is active (AutoSSL issues a cert after DNS resolves, which it will once nameservers switch — for pre-launch testing self-signed is normal)
Remove the hosts entry once done.
---
## Step 7 — Switch nameservers
When the site checks out, update nameservers to Arcline. Bluehost is often both the host and the registrar.
**If your domain is registered at Bluehost:**
1. Log in to Bluehost → **Domains → My Domains**
2. Click **Manage** → **Nameservers** → select **Custom Nameservers**
3. Enter:
- `ns1.arcline.it`
- `ns2.arcline.it`
4. Save
**If your domain is registered elsewhere**, update nameservers at that registrar instead. See [Point Your Domain to Arcline](/getting-started/nameservers/).
Keep Bluehost live for 24–48 hours while DNS propagates. Don't cancel your Bluehost account until propagation is confirmed and you've verified email is working.
---
## Step 8 — Email
**Moving to Arcline email:**
1. Create accounts in Arcline cPanel → **Email → Email Accounts**
2. Once nameservers switch, Arcline's MX records activate automatically
3. Export any mail you want to keep from Bluehost webmail (Bluehost uses Roundcube or Horde) before cancelling
**Keeping external email (Google Workspace, Microsoft 365):**
After switching nameservers to Arcline, add your existing MX records back in cPanel → **Domains → Zone Editor**. You'll find the required MX records in your Google or Microsoft 365 admin panel.
---
## Bluehost-specific notes
**SiteLock or CodeGuard backups** — these are Bluehost add-ons. You don't need them on Arcline; standard cPanel backups are included.
**WordPress staging site** — Bluehost provides a staging environment. After migration, delete the staging version from Bluehost to avoid confusion during the transition.
**Bluehost's custom wp-config constants** — Bluehost adds some non-standard constants to `wp-config.php` (like `COOKIE_DOMAIN` or Bluehost-specific feature flags). These can be removed safely after migrating.
**"Account Suspension" page appearing** — if Bluehost's CDN or caching layer still serves your domain during propagation, visitors may briefly see a Bluehost holding page. This resolves once propagation is complete.
**File permissions** — Bluehost uses suPHP/suEXEC. Standard permissions (644 files, 755 directories) work on Arcline. If Bluehost set unusual permissions (e.g., 777), correct them on Arcline.
---
## After migration checklist
- [ ] Site loads at `https://yourdomain.com`
- [ ] WordPress admin accessible at `/wp-admin`
- [ ] Forms submit and send email
- [ ] SSL certificate shows valid in browser
- [ ] Email accounts created and working
- [ ] Old Bluehost account not yet cancelled (wait 48 hours)
- [ ] DNS fully propagated (check at dnschecker.org)

176
content/migrate/from-godaddy.md Normal file
View File

@@ -0,0 +1,176 @@
---
title: "Migrate from GoDaddy"
description: "Step-by-step guide to moving your website and email from GoDaddy shared hosting to Arcline without downtime."
section: migrate
order: 1
---
# Migrate from GoDaddy
Moving from GoDaddy to Arcline involves three parts: transferring your files, moving your database, and finally switching DNS. Done in that order, you can complete the whole migration with zero downtime.
---
## Before you start
You'll need:
- GoDaddy cPanel login (or FTP credentials if you're on GoDaddy's non-cPanel shared hosting)
- Access to your Arcline cPanel account
- Your domain's registrar login (wherever you registered the domain — could be GoDaddy itself)
- About 30–60 minutes depending on site size
---
## Step 1 — Export your files from GoDaddy
### If GoDaddy uses cPanel
Log into GoDaddy's cPanel and create a full backup:
1. cPanel → **Files → Backup** (or **Backup Wizard**)
2. Choose **Full Account Backup** and download to your computer
The backup includes your `public_html` files and all databases.
### If GoDaddy uses their custom control panel (Websites + Marketing / Managed WordPress)
GoDaddy's Managed WordPress product doesn't give you direct file or database access. Options:
- Use the **Jetpack** or **UpdraftPlus** plugin to export a full backup (files + database) that you can import on Arcline
- Use the WordPress **Export** tool (Tools → Export) for content only, then reinstall plugins/themes manually
- Contact GoDaddy support and request a backup — they're required by some hosting terms to provide one on request
For standard GoDaddy shared hosting (cPanel-based), direct export is straightforward.
---
## Step 2 — Export your database from GoDaddy
If you used the full cPanel backup in Step 1, the database is already included. Otherwise:
1. GoDaddy cPanel → **Databases → phpMyAdmin**
2. Click your database name in the left sidebar
3. Click **Export → Quick → SQL → Go**
Save the `.sql` file.
For large databases: use **Custom** export, enable **Add DROP TABLE**, and export table-by-table if phpMyAdmin times out.
---
## Step 3 — Set up your site on Arcline
**Create the database:**
1. Arcline cPanel → **Databases → MySQL Databases**
2. Create a new database and a new user
3. Add the user to the database with **All Privileges**
4. Note the database name, username, and password
**Import the database:**
1. cPanel → phpMyAdmin → select the new database → **Import**
2. Upload the `.sql` file from GoDaddy
3. Click **Go**
For large databases, import via SSH instead (see [Back Up and Restore a MySQL Database](/getting-started/mysql-backup/)).
**Upload your files:**
Connect to your Arcline server via SFTP (see [Upload Files via SFTP](/getting-started/sftp/)) and upload your site files to `/home/username/public_html/`.
If you downloaded a full cPanel backup, extract it first and locate the `public_html` folder inside.
---
## Step 4 — Update your database connection settings
WordPress stores the database host, name, username, and password in `wp-config.php`. Update it to point to the new database you created in Step 3:
```php
define( 'DB_NAME', 'cpanelusername_newdbname' );
define( 'DB_USER', 'cpanelusername_newdbuser' );
define( 'DB_PASSWORD', 'your-new-password' );
define( 'DB_HOST', 'localhost' );
```
On GoDaddy, `DB_HOST` is sometimes a custom hostname. On Arcline it's always `localhost`.
For non-WordPress sites, update whatever config file stores your database credentials (`.env`, `config.php`, `database.yml`, etc.).
---
## Step 5 — Test before going live
Before switching DNS, preview your site on Arcline by editing your local `hosts` file.
Find your Arcline server IP in cPanel → **Server Information**.
**On macOS / Linux**, edit `/etc/hosts` (requires sudo):
```
123.456.789.0 yourdomain.com www.yourdomain.com
```
**On Windows**, edit `C:\Windows\System32\drivers\etc\hosts` as Administrator with the same line.
Now visit `https://yourdomain.com` in your browser — you'll see the Arcline version of your site even though DNS still points to GoDaddy. Check:
- Pages load correctly
- Images appear
- Forms work
- Login works (WordPress admin, etc.)
- SSL certificate is valid (if AutoSSL has run)
Remove the `hosts` entry when done testing.
---
## Step 6 — Switch DNS
When you're happy the site works on Arcline:
**If your domain is registered at GoDaddy:**
1. GoDaddy → My Products → Domains → click your domain
2. Scroll to **Nameservers → Change → I'll use my own nameservers**
3. Enter `ns1.arcline.it` and `ns2.arcline.it`
4. Save
**If your domain is registered elsewhere:**
Follow the nameserver update instructions for your registrar. See [Point Your Domain to Arcline](/getting-started/nameservers/) for provider-specific steps.
DNS propagation takes 15 minutes to a few hours. During this time, some visitors may still hit GoDaddy. Keep the GoDaddy site live until propagation is complete (at least 24 hours).
---
## Step 7 — Email migration
If you were using GoDaddy email (Workspace Email or Microsoft 365 through GoDaddy), you'll need to decide what to do with email:
**Switching to Arcline email:**
1. Create email accounts in Arcline cPanel → **Email → Email Accounts**
2. After nameservers switch, Arcline handles MX automatically
3. Export any email you want to keep from GoDaddy webmail before the cutover (GoDaddy Workspace Email → Settings → Export)
**Keeping GoDaddy email (or Microsoft 365):**
After switching nameservers to Arcline, add the original MX records back in cPanel → **Domains → Zone Editor**. GoDaddy's Workspace Email uses:
| Type | Priority | Value |
|---|---|---|
| MX | 0 | `mailstore1.secureserver.net` |
| MX | 10 | `smtp.secureserver.net` |
For Microsoft 365 through GoDaddy, the MX record is specific to your tenant — find it in your Microsoft 365 admin portal.
---
## Common GoDaddy-specific issues
**Site was on a subdomain (e.g., GoDaddy's temp URL)** — GoDaddy gives sites a staging URL while DNS isn't pointed. Make sure `siteurl` and `home` in WordPress → Settings → General (or `wp-config.php`) are set to your real domain, not GoDaddy's temp URL.
**GoDaddy's PHP version differs** — GoDaddy defaults vary. Check your PHP version in GoDaddy cPanel and match it in Arcline cPanel → **Software → Select PHP Version** to avoid compatibility issues.
**GoDaddy file permissions** — GoDaddy sometimes uses suEXEC with specific permission requirements. On Arcline, standard permissions (644 for files, 755 for directories) are correct.
**Email forwarding was set up at GoDaddy** — if you had forwarders, recreate them in Arcline cPanel → **Email → Forwarders** after switching nameservers.

195
content/migrate/from-hostgator.md Normal file
View File

@@ -0,0 +1,195 @@
---
title: "Migrate from HostGator"
description: "How to move your website from HostGator shared hosting to Arcline, including WordPress and cPanel-to-cPanel transfers."
section: migrate
order: 5
---
# Migrate from HostGator
HostGator runs cPanel on its shared and reseller plans, so migrating to Arcline is familiar territory. You'll export your files and database from HostGator, set them up on Arcline, test, and then switch nameservers.
---
## Before you start
- HostGator customer portal login (at [portal.hostgator.com](https://portal.hostgator.com)) — you may need this to reach cPanel if single sign-on is enabled
- Arcline cPanel account
- 30–90 minutes depending on site size
- Note your HostGator PHP version: cPanel → **Software → MultiPHP Manager**
---
## Step 1 — Export your files from HostGator
### From cPanel
1. Log in to HostGator cPanel (via customer portal or directly at `https://yourdomain.com:2083`)
2. **Files → Backup** (or **Backup Wizard**)
3. Choose **Full Backup** and download to your local machine
This produces a single archive with your `public_html` directory and all databases.
### Via SFTP
If the cPanel backup is too large to download through the browser, use SFTP:
- Host: your server hostname or IP (find it in HostGator cPanel → **Server Information**)
- Port: `2222` (HostGator's default non-standard SSH/SFTP port)
- Username and password: your cPanel credentials
Download everything in `/home/username/public_html/` to your local machine.
---
## Step 2 — Export your database from HostGator
1. HostGator cPanel → **Databases → phpMyAdmin**
2. Click your database name in the left sidebar
3. **Export → Quick → SQL → Go**
Save the `.sql` file.
For databases over 50 MB, use **Custom** export and check **Add DROP TABLE**. If phpMyAdmin times out, export via SSH:
```bash
mysqldump -u cpaneluser_dbuser -p cpaneluser_dbname > hostgator_backup.sql
```
---
## Step 3 — Set up on Arcline
**Create the database:**
1. Arcline cPanel → **Databases → MySQL Databases**
2. Create a new database and a new user
3. Add the user to the database with **All Privileges**
4. Write down the database name, username, and password
**Import the database:**
1. cPanel → phpMyAdmin → select the new (empty) database → **Import**
2. Choose the `.sql` file from HostGator
3. Click **Go**
For large imports, use the command line (see [Back Up and Restore a MySQL Database](/getting-started/mysql-backup/)).
**Upload your files:**
Connect to Arcline via SFTP and upload everything to `/home/username/public_html/`. See [Upload Files via SFTP](/getting-started/sftp/).
---
## Step 4 — Update wp-config.php
Edit your `wp-config.php` to use the new Arcline database credentials:
```php
define( 'DB_NAME', 'arclineuser_newdbname' );
define( 'DB_USER', 'arclineuser_newdbuser' );
define( 'DB_PASSWORD', 'your-new-password' );
define( 'DB_HOST', 'localhost' );
```
HostGator typically uses `localhost` for `DB_HOST` — same as Arcline. Update the database name, username, and password to the values you created in Step 3.
For non-WordPress sites, update the equivalent database configuration file.
---
## Step 5 — Check PHP version and extensions
1. HostGator cPanel → **Software → MultiPHP Manager** or **Select PHP Version** — note the version
2. Arcline cPanel → **Software → Select PHP Version** — set the same version
3. Check the **Extensions** tab to match any custom extensions your site uses
HostGator supports PHP 5.6 through 8.x. If your site is running an older version (5.6 or 7.0–7.3), consider updating to PHP 8.1+ on Arcline — test thoroughly before switching DNS.
---
## Step 6 — Test before DNS cutover
Add Arcline's server IP to your local `hosts` file to preview the site before changing DNS.
Find your Arcline IP in cPanel → **Server Information**.
Add this line to your hosts file:
```
YOUR_ARCLINE_IP yourdomain.com www.yourdomain.com
```
- **macOS / Linux:** `/etc/hosts` (requires sudo)
- **Windows:** `C:\Windows\System32\drivers\etc\hosts` (open as Administrator)
Visit `https://yourdomain.com` and verify:
- The homepage and key pages load
- Images and media work
- WordPress admin is accessible
- Contact forms, shopping cart, and other dynamic features work correctly
Remove the `hosts` entry after testing.
---
## Step 7 — Switch nameservers
**If your domain is registered at HostGator:**
1. Log in to HostGator customer portal → **Domains**
2. Select your domain and go to **Nameservers**
3. Choose **Custom Nameservers** and enter:
- `ns1.arcline.it`
- `ns2.arcline.it`
4. Save changes
**If your domain is registered elsewhere**, update nameservers at the registrar. See [Point Your Domain to Arcline](/getting-started/nameservers/) for provider-specific steps.
DNS propagation takes 15 minutes to a few hours. Keep HostGator active for at least 24 hours during propagation.
---
## Step 8 — Email migration
**Moving to Arcline email:**
1. Create your email accounts in Arcline cPanel → **Email → Email Accounts**
2. Once nameservers switch, Arcline handles MX records automatically
3. Export any mail you want to keep from HostGator webmail (Roundcube or Horde) before cancelling
**Keeping external email (Google Workspace, Microsoft 365):**
If you use an external email provider and only used HostGator for hosting, add your existing MX records back in Arcline cPanel → **Domains → Zone Editor** after switching nameservers.
---
## HostGator-specific notes
**SiteLock** — HostGator pushes SiteLock as an add-on for malware scanning. You don't need it on Arcline; standard WordPress security practices (keep everything updated, use strong passwords, limit login attempts) are sufficient. If you want extra scanning, use a free alternative like the Wordfence plugin.
**HostGator's custom caching** — HostGator sometimes uses server-level caching (Varnish or similar). Your site won't have this on Arcline, but standard WordPress caching plugins (W3 Total Cache, WP Super Cache) work well and give you more control.
**QuickInstall / Softaculous apps** — if you installed WordPress or other apps through HostGator's auto-installer, the installation itself is standard — it will migrate normally. The auto-installer is just a convenience tool; your site doesn't depend on it.
**HostGator's `public_html` / `www` difference** — HostGator sometimes uses `www` as a symlink to `public_html`. On Arcline, your site files go directly in `public_html`. Just upload everything there.
**Resource usage warnings** — HostGator's shared plans have strict inode and CPU limits. If you received warnings about resource usage, these don't apply on Arcline — our shared plans have different limits. Check your site's resource usage on Arcline's cPanel (left sidebar → **Resource Usage**).
**HostGator website builder** — if you built your site with HostGator's proprietary website builder (Gator Website Builder), it can't be exported as files. You'll need to rebuild the site on Arcline, or use a WordPress-based site instead. This guide only covers cPanel-based sites with standard file/database exports.
---
## After migration checklist
- [ ] Site loads correctly at `https://yourdomain.com`
- [ ] WordPress admin accessible at `/wp-admin`
- [ ] Forms submit and send email
- [ ] SSL certificate valid (AutoSSL in cPanel → **SSL/TLS Status**)
- [ ] PHP version matches what the site expects
- [ ] Email accounts created and working
- [ ] DNS propagated (check at dnschecker.org)
- [ ] HostGator account kept active for 48 hours as fallback
- [ ] HostGator account cancelled only after confirming everything works

201
content/migrate/from-namecheap.md Normal file
View File

@@ -0,0 +1,201 @@
---
title: "Migrate from Namecheap"
description: "Move your website and email from Namecheap shared hosting to Arcline — step by step, with zero downtime."
section: migrate
order: 4
---
# Migrate from Namecheap
Namecheap's shared hosting runs cPanel, which makes moving to Arcline straightforward. The process covers exporting your files and databases from Namecheap, setting them up on Arcline, testing, and then switching DNS.
---
## Before you start
- Namecheap cPanel login (reachable from your Namecheap dashboard → Hosting List → Manage → cPanel)
- Arcline cPanel account
- 30–90 minutes depending on site size
- Note your Namecheap PHP version: cPanel → **Software → Select PHP Version**
Namecheap is often both the host **and** the registrar — if your domain is registered there, you'll update nameservers in Namecheap's domain panel (covered in Step 6).
---
## Step 1 — Export your files from Namecheap
### Full cPanel backup
1. Namecheap cPanel → **Files → Backup** (or **Backup Wizard**)
2. Choose **Full Backup** and download to your local machine
This includes `public_html` and all databases in one archive.
### Manual export via SFTP
If you prefer to download files individually:
- Host: your server hostname or IP (find it in Namecheap cPanel → **Server Information**)
- Port: `21098` (Namecheap's default SFTP port) or `21` (FTP)
- Username and password: your cPanel credentials
Download `/home/username/public_html/` to your local machine.
---
## Step 2 — Export your database from Namecheap
1. Namecheap cPanel → **Databases → phpMyAdmin**
2. Click your database name in the left sidebar
3. Click **Export → Quick → SQL → Go**
Save the `.sql` file.
For large databases (over 50 MB), use **Custom** export and enable **Add DROP TABLE**, or export via SSH:
```bash
mysqldump -u cpaneluser_dbuser -p cpaneluser_dbname > namecheap_backup.sql
```
---
## Step 3 — Set up on Arcline
**Create the database:**
1. Arcline cPanel → **Databases → MySQL Databases**
2. Create a new database and a new user
3. Add the user to the database with **All Privileges**
4. Note the database name, username, and password — you'll need them for `wp-config.php`
**Import the database:**
1. cPanel → phpMyAdmin → select the new database → **Import**
2. Upload the `.sql` file from Namecheap
3. Click **Go**
For files over 50 MB, import via the command line instead (see [Back Up and Restore a MySQL Database](/getting-started/mysql-backup/)).
**Upload your files:**
Connect to Arcline via SFTP (see [Upload Files via SFTP](/getting-started/sftp/)) and upload your site to `/home/username/public_html/`.
---
## Step 4 — Update your database connection settings
WordPress stores database credentials in `wp-config.php`. Edit it to point to the new Arcline database:
```php
define( 'DB_NAME', 'arclineuser_newdbname' );
define( 'DB_USER', 'arclineuser_newdbuser' );
define( 'DB_PASSWORD', 'your-new-password' );
define( 'DB_HOST', 'localhost' );
```
On Namecheap, `DB_HOST` is typically `localhost` — same as Arcline. Change the other three values to match your new Arcline database.
For non-WordPress sites, update whatever config file stores your database credentials (`.env`, `config.php`, `database.yml`, etc.).
---
## Step 5 — Match the PHP version
Namecheap's default PHP version may differ from Arcline's. Check and match:
1. Namecheap cPanel → **Software → Select PHP Version** — note the version
2. Arcline cPanel → **Software → Select PHP Version** — set the same version
3. Also check the **Extensions** tab to enable any extensions your site needs (common ones: `mbstring`, `curl`, `gd`, `zip`, `intl`)
---
## Step 6 — Test before going live
Before switching DNS, preview your site on Arcline using your local `hosts` file.
Find your Arcline server IP in cPanel → **Server Information**.
**On macOS / Linux**, edit `/etc/hosts` (requires sudo):
```
YOUR_ARCLINE_IP yourdomain.com www.yourdomain.com
```
**On Windows**, edit `C:\Windows\System32\drivers\etc\hosts` as Administrator with the same line.
Now visit `https://yourdomain.com` in your browser. Check:
- Pages load correctly
- Images appear
- WordPress admin (/wp-admin) works
- Contact forms submit
- Any dynamic features (shopping cart, search) work
Remove the `hosts` entry when done testing.
---
## Step 7 — Switch nameservers
Since Namecheap is likely both your host and registrar, you'll update nameservers in the Namecheap domain panel (not cPanel).
1. Log in to Namecheap → **Domain List**
2. Click **Manage** next to your domain
3. Under **Nameservers**, change the dropdown from **Namecheap BasicDNS** to **Custom DNS**
4. Enter:
- `ns1.arcline.it`
- `ns2.arcline.it`
5. Click the green checkmark to save
DNS propagation takes 15 minutes to a few hours. Keep Namecheap's hosting active during propagation — both servers will serve the site until DNS fully switches.
> If your domain is registered **elsewhere**, update nameservers at that registrar. See [Point Your Domain to Arcline](/getting-started/nameservers/) for steps by provider.
---
## Step 8 — Email migration
**Moving to Arcline email:**
1. Create email accounts in Arcline cPanel → **Email → Email Accounts**
2. After nameservers switch, Arcline's MX records activate automatically
3. Export any mail you want to keep from Namecheap webmail (usually Roundcube) before cancelling
**Keeping Namecheap email (Private Email):**
If you subscribed to Namecheap's Private Email service and want to keep it, add the MX records back in Arcline cPanel → **Domains → Zone Editor** after switching nameservers. Namecheap Private Email uses:
| Type | Priority | Value |
|-------|----------|-------------------------------|
| MX | 10 | `mx1.privateemail.com` |
| MX | 20 | `mx2.privateemail.com` |
You'll also need the SPF record Namecheap provides in your Private Email settings.
---
## Namecheap-specific notes
**Namecheap's SSL certificates** — Namecheap sells PositiveSSL certificates. These don't transfer to Arcline. Arcline includes free AutoSSL (Let's Encrypt) which will issue automatically once your domain resolves to Arcline. Don't bother exporting Namecheap's SSL cert.
**Supersonic CDN** — Namecheap includes a basic CDN on some plans. Your site doesn't need it on Arcline; our infrastructure already includes caching and performance optimization by default.
**Namecheap's backup service** — Namecheap offers paid automated backups. You don't need this add-on on Arcline — use cPanel's built-in backup tools or set up a cron-based backup (see [Back Up and Restore a MySQL Database](/getting-started/mysql-backup/)).
**EasyWP (Namecheap managed WordPress)** — if you're on Namecheap's EasyWP platform instead of cPanel hosting, you can't export via cPanel. Use a WordPress backup plugin (UpdraftPlus or All-in-One WP Migration) to export your files and database, then import the backup on Arcline.
**.htaccess redirects** — if Namecheap added custom redirects in your `.htaccess` file (e.g., non-www to www), they'll come over with your files and work on Arcline without changes.
---
## After migration checklist
- [ ] Site loads at `https://yourdomain.com`
- [ ] WordPress admin accessible at `/wp-admin`
- [ ] Forms submit and send email
- [ ] SSL certificate valid (check cPanel → **SSL/TLS Status**)
- [ ] Email accounts created and working
- [ ] PHP version and extensions match
- [ ] DNS fully propagated (verify at dnschecker.org)
- [ ] Namecheap hosting account kept active for 48 hours as fallback

200
content/migrate/from-siteground.md Normal file
View File

@@ -0,0 +1,200 @@
---
title: "Migrate from SiteGround"
description: "How to transfer your website and database from SiteGround to Arcline, including handling SiteGround's custom tools and SuperCacher."
section: migrate
order: 3
---
# Migrate from SiteGround
SiteGround uses cPanel on older accounts and their own Site Tools panel on newer ones. The migration process is similar either way: export your files and database, set up on Arcline, test, then cut over DNS.
---
## Before you start
- SiteGround Site Tools or cPanel access
- Arcline cPanel account
- 30–90 minutes depending on site size
- Note any SiteGround-specific plugins installed (see [SiteGround-specific notes](#siteground-specific-notes))
---
## Step 1 — Export files from SiteGround
### Via Site Tools (newer SiteGround accounts)
SiteGround's Site Tools replaced cPanel on newer accounts. To export your files:
1. Site Tools → **Site → FTP Accounts** — create an FTP user if you don't have one
2. Connect with FileZilla or Cyberduck to `yourdomain.com` on port 22 (SFTP) or 21 (FTP)
3. Download your `public_html` folder
Or use SiteGround's Backup tool:
1. Site Tools → **Security → Backups**
2. Select the most recent backup date
3. Click **Restore** on **File System** — but choose **Download** instead of restore to download the archive
### Via cPanel (older SiteGround accounts)
cPanel → **Files → Backup Wizard → Full Backup → Download**
This creates a full archive including databases.
---
## Step 2 — Export your database
### Site Tools
1. Site Tools → **Site → MySQL** → select your database → click **phpMyAdmin**
2. Click the database name in the left sidebar
3. **Export → Quick → SQL → Go**
Or use the **Backup** tool → select the most recent backup → **Download** on the database section.
### cPanel
cPanel → **Databases → phpMyAdmin** → select database → **Export → Quick → SQL → Go**
For large databases, export via SSH:
```bash
mysqldump -u dbusername -p dbname > siteground_backup.sql
```
---
## Step 3 — Set up on Arcline
**Create the database:**
1. Arcline cPanel → **Databases → MySQL Databases**
2. Create a database, a user, and assign the user with **All Privileges**
3. Note all three: database name, username, password
**Import the database:**
1. cPanel → phpMyAdmin → select the new (empty) database → **Import**
2. Choose the `.sql` file from SiteGround
3. Click **Go**
For large files (over 50 MB), import via SSH (see [Back Up and Restore a MySQL Database](/getting-started/mysql-backup/)).
**Upload files:**
Connect via SFTP to Arcline and upload everything to `/home/username/public_html/`. See [Upload Files via SFTP](/getting-started/sftp/).
---
## Step 4 — Update database credentials
Edit `wp-config.php` (or your site's database config file) with the new credentials:
```php
define( 'DB_NAME', 'arclinecpanel_dbname' );
define( 'DB_USER', 'arclinecpanel_dbuser' );
define( 'DB_PASSWORD', 'your-new-password' );
define( 'DB_HOST', 'localhost' );
```
SiteGround sometimes uses a non-localhost `DB_HOST` (e.g., a private IP). On Arcline, it's always `localhost`.
---
## Step 5 — Check PHP version
1. SiteGround Site Tools → **Devs → PHP Manager** — note the PHP version
2. Arcline cPanel → **Software → Select PHP Version** — match it
Also enable any PHP extensions your site needs. Common ones: `mbstring`, `curl`, `gd`, `imagick`, `intl`, `zip`. Check the **Extensions** tab in MultiPHP Manager on Arcline.
---
## Step 6 — Remove SiteGround caching
SiteGround's SuperCacher (now called SG Optimizer) installs a caching plugin and server-side caching. Before testing on Arcline:
1. Deactivate the **SG Optimizer** plugin (or **SiteGround Optimizer**) — it will try to connect to SiteGround's infrastructure which won't be available on Arcline
2. Delete any `.htaccess` lines added by SG Optimizer that reference SiteGround-specific caching rules
3. Install a standard WordPress caching plugin instead (LiteSpeed Cache, W3 Total Cache, or WP Super Cache work well on Arcline)
If you leave SG Optimizer active, the plugin will disable itself gracefully on non-SiteGround servers, but it's cleaner to remove it.
---
## Step 7 — Test before DNS cutover
Add your Arcline server IP to your local `hosts` file:
```
YOUR_ARCLINE_IP yourdomain.com www.yourdomain.com
```
**macOS / Linux:** `/etc/hosts` (requires sudo)
**Windows:** `C:\Windows\System32\drivers\etc\hosts` (as Administrator)
Visit your domain and check:
- Homepage and key pages load
- Images display
- WordPress admin works
- Contact forms submit
- Any e-commerce checkout works (if applicable)
Remove the `hosts` entry when done.
---
## Step 8 — Switch nameservers
**If your domain is registered at SiteGround** (they became a domain registrar):
1. SiteGround → **Domains** → select your domain
2. Go to **Nameservers** and select **Custom Nameservers**
3. Enter:
- `ns1.arcline.it`
- `ns2.arcline.it`
4. Save
**If registered elsewhere**, update nameservers at that registrar. See [Point Your Domain to Arcline](/getting-started/nameservers/).
Leave SiteGround running for 24–48 hours. Both servers will serve the site during propagation — that's fine, the content is the same.
---
## Step 9 — Email migration
**Moving to Arcline email:**
1. Create accounts in Arcline cPanel → **Email → Email Accounts**
2. Arcline's MX records activate after nameservers switch
3. Export existing email from SiteGround's webmail (Roundcube) before cancelling
**Keeping Google Workspace or another provider:**
After switching nameservers, re-add your external MX records in Arcline cPanel → **Domains → Zone Editor**.
---
## SiteGround-specific notes
**SG Optimizer / SuperCacher** — disable and remove before or shortly after migration. It won't cause harm on Arcline but serves no purpose.
**SiteGround staging** — if you used SiteGround's staging feature, the staging site lives on their servers. You can ignore it; migrate only the production site.
**Cloudflare via SiteGround** — SiteGround has a built-in Cloudflare integration. If your site was using it, you have a Cloudflare account attached to SiteGround. After migrating, you can either:
- Switch to Arcline nameservers directly (disables the SiteGround-managed Cloudflare)
- Keep Cloudflare: transfer the zone to your own Cloudflare account and update the A record to point to Arcline's IP
**SiteGround emails about resource limits** — if you were on SiteGround's entry-level plan, you may have hit CPU/memory limits. These limits don't carry over; Arcline has its own resource allocation.
**WordPress auto-updates** — SiteGround has WordPress auto-update settings in Site Tools. These won't apply on Arcline. Set up your own update preferences in WordPress → **Dashboard → Updates** or use a plugin like ManageWP.
---
## After migration checklist
- [ ] Site loads at `https://yourdomain.com`
- [ ] SSL certificate valid
- [ ] WordPress admin accessible
- [ ] SG Optimizer deactivated/removed
- [ ] Caching plugin configured for Arcline
- [ ] Email accounts working
- [ ] DNS propagated (verify at dnschecker.org)
- [ ] SiteGround account kept active for 48 hours as fallback

274
content/migrate/from-wpengine.md Normal file
View File

@@ -0,0 +1,274 @@
---
title: "Migrate from WP Engine or Kinsta"
description: "How to move a WordPress site from managed hosting (WP Engine, Kinsta) to Arcline's VPS or shared hosting without downtime."
section: migrate
order: 6
---
# Migrate from WP Engine or Kinsta
WP Engine and Kinsta are managed WordPress hosts. They don't provide cPanel or direct server access — instead you get a custom dashboard with WordPress-specific tools. Migrating to Arcline involves exporting your site through WordPress itself and setting it up fresh.
The process is similar for both WP Engine and Kinsta. Differences are called out where they matter.
---
## Before you start
- WP Engine User Portal or Kinsta MyKinsta dashboard access
- WordPress admin access (for plugin-based backups)
- Arcline cPanel account (for shared hosting) or VPS access
- 45–90 minutes depending on your site size
- **Important:** Managed hosts sometimes disallow certain plugins. Check the [WP Engine disallowed plugins list](https://wpengine.com/support/disallowed-plugins/) or [Kinsta banned plugins list](https://kinsta.com/knowledgebase/banned-plugins/) — if your backup plugin is on the list, use the manual export method instead.
---
## Step 1 — Export your WordPress site
You have three options for exporting. Choose one.
### Option A: UpdraftPlus (easiest)
1. Install the **UpdraftPlus** plugin from your WordPress admin → Plugins → Add New
2. Go to **Settings → UpdraftPlus Backups**
3. Click **Backup Now** and select both **Database** and **Files**
4. When the backup completes, download all five files from the **Existing Backups** tab:
- Database
- Plugins
- Themes
- Uploads
- Others
### Option B: All-in-One WP Migration
1. Install **All-in-One WP Migration** from Plugins → Add New
2. Go to **All-in-One WP Migration → Export**
3. Choose **Export To → File**
4. Download the `.wpm` file when it's ready
> The free version has a 512 MB upload limit for importing. If your site is larger, use UpdraftPlus or manual export instead.
### Option C: Manual export
**Export files from WP Engine:**
WP Engine provides SFTP access — you can connect with FileZilla or Cyberduck:
1. WP Engine User Portal → **Sites → your site → SFTP**
2. Note the host, port (2222), username, and password shown
3. Connect with FileZilla and download the entire `wp-content` folder
**Export files from Kinsta:**
Kinsta provides SFTP and SSH access:
1. MyKinsta → **Sites → your site → Info**
2. Under **SFTP/SSH**, note the host, port, username, and password
3. Connect with FileZilla and download the `wp-content` folder
**Export the database:**
Both hosts include phpMyAdmin access:
1. **WP Engine:** User Portal → Sites → your site → **phpMyAdmin** (under Utilities)
2. **Kinsta:** MyKinsta → Sites → your site → **Info** → Open phpMyAdmin
Select your database in the left sidebar → **Export → Quick → SQL → Go**.
---
## Step 2 — Set up WordPress on Arcline
### On shared hosting (cPanel)
1. Arcline cPanel → **Software → WordPress Manager by Softaculous**, or install manually
2. Create a fresh WordPress installation in the root `public_html` directory (or a subdirectory if you prefer to test there first)
### Manual WordPress install
1. Download WordPress from [wordpress.org](https://wordpress.org/download/)
2. Upload the files to `/home/username/public_html/` via SFTP
3. Create a database in cPanel → **Databases → MySQL Databases**
4. Create a database user and add it to the database with **All Privileges**
5. Visit `https://yourdomain.com` and complete the WordPress installation wizard
6. Use the database name, username, and password from step 3
### On a VPS
Follow the VPS setup guides for installing WordPress on a LAMP or LEMP stack.
---
## Step 3 — Import your site
### If you used UpdraftPlus
1. Install and activate UpdraftPlus on your fresh Arcline WordPress installation
2. Go to **Settings → UpdraftPlus Backups → Existing Backups → Upload backup files**
3. Upload all five files you downloaded in Step 1
4. After upload, click **Restore** and select all components
5. UpdraftPlus will restore your database and files
6. Log out and log back in — you'll use your **original** WordPress username and password now
### If you used All-in-One WP Migration
1. Install **All-in-One WP Migration** on the fresh Arcline WordPress installation
2. Go to **All-in-One WP Migration → Import**
3. Upload the `.wpm` file
4. Confirm the overwrite warning
5. Log out and log back in with your original credentials
### If you exported manually
1. Delete the `wp-content` folder on your new Arcline installation (via SFTP or file manager)
2. Upload the `wp-content` folder from your managed host backup
3. In phpMyAdmin on Arcline, select the new WordPress database → **Import** → upload the `.sql` file
4. Update `wp-config.php` to match the database credentials you created in Arcline cPanel:
```php
define( 'DB_NAME', 'arclineuser_wpdb' );
define( 'DB_USER', 'arclineuser_wpuser' );
define( 'DB_PASSWORD', 'your-password' );
define( 'DB_HOST', 'localhost' );
```
On WP Engine and Kinsta, `DB_HOST` is **not** `localhost` — it's a remote database server address. You must change this to `localhost` for Arcline.
---
## Step 4 — Update URLs in the database
Managed hosts often use a temporary or staging domain before your real domain points to them. If your WordPress database still references an old URL, update it.
After importing, log in to your WordPress admin and install **Better Search Replace**. Search for the old URL (e.g., `yourdomain.wpengine.com` or `staging-yourdomain.kinsta.cloud`) and replace it with `yourdomain.com` across all tables.
Alternatively, use WP-CLI over SSH:
```bash
wp search-replace 'yourdomain.wpengine.com' 'yourdomain.com' --all-tables
wp search-replace 'staging-yourdomain.kinsta.cloud' 'yourdomain.com' --all-tables
```
---
## Step 5 — Disable managed-host-specific plugins
WP Engine and Kinsta install plugins that connect to their infrastructure. These won't work on Arcline and should be removed:
**WP Engine:**
- **WP Engine Smart Plugin Manager** — manages updates through WP Engine's infrastructure
- **WP Engine Automated Migration** — only connects to WP Engine
**Kinsta:**
- **Kinsta MU Plugin** (must-use plugin) — handles Kinsta's caching and CDN integration. Delete it from `/wp-content/mu-plugins/`
- **Kinsta Cache Plugin** — only works on Kinsta's infrastructure
Remove these from WordPress admin → Plugins. For must-use plugins, delete them via SFTP from `wp-content/mu-plugins/`.
---
## Step 6 — Set up caching
Managed hosts include server-level caching. On Arcline, you'll need to set this up yourself:
1. Install **W3 Total Cache** or **WP Super Cache** (both free)
2. Configure page caching and browser caching — default settings are fine for most sites
3. For VPS users: also consider PHP-FPM opcache and Nginx fastcgi_cache
---
## Step 7 — Test before switching DNS
Before pointing your domain to Arcline, test using your `hosts` file.
Find your server IP in Arcline cPanel → **Server Information** (or use your VPS IP).
Add this line to your hosts file:
```
YOUR_ARCLINE_IP yourdomain.com www.yourdomain.com
```
Now visit `https://yourdomain.com` in your browser. Verify:
- The site loads correctly
- All pages, posts, and media display
- WordPress admin works (use your original credentials)
- Plugins and themes function
- Any e-commerce checkout, forms, and membership features work
Remove the `hosts` entry after testing.
---
## Step 8 — Switch DNS/nameservers
**If your domain is managed at the managed host:**
- **WP Engine:** WP Engine doesn't do domain registration. Your domain is likely at a separate registrar (GoDaddy, Namecheap, etc.). Update nameservers there.
- **Kinsta:** Kinsta doesn't register domains. Manage DNS at your registrar.
**At your registrar**, change nameservers to:
```
ns1.arcline.it
ns2.arcline.it
```
See [Point Your Domain to Arcline](/getting-started/nameservers/) for registrar-specific instructions.
**If you use Cloudflare:**
Keep Cloudflare nameservers and update the A record to point to your Arcline IP. Remove any WP Engine or Kinsta-specific DNS records.
DNS propagation takes 15 minutes to a few hours. Keep your managed host active during the transition.
---
## Step 9 — Email
Managed WordPress hosts typically **don't** include email hosting. If you had email set up elsewhere (Google Workspace, Microsoft 365, your registrar), it won't be affected by this migration.
If you want to set up email on Arcline after migration, see [Set Up Email on Your Domain](/getting-started/email-setup/). You'll create accounts in Arcline cPanel and, if your DNS is managed externally, add the required MX records.
---
## WP Engine-specific notes
**Git push deployment** — WP Engine supports deploying via Git. This doesn't transfer; you'll use SFTP or standard WordPress workflows on Arcline.
**WP Engine CDN** — WP Engine includes a CDN. On Arcline, you can optionally set up Cloudflare (free tier) if you want CDN coverage.
**WP Engine's redirect rules** — if you set up redirects through WP Engine's rules engine, recreate them in your `.htaccess` file on Arcline.
**Staging → Production** — WP Engine's three-environment setup (dev/staging/production) is managed by their platform. On Arcline, set up a staging subdomain manually if you need a test environment.
---
## Kinsta-specific notes
**Kinsta CDN** — Kinsta includes Cloudflare-powered CDN. Similar to WP Engine, you can optionally set up Cloudflare independently on Arcline.
**Kinsta's Redis caching** — Kinsta uses Redis for object caching. On Arcline, install a Redis object cache plugin (like **Redis Object Cache**) if your plan or VPS includes Redis. For shared hosting without Redis, the standard page caching plugins are sufficient.
**Kinsta's New Relic monitoring** — Kinsta includes performance monitoring. On Arcline, use Query Monitor (free WordPress plugin) for basic performance debugging.
**PHP 8.x** — Kinsta pushes PHP 8.x aggressively. Arcline supports PHP 8.1 and 8.2 on all shared plans and VPS instances. Your site should run without PHP version issues.
**IonCube and other loaders** — Kinsta doesn't support IonCube or SourceGuardian. Neither does standard Arcline shared hosting. If your site requires these encoders, you'll need a VPS where you can install them.
---
## After migration checklist
- [ ] Site loads at `https://yourdomain.com`
- [ ] WordPress admin works with original credentials
- [ ] All plugins and themes function
- [ ] Managed-host plugins removed (WP Engine MU plugin, Kinsta cache plugin)
- [ ] Caching plugin installed and configured
- [ ] SSL certificate active (AutoSSL or Let's Encrypt)
- [ ] Email accounts set up (if using Arcline email)
- [ ] DNS propagated (check at dnschecker.org)
- [ ] Managed host account kept active for 48 hours as fallback
- [ ] Managed host billing cancelled only after confirming everything works

203
content/migrate/transfer-domain.md Normal file
View File

@@ -0,0 +1,203 @@
---
title: "Transfer a Domain to Arcline"
description: "How to transfer your domain registration to Arcline's registrar service — what you need to unlock, what it costs, and what to expect during the transfer."
section: migrate
order: 7
---
# Transfer a Domain to Arcline
Domain transfers move your domain **registration** from one registrar to another. It's separate from moving your website hosting — you can host at Arcline while keeping your domain registered wherever it is now, or you can transfer the registration to Arcline so everything is in one place.
---
## Before you transfer
A domain transfer typically takes **5–7 days**. During that time:
- Your website and email **are not affected** if DNS records stay the same
- You can't update nameservers or DNS records at the old registrar
- The domain is locked for 60 days after the transfer completes (ICANN rule)
**Transfers are not free.** ICANN charges registries a transfer fee, which becomes the renewal cost. When you transfer a domain to Arcline, you pay for **one additional year of registration** added to your current expiration date. If your domain expires in 6 months, after the transfer it will expire in 18 months.
---
## Step 1 — Check eligibility
A domain must meet these requirements to transfer:
- **Registered more than 60 days ago** — ICANN prohibits transfers within 60 days of initial registration
- **Not transferred in the last 60 days** — same lock applies after a previous transfer
- **More than 15 days from expiration** — most registrars block transfers of domains about to expire
- **Not in redemption or pending delete status** — the domain must be active
You can check your domain's registration date and status via WHOIS:
```
whois yourdomain.com
```
Or use a web-based WHOIS lookup at [whois.icann.org](https://whois.icann.org).
---
## Step 2 — Prepare the domain at your current registrar
### Unlock the domain
Most registrars keep domains locked to prevent unauthorized transfers. Find the lock setting:
- **GoDaddy:** Domain Settings → Domain lock → toggle off
- **Namecheap:** Domain List → Manage → Sharing & Transfer → unlock
- **Google Domains:** DNS → Registration settings → unlock
- **Cloudflare:** Domain Registration → Manage → Configuration → unlock
- **Other registrars:** look for "Domain lock", "Registrar lock", "Transfer lock", or "Theft protection"
The lock may take a few minutes to a few hours to release.
### Get the authorization code (EPP code)
The authorization code (also called EPP code or transfer key) is a one-time code required to approve the transfer:
- **GoDaddy:** Domain Settings → Transfer domain away from GoDaddy → Get authorization code
- **Namecheap:** Domain List → Manage → Transfer Out → Request EPP code (sent to your email)
- **Google Domains:** DNS → Registration settings → Get authorization code
- **Cloudflare:** Domain Registration → Manage → Configuration → Request auth code
- **Other registrars:** look for "Transfer out", "Authorization code", "EPP code", or "Auth info"
The code is typically a string of 6–32 characters. Save it — you'll need it in the next step.
### Verify admin contact email
Transfer confirmations are sent to the domain's **admin contact email** listed in WHOIS. Make sure this email address:
- Is one you have access to
- Isn't an email address at the domain you're transferring (e.g., `admin@yourdomain.com`) — because if DNS changes, you might miss the confirmation email
If needed, update the admin contact email at your current registrar before starting the transfer.
### Disable WHOIS privacy (if required)
Some registrars require WHOIS privacy to be disabled during a transfer. Check your registrar's transfer documentation. If required:
- **GoDaddy:** Domain Settings → WHOIS privacy → turn off
- **Namecheap:** Domain List → Manage → Domain Privacy → disable
- **Others:** look for "WHOIS privacy", "Privacy protection", or "ID protection"
Turn it back on after the transfer completes.
---
## Step 3 — Initiate the transfer at Arcline
Contact Arcline support to start a domain transfer. Provide:
- The domain name
- The authorization code (EPP code) from Step 2
- Confirmation that the domain is unlocked
Arcline will initiate the transfer through our registrar. The cost is one year's renewal fee, which will be added to your Arcline invoice.
---
## Step 4 — Approve the transfer
After Arcline initiates the transfer, you'll receive two emails:
1. **From your current registrar** — asking for confirmation that you want to transfer the domain away. You must click the approval link within a few days, or the transfer cancels.
2. **From the registry** (Verisign for `.com`/`.net`, Public Interest Registry for `.org`, etc.) — confirming the transfer has been requested.
Follow the instructions in both emails. If you don't receive them within a few hours, check your spam folder and verify the admin contact email is correct.
Some registrars (GoDaddy, Namecheap) allow you to approve the transfer from their dashboard instead of waiting for the email. If that option is available, use it — it's faster.
---
## Step 5 — Wait for the transfer to complete
Once approved, the transfer takes **5 days by default**. The losing registrar can release the domain sooner, but most of them wait the full period as a security measure.
During this time:
- Your website and email **continue working normally** — the transfer only affects the registration, not DNS
- You can't change nameservers at your current registrar
- The domain shows a "pending transfer" status in WHOIS
If your domain's DNS is managed at your current registrar, your DNS records are copied as-is and continue pointing wherever they pointed before. Nothing breaks during a transfer.
---
## Step 6 — After the transfer completes
Once Arcline confirms the transfer is complete:
1. **Verify your DNS records** — log in to your Arcline account and check that your DNS zone is correctly set up with the records you need (A, MX, CNAME, TXT, etc.)
2. **Update nameservers** — if you want DNS managed by Arcline, make sure nameservers are set to `ns1.arcline.it` and `ns2.arcline.it`
3. **Re-enable WHOIS privacy** — turn privacy protection back on if you want it
4. **Check email** — if your email uses the domain (e.g., `you@yourdomain.com`), verify that MX records are present and mail is flowing
---
## Transferring from specific registrars
### GoDaddy
GoDaddy often tries to retain domains by making the transfer process confusing. The key steps:
1. Unlock: Domain Settings → scroll to **Domain lock** → toggle off. Wait 10 minutes.
2. Auth code: GoDaddy calls it the **Authorization Code**. They'll email the admin contact with a link to retrieve it.
3. After initiating: GoDaddy sends a confirmation email with a link to approve the transfer. If you ignore this email, the transfer **will still complete after 5 days** — GoDaddy changed this policy and now auto-approves transfers after the waiting period.
### Namecheap
1. Unlock: Domain List → Manage → Sharing & Transfer → unlock
2. Auth code: Request via **Transfer Out** tab → **Request EPP Code** (emailed to you)
3. Namecheap's confirmation email includes an "Approve Transfer" link — click it for a faster transfer
### Google Domains
1. Unlock: DNS → Registration settings → unlock
2. Auth code: **Get authorization code** in Registration settings
3. Google Domains generally processes transfers quickly
### Cloudflare (as registrar)
1. Unlock: Domain Registration → Manage → Configuration → unlock
2. Auth code: **Request auth code** in Configuration
3. Cloudflare automatically removes your DNS zone after a successful transfer, which can cause downtime. Before transferring away from Cloudflare, export your DNS records (Cloudflare dashboard → DNS → Export) so you can re-import them at Arcline.
---
## What if the transfer fails?
Common reasons for transfer failure and how to fix them:
| Problem | Fix |
|---|---|
| Domain is locked | Unlock at current registrar and try again |
| Wrong authorization code | Request a new one from the current registrar |
| Domain registered less than 60 days ago | Wait until 60 days have passed since registration |
| Transferred within last 60 days | Wait until 60 days have passed since the previous transfer |
| Domain expired | Renew at current registrar first, then transfer |
| Admin contact didn't approve | Check email and spam folder. Ask Arcline support to resend |
| WHOIS privacy blocking | Disable privacy protection at current registrar |
Contact Arcline support if a transfer fails unexpectedly — we can check the exact reason and help you fix it.
---
## Transfer vs. just changing nameservers
You don't need to transfer your domain to host at Arcline. The alternative is simply updating your nameservers to `ns1.arcline.it` and `ns2.arcline.it` at your current registrar (see [Point Your Domain to Arcline](/getting-started/nameservers/)).
**Transfer when:**
- You want all billing in one place (Arcline)
- Your current registrar has raised prices or has bad support
- You're consolidating after an acquisition (Google Domains → Squarespace, etc.)
**Just change nameservers when:**
- You like your current registrar
- The domain isn't eligible for transfer yet (within 60-day lock)
- You want to keep registration and hosting with different providers