Any time you have a complex migration project where losing critical data isn't an option. We previously used Help Desk Migration to migrate from Salesforce Service Cloud to Zendesk, and after a seamless migration, they were the perfect partner to enlist for the migration to Odoo Helpdesk. If you need reliability, structured mapping, and a communicative team to guide you through the process, this platform is for you.
As any other archiving solution, it is very well suited for environments with a large footprint of unstructured data (CIFS / NFS shares for user data) with a large amount of unused/old files and a need to keep those unused files for long term. In our scenario, due to some legal and contractual constraints we need to keep these files for 15 years. Archiving is a good choice to move the unused files to a cheaper storage tier, both on-prem or cloud.
Transitioning work among their staff - we talked to 4 different people during the project, and ever single person was up to speed on the work and status
Overall, Help Desk Migration is very easy to use. The step-by-step migration wizard makes the process intuitive, and features like demo migrations gave us confidence before committing to the full run. The ability to create custom fields in Intercom directly within the tool was a particular highlight that saved us a lot of back-and-forth. The only reason it's not a 10 is that field mapping can get confusing in certain areas — we needed to reach out to support to work through some configurations. Better in-app guidance on more complex mapping scenarios would make it a perfect score.
Mainly used vendor PS teams and individual consultants in the past plus some more enterprise-gearer ETL platforms. Relokia's Help Desk Migration service beats them all by a massive margin due to low cost, high speed and low complexity
We have used Veritas Enterprise Vault in the past, and besides its being a well-known player on the data archiving market, their tool is far more complex to implement, to manage and to keep working. Komprise is very robust and also very easy to implement, as most part of the job is done on Komprise side. The management console is delivered through a public URL as a SaaS platform. You only need to deploy a few VMs for scan/archiving/user access, which they call "Observer VMs." Komprise also doesn't uses Stub files, which is a poor implementation adopted by the competitor for file access. We had a lot of issues in the past with stub files. Komprise has implemented 'bread crumbs', which are CIFS symlinks to the files on the Observer. It is a very good implementation and it works really well.
In terms of time spent, Help Desk Migration cut our time down to just a fraction of what it would have been had we migrated the articles ourselves. This saved us a tremendous amount of time, manpower, and overtime.
