Before Exporting From OPPSA

The first step in the conversion process is exporting the data out of OPPSA to prepare it for conversion into EZ Config Default Data.

OPPSA's Export function allows users to export OPPSA Organizations, Policies, and Products. Each Organization, Policy, and Product is exported as a separate XML formatted file and all files are combined into a single ZIP file.

Before You Begin

  • Users must have System Administrator privilege to export data from OPPSA.
  • Users can export files only for Organizations to which they have access.
  • The Export function produces an XML file for each item selected and combines all XML files together into a single ZIP file.
  • Export only those files that need to be converted in EZ Config Default Data. The exported filenames are named based on the name given in OPPSA. The exported file names do not indicate whether they are organization, policy, or product unless this information was included as part of the naming convention used when setting up OPPSA. As a result, we recommend exporting the organizations, policies, and products separately and into separate subfolders named accordingly to assist with identification, especially if the user performing the conversion function is not familiar with the naming convention in OPPSA.
  • If the export includes policy and product files, the organization file must be included. The organization will be imported before creating the policies and products.
  • EZ Config Default Data does not use the same hierarchical structure for Organizations or Accounts in the way that OPPSA does. In OPPSA, users are granted access rights to Organizations within the hierarchy. Within EZ Config Default Data, the Account controls user access. If you have multiple organization levels in OPPSA, you may wish to discuss with Professional Services how to set your Organizations and Accounts up within EZ Config Default Data, as you may need to have multiple Accounts to support your needs.
  • Review your Organization structure within OPPSA and make any necessary changes prior to exporting data to ensure that you do not have duplicate organization names. The Conversion does not support duplicate names, so it is more efficient to change the names, if necessary, in OPPSA prior to exporting the data.
  • Make any other necessary changes to OPPSA (adding new Product, etc.) prior to exporting data to avoid additional clean up tasks once the data is converted.
Note: The size of the resulting XML files may vary significantly depending not only on the complexity of your Organization structure, but also the number of Policy and Product files you must convert. The Export function in OPPSA is limited on size, so it may be necessary to export your data files in segments instead of all at once. If you receive an error indicating the file is too large, cancel the export and retry with a subset of data. Specifically, the Policy export is most likely to require multiple exports. A possible breakdown of the data might look like the following:
  1. All Organizations
  2. All Policies except Terms and Conditions
  3. Terms and Conditions Policies
  4. All Products
Note: Because there is no standard size of Organization, Product, or Policy, we cannot define how many objects your export should include. You may be required to experiment to find the appropriate number of objects to include for your export.