With the announcement of the LCQ sunset decision in November 2023, many subscribers have asked: how do I get my data from LCQ into another software platform? 

When considering data migration you’ll first need to determine the needs for your data. For example, do you need all historical data in the platform you are moving to? Can you use the SQL file provided by LCQ as a data source for your reporting system? Which users need access to LCQ data and how?

Migrate Data to a new Platform

There are several ways that data can be moved from LCQ into another platform, via Excel (or .csv), API, or SQL file. As noted in the sample transition plan, when reviewing alternative software platforms you should ask how data can be imported into the system. And, if they are able to provide any technical expertise to assist with data migration requirements.

Excel (.csv)

Excel download and import is the least technical method. You can download your data from LCQ via a process view. Please ensure you include all the fields required in the view. Note that you may have to create multiple views as there is a 50-column limit for process views. Review these support articles for more information https://support.rpmsoftware.com/support/solutions/articles/12000070399-process-views, https://support.rpmsoftware.com/support/solutions/articles/12000025691-view-download.

The downside of Excel is file attachments will need to be downloaded manually one by one from LCQ and added to the new platform.


LCQ has an API that can be used to get your data out. The API is a good data migration option if the alternative platform also has an API. Please see the LCQ API documentation paying particular attention to the ProcForms, ProcFormFile, and ProcViews endpoints. These endpoints are likely what you will use to get data out of LCQ. 

To utilize this method, you will need a developer who is familiar with APIs and API program development. The software that you are moving to may have internal resources that can assist. The LCQ system administrator will also need to be involved as there will likely need to be an order for data input into the alternative system. For example, you will want to import reference lists such as organizational structures or assets first. 

SQL or Database Migration

LCQ is providing subscribers with an SQL file that contains all data. This file can be used as a data source to migrate data to another database. The SQL file can be considered a flat file as there are very few relationships defined and no entity relationship diagram included. Although, using your LCQ subscription and direction from the LCQ system admin, or simply from the process and field names, data relationships can be discovered.  For example, if you have a process called Assets and you have an Inspection process with a field name of Asset, you would be able to determine that there is a relationship between Assets and the Inspection process.

The SQL or database migration method will require the use of a Data Migration Service such as AWS (https://aws.amazon.com/dms/) or Table Plus (https://tableplus.com/). And, you will need a developer with experience in extracting, transforming, and loading data.


LCQ support is here to answer questions and discuss data migration options. Email the respective support email for assistance.