Skip to main content

How can I troubleshoot missing data during the Cliniko to splose migration process?

Updated yesterday

When migrating data from Cliniko to splose, users may encounter issues where certain files, letters, or case notes do not transfer successfully.

This article provides an overview of common causes and step-by-step troubleshooting guidance to resolve these issues.


Overview of the Migration Process

The Cliniko to splose migration process is designed to automatically transfer patient file attachments, documents, and other data. However, certain files may not transfer due to how they were stored or categorised in Cliniko. Understanding these limitations can help identify and resolve missing data issues.


Common Causes of Missing Data

  1. Unsupported Storage Methods in Cliniko: Files stored under data types not supported by the import tool may not transfer. For example, letters or documents categorised in unsupported ways may be excluded during migration.
    ​

  2. Issues with API Key or Import Process: Missing case notes or other data may result from issues with the API key used during the import.
    ​

  3. No Retention of Previous Imports: splose does not retain copies of data from previous imports, so missing files cannot be retrieved from earlier migrations.


Step-by-Step Troubleshooting Guide

1. Check the imported data in splose

  • Review the imported patient file attachments and documents in splose to confirm what data has been successfully transferred.

2. Investigate file storage in Cliniko

  • Determine how the missing files were stored in Cliniko. If they were managed in unsupported ways, they would not have been imported.

3. Manually export and re-import missing files

  • For files that were not imported due to unsupported storage methods, manually export them from Cliniko and upload them to Splose.

4. Re-run the import with a new API key

  • If case notes or other data are missing, generate a new API key in Cliniko and re-run the import process. After re-importing, check whether the missing data appears in splose.

5. Import letters separately

  • If letters did not transfer, generate a new API key in Cliniko and run another import specifically for letters.

Re-running the import will not create duplicate records if the ClinikoID already exists in splose.


Manual Data Recovery

If certain files or data cannot be imported automatically, manual recovery is often the best solution. Export the required files from Cliniko and upload them to splose to ensure all necessary information is available.

Did this answer your question?