In typical v16 deployments most filters are at the user level and being imported with the users from a source table in automated fashion as part of a scheduled job. The task can be recreated for v17 to import a user listing & filters from a properly formatted excel file. There is some setup for sure, but once done it's a one time thing to get the bulk of your users and filters into v17. Conditions are typically smaller in number and manual conversion is doable.
No export from 16. I'm just saying a best practice with v16 was to manage your user listing in a external table be it Excel or a QVW table object which sourced it's data from a user directory service. Once properly formatted you would automate the import process and keep user changes in sync as opposed to manually creating users and filters in Nprint. In this scenario rebuilding for v17 is minimal work because you simply need to populate an excel table with the users and their filters which you would already have.
