# Migration When updating from older versions (pre NavigaID) you might need to migrate the old lists/packages you currently have. This due to lists now supporting other types (lists/packages) within lists. We also have a requirement on NavigaID data in the document to know who created it and which org/unit it belongs to. ## Item type With the functionality to allow multiple types in lists all items need a type attribute in order to determine which content type it is. In the example below we have an old list without types and below that a migrated one which specifies one of the types \[Article, Package, List] ```markup Example list list ``` ```markup Example list list ``` ## NavigaID data In order to be able to display the lists and packages in an NavigaID enabled environment they need to have the required data in the document itself. Below is an example of the data that needs to be added with units/orgs and how it looks in the full example ```markup ``` #### List ```markup Example list list ``` #### Package ```markup Example package Daily 2019-08-08T07:40:23.000Z draft ``` --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.navigaglobal.com/oc-list/master-2/admin/migration.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.