Questions And Answers

Movebase backs up the database, uploads, themes and regular plugins, excluding Movebase itself. WordPress core, wp-config.php, root files, must-use plugins and drop-ins are not included. Keep separate copies of custom server configuration and anything outside this scope.

New backups target 256 MiB of uncompressed archive records per part. Compression changes the downloaded size. Download every numbered part from the same backup and keep the names unchanged. The backup card shows their combined download size. Update Movebase on the destination before importing newer backups.

Background work can continue when the host allows loopback requests and runs WordPress scheduled tasks. This is not guaranteed on every host. Browser uploads need the page and connection to remain available. Reopen Movebase to check progress; keep it open if background work stops.

Cancel backup stops an unfinished backup at a safe checkpoint. Delete this backup removes a completed local backup after confirmation. Cloud cancellation keeps objects already uploaded; these may need removal from your storage account. Cancellation is not restore rollback.

Pause changes until the backup finishes. Movebase does not create a transactionally consistent snapshot across a changing database and filesystem. A successful export does not guarantee consistency if orders, uploads or edits continue.

Pause website edits, scheduled updates and file-writing jobs, then start a fresh backup. Do not delete the named source file just to bypass the error. Keep the previous completed backup until a replacement is verified.

Transfer and verification are separate. A row can show 100% transferred while its ZIP is waiting to be checked. The main percentage describes the current stage. Restore becomes available only after verification succeeds.

Select every original numbered ZIP from one Movebase backup. Do not extract, rename or mix parts from different backups. Download a damaged or incomplete part again. If the original archive is damaged, create a new source backup.

Update Movebase on both websites and retry the saved checkpoint. Use backups created by Movebase; arbitrary ZIPs and other backup plugins are not supported. If the error remains, retain the backup and share a Logs report rather than modifying the manifest.

Check hosting disk space and file-count quota, then ask the host to verify PHP temporary-upload directory permissions and upload limits. Keep the original ZIPs. Do not remove WordPress files or Movebase recovery folders to make room.

Yes. Open Restore → Uploaded via File Manager and choose Find server backups to see Movebase’s private folder. Upload all numbered parts there without extraction or renaming, then choose Find server backups again. Do not place sensitive backups in a publicly accessible folder. Keep a separate copy; import moves files into verification storage.

Select the same original files and use Resume upload when offered. Confirmed chunks are retained. If Movebase reports different file identities, locate the original ZIPs rather than forcing a mismatched upload.

Yes. Install Movebase on the new WordPress site and restore your backup there: upload the ZIP parts, use your host’s File Manager, or pick it from your cloud storage. Movebase updates the site address everywhere it appears, including serialized settings, and converts standard table prefixes. Sign in afterwards with an administrator account from the old site.

Usually, yes. While it works, Movebase raises the PHP memory limit to the one WordPress uses for its admin screens (256M by default). If your host locks the limit, restores still work down to about 56M. If PHP runs out of memory, Movebase pauses and keeps your progress: ask your host to raise memory_limit, then click Continue from saved progress. Settings shows the memory available for backups and restores.

Yes. Open Backups and choose Restore backup on the saved backup card. Movebase prepares a separate working copy, verifies it and asks you to confirm the destination before replacement. The original backup stays in Saved backups. Temporary space is needed for preparation and recovery. If WordPress cannot open at all, first recover dashboard access through your host or restore the backup on a working WordPress installation.

Restoration replaces database users with the source website’s users. Use a source-site administrator account if prompted. Sign in again opens the destination WordPress login page; it does not send your password to Movebase. The completion modal does not automatically log you out.

It confirms that Movebase installed the files and database. Check pages, images, forms, checkout, admin access and permalinks. Plugin activation is opt-in, and compatibility is not guaranteed. Keep recovery copies until the restored website is accepted.

Sign in again and reopen Movebase to check the saved job. A session change is not proof that the restore is complete or failed. Do not start a second restore until you know the current job’s state.

A host timeout or an active worker can temporarily prevent a response. Wait briefly and use Refresh status. If the count advances, work is continuing. If it stays unchanged, check host limits and copy Logs. Use Continue from saved progress when offered; avoid repeatedly launching new jobs.

