1. What is Navigate?

    Navigate is the MIB's data platform for data previously held in the Motor Insurance Database (MID). It's the central record of all insured vehicles in the UK. Navigate is managed by the MIB and used by Insurers, the Police and the Driver and Vehicle Licensing Agency (DVLA) to enforce motor insurance laws.

    In November 2025 data from the Motor Insurance Anti-Fraud & Theft Register (MIAFTR) will be moved into Navigate.

    Users can then access data from Navigate through a unified portal.

  2. What is MIPD?

    MIPD is Motor Insurance Policy Data. Every current motor insurance policy in the UK is held in Navigate and can be accessed by users from the MIPD tile in the Navigate portal.

  3. What is VS&TD?

    VS&TD is Vehicle Salvage and Theft Data currently held on the MIAFTR database. When that data is moved into Navigate, users will access it from the VS&TD tile in the Navigate portal

     

  4. What is MIAFTR?

    The Motor Insurance Anti-Fraud and Theft Register (MIAFTR) is one of the MIB’s core data services alongside Navigate (formerly MID) and CUE. It houses c.10m records of loss events (claims) related to vehicles. The Motor Insurers' Bureau (MIB) is the data controller for MIAFTR data that is currently hosted by our technology partner, Solera.  

  5. What is MIAFTR used for?

    MIAFTR was designed and developed to help monitor vehicles written off for insurance purposes, to help trace and recover stolen vehicles and to help detect fraud.

     

  6. How old is MIAFTR and why was it originally established?

    MIAFTR was established in 1987 by the insurance industry as a way of sharing data to better identify and tackle fraud. 

  7. Does the public use it?

    No. The public only interacts with the data held in MIAFTR through third party organisations that charge for checking a vehicle’s history, also called a provenance check.

  8. Why are you replatforming MIAFTR?

    Following an industry consultation, we’re transforming our data services in a phased approach. In 2024 we moved data from the Motor Insurance Database (MID) into our new Navigate data platform.

  9. What benefits does Navigate bring for MIAFTR users?

    Navigate is a modern, cloud data platform hosted in Microsoft Azure offering a unified user portal for all users.

    It provides self-serve capability, enhanced reporting and insight delivery. It also drives data ingestion improvements and better fraud detection.  

    Having data in one place means we can also continue to drive data quality improvements.

  10. When is MIAFTR data going live in Navigate?

    We’re on track to move MIAFTR into Navigate on Monday 24 November 2025.

  11. Will all MIAFTR claims data be migrated?

    Yes, all vehicle claims data held in MIAFTR will be migrated into Navigate, as well as 6 years' of personal data. 

  12. Will all MIAFTR users be migrated or will they need to sign up to the new platform?

    All existing, active MIAFTR users who have email addresses will be migrated onto Navigate.

  13. Will you be telling the industry that MIAFTR is no longer in use?

    Yes, the name MIAFTR will be retired and this is reflected in our communications. 

     

  14. When will we lose the facility to obtain vehicle finance details?

    When MIAFTR data goes live in Navigate in November 2025. After this you will need to find an alternative source for this information.

     

  15. Will reporting be available on day 1 to help with TTS

    On Day 1 the capability of self-service won’t be available for purposes of TTS however this is something we'll look into developing in future.

  16. Once MIAFTR data moves to Navigate, if there’s an issue with that data, will this affect the availability of policy data in Navigate, or vice versa?

    Data from the MIAFTR database will be moved to Navigate that already hosts Motor Inusrance Policy Data (MIPD) from the former MID.

    Migrating the MIAFTR dataset onto Navigate does imply a risk to the performance of the platform. With that in mind, we're conducting robust load testing, to assure ourselves that any performance impacts are mitigated, before we Go lLve.

    After launch, we'll closely monitor service performance.

     

  17. If we're not currently an API user when can you support us to connect? Will it be 2025?

    Please contact our engagement team at engagement@mib.org.uk to discuss available options.

  18. For those with DA access, do we also need to sign the legal agreement?

    Delegated Authorities (DAs) who only supply data (and enquire) on behalf of insurers who have already signed up to the Navigate legal agreement will not need to sign a legal agreement. 

    However,DA organisations who only enquireon behalf of organisationswill need to sign a legal agreement, so if you haven’treceived a link to DocuSign, please contact engagement@mib.org.uk. 

    Other organisations working independently who enquire on MIAFTR datawill also need to sign a legal agreement so if this applies to you, please do reach out. 

  19. Will there be SLA’s or cut off periods for interest claims being put on to Navigate by customers?

    All types of claims that are currently entered on MIAFTR will be able to be entered onto Navigate. If you are referring to something specific, please reach out to us at engagement@mib.org.uk to clarify. 

  20. Will there be any enhancements to accessing MIAFTR data when it's migrated to the Navigate platform?

    You'll access MIAFTR data (re-named to Vehicle Salvage & Theft Data) via the Navigate portal. Apart from how you log in to the new platform and a new look and feel, not much is changing to the functionality of accessing that data.

    You can watch our demo video which gives you an idea of the Navigate portal functionality. We're open to any input that would make accessing MIAFTR data in Navigate easier for all our customers, but any enhancements will be considered as part of our future, Day 2 development.

  21. When do you expect is the earliest new API connection available post Go Live?

    To assist your integration with MIAFTR V2, we currently anticipate its availability in the second quarter of 2026.

    We're committed to providing you with the finalised API specification in early June 2025 to enable thorough review and effective development planning.

Share your feedback

...