Something looks wrong. Start here.

Looking through your files

Reading the source to find out what there is to copy. Nothing has moved yet. On a large account this stage alone can take a while, because it is a full walk of the folder tree.

Waiting, trying again in …

Not stuck. A provider asked us to slow down, so the copy is spacing its requests out and will carry on by itself. This is the normal state for a long migration and needs nothing from you.

Paused, needs a hand

The copy ran out of its own retries and stopped rather than hammering something that kept refusing. The reason it gives is passed through from whichever provider refused, so it says what actually happened. Press Resume now once the cause is dealt with.

Waiting for you to reconnect

The stored authorization for one of the accounts stopped being accepted, which happens when a grant is revoked or goes stale. Nothing is lost. Use the Reconnect link on the account, then resume the copy, and it picks up from where it stopped rather than starting over.

Finished, 3 files had problems

Everything else arrived. The files that did not are listed with the reason for each, and Retry attempts only those rather than repeating the whole job.

It has been running for days

Probably correct. Google may enforce a limit of 750 GB uploaded per account per day, and a copy larger than that is spread across as many days as it takes. Google publishes that figure for Workspace accounts and does not publish one for personal accounts, so we plan against it either way rather than discover it partway through. Once the size is known the app shows how much is left and roughly how long that is. It runs on our side, so closing the tab does not stop it.

A Google Doc arrived as .docx

Google Docs, Sheets and Slides are not files with contents to copy, so when Drive is the source they are exported to Office formats. The conversion is Google's own and is imperfect. Google also caps one export at 10 MB, and a document over that is reported as a problem rather than silently truncated.

I ran the same copy twice and got two sets of files

That will happen. A job only knows about the files it copied itself, and Drive allows two files to share a name, so a second run into the same folder does not recognise the first run's work. Check the destination before repeating a job. This one is on our list.

What each file's verification result means

Destination checksum matched means the reported digest matched a complete streamed digest or a compatible source digest. Source checksum only checks downloaded bytes. Destination size only compares a reported size. Upload acknowledged does not prove matching contents. Resumes and native conversions can have weaker evidence. Download the final manifest for every recorded check and exclusion; keep your originals until you have checked the copy.

OneDrive is not in the list yet

It is the provider we are building next. Microsoft's API supports everything the transfer engine needs, so this is work rather than a question of whether it can be done. If you want it, say so when you write in: it moves things up the list.

iCloud Drive is not in the list

Apple provides no way for a service to read iCloud Drive on your behalf, so it is not something we can add. Anything claiming otherwise is using something unofficial.

Nothing is charged yet

Flitterby is in private testing and every copy is free during it. The rates on the home page are what transfer will cost when it opens, published early so that nobody meets them for the first time on an invoice.

Credit left over after a copy

It stays on your account. You are buying transfer, not a single migration, so moving one folder now and another in three months spends the same credit rather than costing twice. Nothing expires, and only data that reaches the destination is deducted.

A copy that does not finish

Write to support@flitterby.com and say which copy it was. We would rather return the money than keep it for a copy you did not get. The terms say the same thing in the language of an agreement.

A charge from your own provider

That one we cannot return, because we never received it. Reading a file out of object storage is egress and the bill lands with whoever you copied from. It is worth checking their pricing before a large transfer; there is more about this on the home page.

Cutting off access

Removing a connection requests cleanup of its stored credential and is refused while unfinished copies rely on it. You can also revoke access in the provider's own security settings. Further authorized requests fail once the provider applies the change; a request already in flight may finish. Revocation does not remove files from either provider.

Deleting your account

Request deletion by emailing support@flitterby.com. We need to verify the request and stop unfinished work. Payment and credit records may be retained for accounting and reconciliation. See the privacy policy for what is stored in the first place.