KeyACCIDENT Data: Importing v6 3-file format data into KeyACCIDENT 2025

Issue

Our data provider still supplies data in the KeyACCIDENT v6 3-file format. How do I import this into KeyACCIDENT 2025?

 

Solution

The v6 3-file format became obsolete with the implementation of the STATS19 2024 format

There is a workaround to import data in this format into KeyACCIDENT 2025 onwards

You will need to retain a working version of KeyACCIDENT version 7 and you may find data import easier to manage if you have a separate version 7 database

Import data as follows:

1. Import the v6 3-file format data into KeyACCIDENT v7 as usual

2. Search the data and export as a KAML/KAMZ file

This is still in v7 and STATS19 2011 format

KAMZ is a compressed file version of KAML, KeyACCIDENT’s language based on XML

3. Import this KAML/KAMZ file into KeyACCIDENT 2025

4. The first import of into KeyACCIDENT will trigger the Migration Wizard

Subsequent imports from the same source should detect the format and reapply your migration options automatically

You can find guidance on the migration options HERE

5. You may find it helpful to delete the data from version 7 once you have imported it into KeyACCIDENT 2025

 

Transport for London (TfL) CollStats system

  • TfL CollStats system currently only exports data in the v6 3-file format for KeyACCIDENT users
  • TfL aims to deliver an updated CollStats system compatible with STATS19 2024 format by the end of April 2025
  • TfL plans to provide a CRASH XML format export to replace the v6 3-file format, which will simplify data provision from TfL’s CollStats
  • TfL developers will only be able to consider implementing a CRASH (XML) export after release of the STATS19 2024-compliant CollStats system, a decision to be made by their business team
  • Until then, any customers accessing data from TfL’s CollStats will need to keep a working copy of KeyACCIDENT version 7 to process the v6 3-file format data