DIGITER MIGRATION LITE - MANUAL RESTORE AND MIGRATION

This portable ZIP is independent of the Full edition. Manual restoration is free.
It is NOT a DGM4 package and cannot be opened by the Full edition's importer.

BEFORE BACKUP
Pause content edits, uploads, orders, cron writes and other database/file changes.
The export reads live data in batches; it is NOT an atomic database snapshot.
Keep the backup tab open. After an interrupted request, reopen it and Resume.
If your host cannot process a large file or table, use its backup tools instead.

WHAT IS INCLUDED
Numbered database/*.sql files, wp-content files, manifest.json and these instructions.
SQL contains this site's table-prefix tables, including users and plugin settings.
The archive contains sensitive data. Store it privately and encrypt your stored copy.

WHAT IS EXCLUDED
WordPress core, wp-config.php, web-server configuration, other files outside
wp-content, symbolic links, special files, .git, .svn, .env, debug.log, cache,
upgrade, upgrade-temp-backup, backup/backups, updraft, ai1wm-backups and directories
whose name begins with digiter-migration-. These names are excluded at any depth.
The manifest shows an excluded-entry count; a skipped directory counts as one.
Custom database triggers, stored routines and events are not exported. Views and
multisite and spatial columns are unsupported. Keep separate copies of custom configuration, secrets,
external uploads, symlink targets, and database objects not covered here.

RESTORE ON A STAGING SITE FIRST
1. Preserve a complete backup of the destination. Extract this ZIP locally.
   Never leave this archive or its SQL files in a publicly reachable web directory.
2. Install a compatible clean WordPress release. Create a NEW empty database.
   Configure wp-config.php for that database, its credentials and the table_prefix
   shown in manifest.json. Supply your own security salts and host-specific settings.
3. Copy wp-content into the destination using SFTP or the hosting file manager.
   Existing source plugin/theme files may execute after restoring the database;
   restore only your trusted backups. Review plugin compatibility on the new host.
4. Import EVERY database/*.sql file in ascending filename order. They are chunks
   of one logical database dump. Do not select only the first file.
   SQL DROPS and REPLACES matching tables. Never import into an unrelated database.

   To combine the chunks on Linux/macOS, from the extracted backup directory:
       cat database/*.sql > database.sql
   Then use your host's database importer, or:
       mysql --user=DESTINATION_USER --password DESTINATION_DATABASE < database.sql

   On Windows PowerShell, combine bytes without changing the SQL encoding:
       $target = [IO.File]::Create((Join-Path $PWD 'database.sql'))
       try {
         Get-ChildItem .\database\*.sql | Sort-Object Name | ForEach-Object {
           $source = [IO.File]::OpenRead($_.FullName)
           try { $source.CopyTo($target) } finally { $source.Dispose() }
         }
       } finally { $target.Dispose() }
   Import database.sql using your host's database tool.

5. If the domain/path changes, run a serialization-aware replacement on the
   destination, for example with WP-CLI (test the dry run first):
       wp search-replace 'https://old.example' 'https://new.example' --all-tables-with-prefix --skip-columns=guid --dry-run
       wp search-replace 'https://old.example' 'https://new.example' --all-tables-with-prefix --skip-columns=guid
   Repeat deliberately for changed filesystem paths if your plugins store them.
   Do not replace strings directly inside SQL: serialized lengths can be corrupted.
6. Source users and passwords are restored. Sign in with a source administrator
   account. Review plugins, mail/payment integrations and background jobs before
   enabling writes. Recreate the excluded Migration plugin if required.
7. Save Settings > Permalinks; review media, links and content. Test the complete
   site before switching DNS or accepting live traffic. Keep the source backup.

TEMPORARY STORAGE
The server copy is outside the web root. Only the initiating administrator can
download it through an authenticated, nonce-protected WordPress request. Copies
expire at 24 hours and are removed when cleanup cron next runs, or on deactivation.
Download and protect your own copy before removing or deactivating Lite.

OPTIONAL FULL VERSION
In WordPress, open Migration Lite > Full version or Plugins > Buy Full version.
Shop: https://digiter.org/shop/?product=digiter-migration-pro
Choose Digiter Migration, review current price and renewal terms, and complete
checkout on digiter.org. Recurring plans require a verified Digiter Account.
Download the Full ZIP and license from your order or Customer Account. Download
temporary Lite backups, deactivate Lite, then install the Full ZIP via Plugins >
Add New > Upload Plugin. Activate it and enter the license in its License screen.
The Full edition creates separate DGM4/DGE1 packages and provides staged restore,
password protection, schedules, rollback and recovery. All Lite functions are free.
