Terms of Service

What we change in your system

This is the part to read carefully, because we modify records in your Dynamics environment. For each attachment we migrate:

• the file contents are removed from the note and replaced with a small shortcut
• the note's file name gains a .url suffix
• a line is added to the note's text saying where the file now lives
• a new record is created holding the file's location and fingerprint

The note itself is never deleted. Its link to the parent record, its author, its date and its position in the timeline are unchanged.

What this means for you: anything that reads attachment contents directly out of Dataverse — a report, an integration, another vendor's app — will find the shortcut instead of the file. If you have such a system, tell us before we start.

Our promise about your files

We never delete an original before the copy is proven. Every file is copied to your container, read back out of it, and checked against the source fingerprint. Only if those match do we touch the note. If anything fails at any point, your original is left exactly as it was and the failure is reported to you.

Files that cannot be migrated are recorded and skipped. The job continues. You get a list of every one of them.

Reversal

Every migrated file keeps a record of its original name, type, size and fingerprint. If you want to move files back into Dataverse, we will do it at no charge within 12 months of your migration, subject to your environment's file size limits allowing it.

Pricing and refunds

The price is set by the volume found in the free scan. If the volume in your environment has changed significantly by the time the migration runs, we contact you before starting rather than proceeding at the wrong price.

If the migration has not started, you get a full refund on request. If it has started and fails through our fault, you get a full refund and we reverse anything already moved. If it completes, the work is done and the fee is not refundable.

What you are responsible for

• Having a working backup of your Dynamics environment before we start. We are careful, but you should never let anyone modify your production data without one.
• Owning the Azure storage account and paying its costs, which are yours directly.
• Having the authority to authorise this change in your organisation.
• Telling us about systems that read attachments directly, before we begin.

Limits of liability

We are liable for losses we cause through our own failure to follow the process described above, up to the amount you paid us for the migration. We are not liable for losses arising from your environment being unavailable, from Microsoft or Azure outages, from a missing backup, or from systems we were not told about.

Nothing here limits liability that cannot legally be limited.

Support

Email support@blobward.com. We answer within one business day. During a migration, we answer faster. See our support page.

Governing law

These terms are governed by the laws of the Netherlands, and disputes are heard in the Dutch courts.