=== EasyWpTools Migration, Backup & Restore for WordPress – Full Documentation (English) ===

== Overview ==

EasyWpTools Migration, Backup & Restore for WordPress allows you to move your old WordPress website onto a new WordPress installation.

This is a TWO-STAGE process:

1. Export your OLD website
2. Install (restore) it over a NEW WordPress installation


== IMPORTANT CONCEPT (READ CAREFULLY) ==

- The NEW WordPress installation is ONLY a base
- Your OLD website is stored inside TWO files:

database.sql
files.zip

When you click "Run Restore", the plugin:

- Removes parts of the NEW installation
- Replaces them with your OLD website

This means you are NOT "updating" the site
You are REPLACING the new site with your old one


== HOW THE PLUGIN WORKS (STEP-BY-STEP) ==

== 1. EXPORT PROCESS (OLD WEBSITE) ==

When you click "Export Website":

- The plugin reads your OLD database
- It generates: database.sql
- It scans your files:
  /wp-content/uploads
  /wp-content/themes
  /wp-content/plugins

- It creates: files.zip

RESULT:
You now have your FULL website inside TWO files


== 2. PREPARING THE BACKUP ==

You MUST create:

wpem-backup.zip

Inside it:

- database.sql
- files.zip

IMPORTANT:
Both files must be directly inside the ZIP
NOT inside a folder


== 3. IMPORT PROCESS (NEW WEBSITE) ==

On the NEW WordPress installation:

- Install the plugin
- Upload wpem-backup.zip

The plugin will:

- Extract the ZIP
- Store files in a temporary import directory


== 4. RESTORE PROCESS (CRITICAL STEP) ==

When you click "Run Restore":

The plugin will:

1. Delete non-matching database tables
2. Import database.sql
3. Extract and copy files.zip
4. Replace old URLs with the new URL
5. Clean temporary files


== WHAT HAPPENS NEXT (IMPORTANT) ==

After restore:

- Your website may go blank
- You may see errors

THIS IS NORMAL

This means the plugin has FINISHED its job


== FINAL STEP (MANUAL – REQUIRED) ==

You MUST update:

$table_prefix

Steps:

1. Access your website via:
   - SFTP
   - Hosting File Manager

2. Open file:
   wp-config.php

3. Find:
   $table_prefix = 'wp_';

4. Replace it with your OLD prefix from database.sql

Example:
   $table_prefix = 'abc_';

5. Save the file
6. Upload it BACK to the server (overwrite the original)


== AFTER UPDATING PREFIX ==

- The website may take a few minutes to 1 hour to load
- Depends on hosting/server

You may need to:

- Visit /wp-admin
- Log in again
- Or access via hosting panel


== SSL CERTIFICATE (VERY IMPORTANT) ==

Before starting migration:

- Make sure SSL is ACTIVE

If SSL is NOT ready:

- Website may not load
- HTTPS errors may occur

Some hosts require:

- TXT verification
- CNAME setup

This may take time → WAIT until SSL is fully active


== WHERE FILES ARE STORED ==

Temporary files are stored in:

/wp-content/uploads/wpem-private/

Includes:

- database.sql
- files.zip
- import folder

These are automatically deleted after restore


== UNDERSTANDING THE PROCESS ==

New WordPress = Base installation

database.sql + files.zip = Your OLD website

Run Restore = Replacing base with your OLD site

$table_prefix = Final connection step


== KEY TERMS (IMPORTANT INDEX) ==

Export Website
= Creates backup from OLD site

Import Website
= Uploads backup to NEW site

Run Restore
= Installs OLD site over NEW WordPress

Old Site URL
= Used to replace links

database.sql
= Your database

files.zip
= Your website files

$table_prefix
= Connects WordPress to database


== TIPS ==

- Always use a fresh WordPress installation
- Do NOT refresh too early during restore
- Wait until process finishes
- Keep backup copies
- Large websites take longer


== COMMON MISTAKES ==

- Wrong ZIP structure
- Not updating $table_prefix
- SSL not ready
- Using on live site without backup


== FINAL RESULT ==

When everything is correct:

- Your OLD website loads
- Admin panel works
- URLs are correct
- Migration complete