DIGITER.ORG · DOCUMENTATION

Digiter Migration Pro Documentation

Focused, release-aligned setup, workflow, licensing, compatibility, recovery and support guidance for this product.Effective date: September 8, 2026 · Version 2.4.0

Developed by Digiter TeamThis documentation explains each product's purpose, current release capabilities, operating model, normal workflows, practical use cases, compatibility, recovery, best practices and support boundaries. It intentionally excludes source code, private keys, service credentials, security bypass information, proprietary detection rules, internal thresholds and implementation details that could weaken the products or assist abuse.

12focused Digiter products

01consistent licensing ecosystem

✓private updates & protected delivery

∞documentation that grows with the products

Maintenance and corrections for every Digiter pluginDigiter plugins are complex, actively maintained systems. Although releases are tested before publication, defects or compatibility issues can occur. When a reproducible plugin defect is confirmed, Digiter addresses it through a subsequent maintained update. Update availability follows the customer’s purchased entitlement.

Account-gated Demo packages and licensed activationEvery available Demo package requires a signed-in Customer Account with a confirmed email address. It is the complete license-gated product package: without a valid license only the declared minimal function is available, and valid activation unlocks the purchased capacity without reinstalling the plugin. Customer data, license records, signing material and private release records are never included. Any authorized recipient can inspect delivered PHP files; account controls, rate limits and licensing reduce unauthorized access and use but cannot provide impossible post-download DRM.

One confirmed Account state across Shop, Chess and CommunityA WordPress login alone does not prove email confirmation. On the first Account-page visit, an existing logged-in user who is not confirmed is automatically sent one private 24-hour confirmation link for the current WordPress email. A still-valid link prevents repeated automatic mail, and the Account page provides a controlled resend action. Shop Demo access depends on that confirmed Account and an available reviewed Demo release; it does not depend on whether Chess or Community is active. Customer Account shows Chess or Community data only while the corresponding compatible plugin is active and validly licensed.

Continuous Development, Innovation & Competitive StrengthDigiter products are actively developed rather than treated as static one-time releases. In many important product segments, the current Digiter generation goes beyond conventional competing solutions through local control, hardware-adaptive execution, explainable results, integrated recovery, privacy-conscious processing and unusually broad administration from one product. This is a capability-based position, not a claim that one plugin is universally best on every server or for every workflow. Maintained releases continue to improve compatibility, reliability, security, usability and performance as WordPress, PHP, browsers, hosting environments and customer needs evolve.

← All product documentation

Digiter Migration Pro 5.2.17

Resumable backup, optional authenticated encryption, portable cross-server migration, staged restore and disaster recovery for WordPress.

Product overview

Digiter Migration Pro is designed for WordPress moves and recoveries that are too important to depend on one long browser request. The product breaks demanding work into controlled stages, records progress and uses the resumable DGM4 package format so larger sites can continue through ordinary PHP, browser and hosting interruptions.

The plugin covers the complete operational chain: create a backup, optionally protect it with a password, preserve complete integrity metadata, move or upload the package, normalize cross-server differences, restore files and database content in ordered phases, recover from an interruption and verify the result. Unlicensed Manual / Browser backup creation, download and deletion remain available; licensed functions unlock import, restore, encryption, advanced execution, scheduling, diagnostics and recovery.

Portable mode is intended for migration to a different server while preserving destination-specific configuration. Complete mode is intended for same-server disaster recovery where a broader replacement is appropriate. These explicit modes reduce the ambiguity found in one-size-fits-all restore tools.

Demo, purchase, delivery and activation

The Shop product card provides the reviewed complete license-gated ZIP only after Customer Account login and email confirmation. No license is needed for the product's declared minimal Demo function.
For a downloadable commercial plan, Digiter Shop waits for verified PayPal confirmation, issues the domain-bound signed license and sends the protected full-package download and license key to the checkout email.
The Demo and commercial delivery use the same complete license-gated product version. Activating a valid key unlocks the full installed capacity without reinstallation; the paid email link remains available for a clean copy or recovery.
Eligible Account purchases also expose current protected downloads while update access remains active. Download counts, expiry, domain and plan terms remain those recorded for the order.
Private signed releases integrate with the standard WordPress Plugins and Dashboard Updates screens. Update eligibility follows the purchased update period and does not change the permanent-use term of a Lifetime license.

Current release highlights

