Email support@blobward.com. We reply within one business day, and faster while a migration is running.
Email us and say "urgent" in the subject. Include your environment URL. If a migration is running and you want it stopped, say so — we can pause a job, and a paused job leaves every file it has not yet reached completely untouched.
It is in your Azure Blob Storage container, and the note in Dynamics has a shortcut to it. Open the note and double-click the attachment — it will open the file after you sign in with the same Microsoft account you use for Dynamics.
If the shortcut does not work, the file is still in your storage account. Email us with the record and we will find it. Nothing is ever deleted from Dataverse until an identical copy has been confirmed in your container.
Yes. We keep the original name, type, size and fingerprint of every migrated file, and we will move them back at no charge within 12 months. Ask by email.
One limitation: your environment has a maximum attachment size, and a file larger than that cannot be written back until the limit is raised. We will tell you if any of your files are affected before starting.
No. Every file is in exactly one of two states: fully migrated, or completely untouched. There is no half-migrated state — the original is only removed after the copy is verified, so an interruption always leaves the original in place.
Jobs resume from where they stopped. A file that was already moved is never moved twice.
Almost always because Dynamics is applying its service protection limits — your environment is busy, and Microsoft is asking us to slow down. We pause rather than fail, and pick the job back up later. You do not need to do anything, and you are not charged again.
Your completion report lists every skipped file and the reason. The usual reasons are: the file was deleted from Dynamics between the scan and the migration, the record was read-only, or the file was under 1 KB — those are left alone deliberately, because moving them would use more space than it saves.
In the Azure portal, remove the Storage Blob Data Contributor role from the Blobward application on your container. Our access ends immediately. Your files are unaffected — they are in your account and they stay there.
It can, and it is worth checking before you buy. Anything that reads attachment contents directly out of Dataverse will find a shortcut instead of the file. Anything that reads the note itself — its text, date, author, or link to the parent record — keeps working, because we never delete or move the note.
Tell us about such systems before we start and we will work around them.
Take a backup of your Dynamics environment. We are careful and we verify every copy, but nobody should modify production data without a backup — including us.