We are a small software consultancy. Several of our existing clients are unhappy with one of companies they have licensed software from (CompanyX) because that company started abusing their majority market position by increasing the prices significantly across the customer base.
Our customers are asking us if we would be able to help migrate their existing assets from the tool they currently use from CompanyX to a new tool either opensource or another commercial offering.
They are happy to share the CompanyX tool configuration files with us for the product they currently use, they hope we can analyse them and automatically migrate to a format compatible with other commercial or open source tools.
The CompanyX tool they use stores its configuration in a number of JSON files that are ZIP-ed up into one master-configuration file. Those JSON files contain instructions for the CompanyX software tool to perform certain tasks. The JSON files contain instruction and variable names that are abbreviations of the functions they represent. It is not a documented format, CompanyX does not disclose the schema of those JSON files. So we only would have samples provided by our clients.
- Is it OK to extract those CompanyX ZIP configuration files and analyse the JSON files with a script to help our clients understand the scope of the migration project they are looking at?
- Is it OK to create an automated migrator script that unzips those CompanyX ZIP files, inspects the JSON configuration files and translates them to a format that is readable by opensource tools and/or other commercial tools?
- What are the risks we face when embarking on this journey?
We are a company based in the UK. Our clients are in different countries in Europe and US. CompanyX is based in the US.