The current release supports optional password-protected DGE1 packages around the proven DGM4 stream, using authenticated encryption and resumable processing.
Wrong passwords, altered or reordered encrypted chunks, truncation and unexpected trailing data are rejected before rollback creation or live-site changes.
Package verification covers the complete index, record order, final manifest and payload instead of relying on a single superficial archive check.
Portable cross-server migration now covers URL/path variants, serialized and encoded WordPress values, database-engine differences, selective exclusions, capacity preflight and native WP-CLI operations.
When a reviewed license-gated Demo is available, a confirmed Customer Account can download it from the Shop product card.

Why this product stands apart

Digiter combines unlicensed basic backup creation with a professional licensed restore and disaster-recovery system instead of hiding the basic export path behind the license screen.
Resumable packaging, resumable encryption and staged restore reduce dependence on one uninterrupted browser request, a major advantage on constrained hosting.
Integrity is validated at several levels before destructive work, and restore is paired with rollback and emergency-recovery paths rather than presented as an irreversible black box.
Portable and Complete restore modes explicitly separate cross-server migration from disaster recovery, while serialized-safe replacement and database normalization address difficult real-world moves.
For many migration and recovery workloads, this combination of resumability, encrypted portability, preflight checks and reversible restoration is broader than conventional export/import competitors.

Core capabilities

Create manual browser-driven backups and licensed server-side or scheduled backup jobs depending on the active entitlement.
Build resumable DGM4 migration packages and reconstruct the complete index, record sequence, manifest and payload hashes before trusting a package.
Optionally wrap the complete package in resumable password-protected authenticated encryption when OpenSSL support is available.
Handle supported Digiter legacy package generations through the current conversion and restore compatibility layer.
Choose Portable migration to preserve destination server configuration or Complete restore for broader same-server disaster recovery.
Repair supported nested and encoded serialized WordPress values without instantiating PHP objects, and replace source URLs, encodings and filesystem paths in a structured manner.
Normalize supported MySQL/MariaDB engine, charset, collation, type and table-option differences before staged import.
Include standard WordPress tables, supported standalone application tables or an explicit all-table selection where required.
Run staged database restore and ordered file operations with automatic rollback safeguards and an emergency recovery runner.
Preflight destination storage, migration storage and locally measurable database capacity before destructive work.
Use selective media, theme and plugin exclusions plus administrator-defined serialized-safe replacement pairs for controlled packages.
Operate through browser, server-side background execution or WP-CLI according to the action and license entitlement.

Protection, integrity and recovery model

Encrypted packages are authenticated before live changes, then pass the complete native DGM4 verification path after decryption.
Plaintext backup passwords are not stored in migration settings or logs; administrators should still use a password manager and protect server backups.
Database restore uses staging before commit where supported, and the system creates a rollback package before destructive replacement.
Archive paths, declared record boundaries, expanded sizes, symlinks and active-job deletion are checked to reduce traversal, memory and partial-operation risks.
Portable mode preserves destination configuration files that should not be blindly copied from a different host, and wp-config.php is never overwritten by a migration package.
Account-gated Demo packages must be verified to keep only the declared minimal runtime available until a valid signed license is activated. Customer data, credentials, signing material and internal release records must never be included.
A downloaded WordPress ZIP remains technically inspectable. Confirmed-Account access, encryption at rest, user-bound expiring links, integrity checks, request limiting and crawler controls protect storage and delivery but do not claim impossible post-download DRM.

Administration and visibility

Export, Import, Backups, Diagnostics, Settings, Logs and License screens share a consistent administrator workflow.
Job state, current stage, resumability, failures and recovery information remain visible instead of hiding a large operation behind one spinner.
OpenSSL, storage, execution and server-capability diagnostics help identify environmental limits before a restore is attempted.
Native WP-CLI commands support backup creation, package listing and licensed restore, including password input through an environment-variable workflow.
Digiter Shop → Demo Downloads manages the reviewed Account-gated package. The current commercial release is validated and linked without a duplicate upload. Manual fallback accepts only the exact same current ZIP, version and SHA-256. Publish only after testing both unlicensed minimal mode and licensed full activation.
With an active update entitlement, signed Shop releases appear automatically in WordPress Plugins and Dashboard Updates. Manual Check now, Update now and authorized rollback remain available in the product administration.

Typical operating workflow

Before migration, update the source site where appropriate and confirm that a separate working backup exists.
Choose whether the job needs a normal DGM4 package or an encrypted DGE1 package; store the password separately from the archive.
Create a new Digiter package and allow all stages to finish before moving it away from the source installation.
Check package verification, destination storage and database capacity before starting an import or restore.
Choose Portable or Complete mode deliberately and review any exclusions or custom replacements before live changes.
Place the destination site in a controlled maintenance window when overwriting an existing installation could affect visitors or orders.
Run the restore through its staged workflow and avoid closing or interrupting recovery actions that explicitly need administrator confirmation.
After completion, verify the front end, wp-admin, permalinks, key plugins, media, forms and any site-specific scheduled or external integrations.
Keep the pre-migration and post-migration backups until the new site has operated correctly for a reasonable verification period.

