# Migration to v2 and entry \_ids

**URL:** <https://discourse.getcockpit.com/t/migration-to-v2-and-entry-ids/2846>\
**Category:** Support\
**Created:** [July 26, 2023, 4:30pm UTC](https://discourse.getcockpit.com/t/migration-to-v2-and-entry-ids/2846 "2023-07-26T16:30:39Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![seank1968](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.getcockpit.com/seank1968/32/1002_2.png) [@seank1968](https://discourse.getcockpit.com/u/seank1968)\
**Post date:** [July 26, 2023, 4:30pm UTC](https://discourse.getcockpit.com/t/migration-to-v2-and-entry-ids/2846/1 "2023-07-26T16:30:39Z")

</div>

Currently using v1 as a database from which I’m pulling data into a php based website via the api using the entey \_id to identify the data.

I want to start using v2 but I’m not sure about migrating the data.

For example, I have a collection called ‘staff’ with fields ‘first\_nane’ and ‘last\_name’

John Smith has the \_id ‘abc123’

Can I import the data from v1 onto v2 and keep the existing \_id values for the imported enties in v2? Or will I have to let the system create the \_id?

---

<div class="post-metadata">

**Author:** ![raffaelj](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.getcockpit.com/raffaelj/32/331_2.png) [@raffaelj](https://discourse.getcockpit.com/u/raffaelj)\
**Post date:** [July 28, 2023, 8:09am UTC](https://discourse.getcockpit.com/t/migration-to-v2-and-entry-ids/2846/2 "2023-07-28T08:09:18Z")

</div>

You can keep the old `_id`.
