Selecting Import Configuration from the Administration Menu will take you straight into a file browser. Select the configuration file you wish to import, and continue. You will be taken to the Import Configuration form. At this point you can press Choose Files to change the configuration file you will import, or Upload to continue with the import.

After selecting the configuration file, a form will appear to enter a password to import encrypted fields. This is the password which was set during export. If no password is entered then no encrypted data will be imported.

If Publish Streams is ticked, publishing will be run at the end of the import. This means that changes to streams and stream attributes will be applied to the stream data tables in the database. If publishing fails, the import will still complete successfully, and the publishing errors will appear in the console. See also Publishing Streams.

When import is complete log messages in System Console will list which objects have been imported.

If translation is configured, audit trail changes to drop-down field now have the translated name of the option.

PhixFlow will automatically start to rebuild its database DTO caches when the import completes. We recommend that you run large import processes during periods of low system usage, for example overnight. This gives PhixFlow time to complete the import and rebuild the caches without affecting the performance seen by users.

Passwords

Passwords Saved in PhixFlow

Exported files do not include any passwords from the PhixFlow system, such as passwords for:

user accounts
accessing external data, for example using file or HTTP collectors and exporters or FTP sites.

If you are planning to import an exported configuration to another PhixFlow instance, you may need to update the passwords in that instance.

Providing a Password to Encrypt the Exported File

By default, when you download an exported file, it is encrypted. You must provide a password that you can then use when you import the file into another instance.

Importing Users to Another Instance

In 8.3.1 and Earlier Versions

PhixFlow exports/imports references between user groups and users. When you import to another instance:

existing local and mixed users have their user groups, roles and privileges overwritten
any new local or mixed uses that are created with the same user groups, and therefore roles and privilages, as the source instance.

In 8.3.2 and Later Versions

PhixFlow treats user roles and privileges as instance-specific. For this reason, exports from a PhixFlow instance do not include the references between user groups and users. When you import to another instance:

existing local and mixed users retain their user groups, roles and privileges unchanged
any new local or mixed uses that are added do not have user groups, roles or privileges set by the import process. You will need to set appropriate user groups, and therefore roles and privilages.