Replies: 2 comments 2 replies
-
It would be pretty difficult to do so with all the secondary keys linking back to other tables. My recommendation would be to create a bulk import file of your existing endpoints from the old system and use the bulk import option in the ispk manager gui to import them into the new system. This way it would properly populate all the linked table data. |
Beta Was this translation helpful? Give feedback.
-
So, what I eventually did was to export all the endpoints together with groups to a csv file, and based on this file to prepare individual groups csv files to be imported. The last step was to copy some endpoint attributes from old to the new DB using a python script. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, I am using the old iPSK manager version for production (2019 version) and now I'd like to move to the newest version that I installed/configured from a scratch. Is there a way to copy the endpoints between the two databases, keeping all the endpoint-related tables?
Beta Was this translation helpful? Give feedback.
All reactions