Where the product fits

Moving a WordPress site between hosting providers when the administrator needs both files and database content transferred in a coordinated package.
Creating a restorable snapshot before a major redesign, plugin replacement or infrastructure change.
Recovering a site after an interrupted deployment, damaged database operation or failed migration attempt.
Handling larger sites where a single browser export, encryption request or restore would be vulnerable to PHP timeouts or connection loss.
Creating password-protected off-site or hand-carried migration packages when the archive contains confidential site data.
Moving between different MySQL/MariaDB and hosting environments where URLs, paths, collations or server configuration differ.
Maintaining a repeatable backup-and-restore procedure for sites managed by an agency or technical administrator.

Operational considerations

Backup success is not proven until a restore path has been tested. Administrators of important sites should periodically verify that their packages can be read and restored in a disposable environment.
A migration can change URLs, filesystem paths, database credentials, PHP capabilities and server behavior at the same time. Post-restore testing should therefore cover both WordPress and the surrounding hosting stack.
Free disk space is required for package creation, extraction and rollback data. A server that is nearly full can fail even when the final site itself would fit.
Large database tables and media libraries can extend operation time. The adaptive engine reduces pressure but cannot override hard provider limits or insufficient storage.
Do not delete the only known-good source site or backup immediately after a successful-looking migration. Preserve a rollback path until functional verification is complete.
This is a complex, actively maintained WordPress plugin. Despite pre-release testing, reproducible defects or compatibility issues can occur; confirmed product defects are corrected through maintained updates according to the customer’s active update entitlement.

Compatibility and environment

The product targets modern WordPress/PHP environments and records product-specific minimum requirements in the Shop catalog and plugin package.
Host limits such as execution time, memory, file size, process restrictions and free disk space still apply. The resumable design reduces exposure to those limits but does not make them disappear.
Security plugins and web-server rules can block archive upload, extraction or recovery requests. Temporarily adjusting a conflicting rule should be done only by an authorized administrator and restored afterward.
Encrypted backups require supported OpenSSL capability. A forgotten password cannot be recovered by Digiter, so password custody belongs to the administrator.
Cross-version or legacy-package restore depends on the compatibility support built into the current release; unsupported archive formats should not be forced into the restore process.

Recommended best practices

Create at least one independent backup before overwriting a destination site.
Perform major migrations during a maintenance window and suspend content/order changes if data consistency matters.
Check PHP version, available storage and important plugin requirements on the destination before beginning the transfer.
After restore, regenerate permalinks and verify forms, email, scheduled actions, ecommerce callbacks and external API credentials.
Keep backup archives protected from public download, use encrypted packages for sensitive transfers where appropriate and remove obsolete copies when they are no longer needed.

Privacy, security and implementation boundary

Migration packages can contain the entire WordPress database, uploads and configuration data, which may include personal or confidential information belonging to the site. Package handling is therefore an administrator responsibility and archives should be treated like a full site backup. Archive layout, recovery sequencing internals, serialization handling and proprietary compatibility logic are intentionally not disclosed because they are implementation-sensitive.

Support and troubleshooting

For backup, import or restore trouble, contact [email protected] with the plugin version, source and destination WordPress/PHP versions, package size, operation stage and sanitized diagnostic message. Never send a full customer database or configuration containing secrets unless a secure support procedure has been explicitly agreed.

Current Shop release reference: 5.2.17Automatically synchronized from the current Shop release. Capabilities may expand through maintained releases while the purchased entitlement continues to be governed by the selected license plan.

Licensing, updates, support and ownership

A Digiter purchase grants the usage entitlement described by the selected product plan. It does not transfer copyright, source code ownership, trademarks, design rights, private signing material or proprietary implementation knowledge. Lifetime plans, where offered, refer to the stated software-use entitlement; update periods are shown separately in the Shop and purchase record.

Hosted Smart Cloud Monthly is an Account-bound service and is operationally different from a downloadable domain license. Standard plugin purchases may be completed as a guest where the Shop allows it, while Account-based purchases can remain associated with the verified Digiter Account.

Protected downloads and private updates are delivered through the Digiter Shop licensing system. Customers should retain their purchase email and license information and should not publish license keys publicly. For setup, licensing, delivery, update or product questions contact [email protected]. Digiter Team will investigate verified issues and work with the customer toward a practical resolution.