The host could not save progress. Check free disk space, file-count quota and private-directory write permissions with your host. Do not delete restore journals, staged files or rollback data. Once the underlying problem is resolved, refresh status and use the saved checkpoint.

ZIPs are compressed. Restore can hold downloaded archives, extracted data, staged files and previous-destination recovery copies at the same time. Disk capacity and file-count quotas are separate. Direct-to-cloud reduces backup working space, not restore space.

Keep the backup and recovery data. If WordPress cannot open, use the host’s File Manager to rename only the specific failing plugin folder to disable it, then sign in. A required theme plugin may need a complete, matching-version copy from the source or trusted vendor. Avoid merging different plugin versions. Earlier archives that omitted plugin code need a fresh source backup. Ask for help before changing database tables.

Use a compatible destination core. Movebase can handle supported forward database upgrades, but does not include WordPress core and cannot promise plugin compatibility. Backups from newer core cannot be restored onto older core through this workflow. Retain downloaded files and retry after resolving the version check.

Current Movebase supports generated columns and supported named foreign keys. Some schemas remain unsupported: views, triggers, non-InnoDB tables, unsupported constraints, external relationships and tables without required primary keys. Update both connectors and share the exact table-specific error with your developer. Do not drop constraints or tables simply to bypass a backup check.

Use Recover previous destination when available and confirm the destination URL. Recovery replaces changes made since restoration. Delete backup and recovery copies only after checking the website and keeping a separate backup; deletion removes that rollback option. Do not delete private job directories manually.

Directly to storage uploads and verifies completed parts before releasing temporary part space. It needs at least 576 MiB working space plus growing inventory and hosting overhead. Keep a local copy and upload retains a complete local backup as well. Neither option removes the space needed for restore and recovery.

Check the provider, HTTPS endpoint, bucket, region and access-key permissions. The account needs permission for the operations Movebase performs, including reading and writing backups. Check hosting outbound HTTPS access. Do not share access keys or secret keys in support messages.

Check the selected account, bucket and backup folder. Completed backups appear after publication; a cancelled or incomplete transfer may leave remote objects without a completed catalog entry. Use Continue transfer or retry when available. Do not delete cloud files while a transfer is using them.

In Storage → Connection, use the Download connection file icon to save a password-protected connection file. On the other website, use Upload connection file, enter its password, review the filled settings and click Connect. Keep the file and password separate.

For S3-compatible accounts, put all original numbered ZIPs in the configured backup folder’s imports/ directory, then use Cloud backups → Find uploaded ZIPs. Verification still checks completeness.

Open Logs, refresh, then use Copy logs or Download report. Copy includes the complete loaded report even if the table is filtered. Include the exact displayed error, the stage, plugin version and whether counters still advance. Reports exclude passwords, storage keys and website content, but review any screenshots or extra text before sharing.

No backup tool can promise that. Movebase supports single-site installations within its configured limits and requires PHP ZIP, SQLite3 and 64-bit PHP 8.1+. Hosting quotas, background jobs, database schemas and third-party plugins affect results.

Storage for your Movebase backups that we run for you, so you do not need your own bucket or keys. One account covers any number of your WordPress sites, and all of them share your plan storage.

No. Backup, restore and migration are free in the plugin, and you can keep backups on your server or connect your own IDrive e2, MEGA S4 or S3-compatible storage. Movebase Cloud is optional.

By the total size of the backups you keep in Movebase Cloud, across all your sites. Deleting a backup frees its space right away.

New uploads stop until you delete older backups, upgrade, or add extra storage. Backups you already have stay safe and restorable.

Upgrading to a bigger plan applies as soon as you pay the difference for the rest of your current period. Moving to a smaller plan starts at your next renewal: you keep your current storage until then, with no refund for the time already paid. Your stored backups must fit in the smaller plan.

Yes, shortly after a payment, if you have used little of the storage since paying. When a payment qualifies, a “Request a refund” button appears in Plan & billing. Your plan ends when the refund is made. The exact time limits are in the Terms of Service.

Yes, from Plan & billing. Your plan stays active until the end of the period you paid for. After it ends you have 30 days to download or restore your backups before they are deleted.

With an S3-compatible storage company we contract with. Each account has its own private folder, and your sites only ever get short-lived links for their own files, never storage keys.