Support

What to include in your message

• The site address the plugin is installed on.
• The MigratePress version, the WordPress version and the PHP version (all shown on the plugin's status screen).
• The storage destination involved — Google Drive, Dropbox, OneDrive, S3, and so on.
• The exact error text, and roughly when it happened.

Common questions

Connecting Google Drive asks for no API keys. Is that safe?

Yes. MigratePress holds one registered Google application so you do not have to create one. The authorisation is completed on our sign-in service, the resulting tokens are handed to your site once and then deleted from our side, and they are stored encrypted in your own database. The scope requested is drive.file, which reaches only the files MigratePress creates. The full flow is described on the Google user data page.

A backup stops part-way through. What now?

Large sites upload in chunks and resume automatically, so first let the schedule retry. If it keeps failing, send us the job log from the plugin — it names the file and the byte offset where the transfer stopped, which usually identifies the cause immediately.

My Google connection stopped working after about a week.

That is the signature of an OAuth consent screen left in "Testing" mode, which expires refresh tokens after seven days. If you are using your own Google application, publish it to production and reconnect. Connections made through the MigratePress sign-in service are not affected.

Can I use my own storage application instead?

Yes. Every provider that supports sign-in also accepts your own client ID and secret, and the S3-compatible destinations always use your own access keys.

How do I remove MigratePress and everything it stored?

Follow the steps on Delete Your Data & Revoke Access.