Frequently asked questions
The questions we are asked most, answered plainly. If yours is not here, ask us.
Pricing and licensing
How much does it cost?
€499 plus VAT per Microsoft 365 tenant. It is a one-time purchase with a perpetual licence: no subscription, no per-gigabyte charge, and no per-user pricing. Registered MSPs get 25% off every tenant licence.
What does one licence cover?
One Microsoft 365 tenant, for life. The tenant is the destination you are migrating into. If you migrate into three separate tenants, that is three licences. All sources are included in the one price, so a licence is not tied to Datto, local storage or anything else.
Is it genuinely one-time, or does it renew?
One-time. The licence is perpetual and does not expire. There is nothing to renew and nothing to cancel.
How does the MSP discount work?
Register as an MSP and we issue you a discount code to enter on the Stripe payment page, for 25% off every tenant licence, with no minimum commitment and no expiry on the code. Register your MSP here.
How is VAT and payment handled?
Purchases are processed securely through Stripe: complete the purchase form and you are taken straight to a secure Stripe Checkout page to pay, where Stripe also calculates VAT for your location and generates your invoice. Your licence file(s) are generated automatically and emailed to you as soon as payment completes.
Trying it out
Can I try it before I buy?
Yes, on your own real data. Without a licence you can connect, list your projects, run a full Preview and Compare sizes as often as you like, and copy up to 20 of your own files for real into your own tenant, then run Verify on them so you can watch them land and check them. It is a sample, not a full migration, but it answers the only question that matters: does it move my data correctly.
What is the difference between the trial and a demo?
The trial is you running an evaluation build against your own environment. The demo is a live walkthrough with us, where we connect to a supported source and show you a migration end to end. Either is a fine place to start.
Support
The licence is perpetual, so is support forever?
The licence is perpetual; support is not open-ended. Software support is included and we intend to support the product for as long as it is in active use, but a perpetual licence is a licence to keep using the version you have, not a guarantee of indefinite support or updates. The support policy sets out the detail.
What if I need help during a migration?
The tool has a built-in support option that bundles the run's log and report into an email to us, so we are looking at what actually happened. Chargeable migration consultancy is also available if you want a run planned or delivered with you.
Using the tool
What is the difference between Upload and Sync?
Upload all files is the first full migration: it copies everything and overwrites the destination with the source version. Sync new and changed is a top-up: it merges into what is already there, adding new files or updating where the source is newer, and it never deletes anything. A typical job is one Upload, then Sync each night until cutover.
Does Sync ever overwrite a file at the destination?
Only if you tell it to. Sync new and changed offers a choice every time you run it: Add new files only, which never touches or overwrites anything already at the destination, or Update where the source is newer, which replaces a destination file only when the source copy has a later modified date. A destination file that is the same age or newer, for example one someone has since edited directly in SharePoint, is left alone either way. Sync never deletes. Upload all files is the one action that overwrites unconditionally, and it is meant for the first full pass, not a top-up.
Can I stop a migration partway through and pick it up again?
Yes. Pause a run and Resume it later, or Stop it outright, either way the tool always finishes by writing a report from the audit trail, so you never lose the record of what happened. A resumed run continues in the same mode it was paused in and does not repeat work it has already done.
What happens if a migration is interrupted unexpectedly, a reboot, a dropped connection, or the app just closing?
Nothing is lost. Reopen the job and run Sync new and changed: because Sync compares the source against the live destination rather than a stored record of what a previous run thought it had done, it always knows exactly what is genuinely still missing, however the previous run ended.
Can I run more than one migration from the same computer?
Yes. Each migration is its own job, usually one per client, with its own mapping, logs, reports and state, so jobs never interfere with each other on the same machine. Several projects within one job can also migrate in parallel, each in its own process with its own connection.
If some files fail, do I have to rerun the whole migration?
No. Rerun failed files only re-copies just the files that failed in the last run, taken from that run's own record, and leaves everything that already succeeded untouched. It becomes available after any run that reports a problem. See what happens when files fail, and how to fix it for the common causes and how to catch them early.
Which sources are supported?
Datto Workplace and local or network file storage are supported today. Box, Dropbox, and Google Drive and Shared Drives are on the roadmap. The same interface, licence and reporting apply to every source. See the current list on the product page.
Where do I see a full account of what a migration did?
The per-file audit record, the authoritative account of every file's outcome, copied, skipped, failed or repaired. Every report, and the certificate and provenance pack, are built from it. See understanding your audit trail and reports for what each report contains and where they live.
What does not come across?
Two things, because they are a function of what the source APIs expose rather than the tool. Version history from the source is not carried across; the API exposes current content only. Source share permissions are not applied at the destination; the tool can produce a read-only permissions plan for you to review and apply deliberately, but it never writes permissions itself. If either matters for your migration, plan for it up front. More on why, and what to do about it.
How long will a migration take?
Usually less about your internet connection than about the source API's rate limit. Liscaragh Migrate learns each source's fastest sustainable rate at run time and adapts to it, and it estimates duration from measured throughput rather than bandwidth. A run can be scheduled for a set time or restricted to a nightly window, resuming as a Sync each night until the job is done. This is a scheduler built into the app rather than a Windows scheduled task, so the app needs to stay open and the machine awake while it runs. See our note on running a large migration without anyone in the office noticing.
Requirements and data handling
What do I need to run it?
A Windows machine, PowerShell 7 (the installer adds it if it is missing), the Microsoft Graph module, and a Microsoft Entra app registration in the tenant you are migrating into (a one-time setup, guided by the tool). No admin rights are needed on the machine to install the software itself. Setting up the app registration is a Microsoft 365 requirement rather than something the tool adds, so that one-time step does need a Microsoft 365 admin account, ideally just for the few minutes it takes the guided wizard to run. You also need your source credentials, entered in the app on first run.
What are the hardware and operating system requirements?
Windows 10 or 11, and PowerShell 7.2 or newer, which the installer adds for you if it is missing or too old, installed into your own user folder with no admin rights needed. There is no unusual RAM requirement, because the tool streams one file at a time rather than holding a migration in memory, so demands do not scale with the size of what you are migrating. Disk space works the same way: the temporary folder only ever needs room for your single largest file, not the whole estate, since exactly one file is ever staged on disk at once.
Does my data pass through your servers?
No. Liscaragh Migrate runs entirely on your machine and moves data directly into your tenant. Nothing routes through any Liscaragh infrastructure. Validating a licence needs no network call; the one exception is a periodic revocation check against a public list on GitHub, which carries no tenant data and fails open if it cannot be reached. The security page covers this in full.