Conversion Workflow

  1. Ensure the approprate content is loaded to your Account. Professional Services or your System Administrator will create the Account within Security Administration and create users. Your Professional Services Rep or System Administrator will use DGS Management to assign the Deposit content to your account.
    Important: This Conversion is designed to work with the Deposit Content dated May 2021 or later. You should reference the Content Release Notes for any additional changes.
    Note: There is an issue with the May 2021 content release that requires you to remove the following datapoint from the Default Data Privacy Policy REQ. This issue will be resolved with the July 2021 content release. /Txn/Deposit/Accounts/Account/AccountPurposeType = '1'
  2. Establish appropriate user permissioning and access. Confirm the appropriate user(s) for your organization have access to the Conversion functionality.
  3. Specify your Account Details within EZ Config Default Data. This step ensures that the account details can be applied to those organizations and policies as they are created by the conversion process.
    Note: In order for the conversion to process correctly, it is important that you complete the Account Details information prior to running the import and conversion process.
  4. Export the Organizations, Policy, and Product data files from OPPSA that you wish to have converted to EZ Config Default Data. Consider breaking the data into smaller exports if you have a large amount of data to convert.
  5. Convert data in EZ Config Default Data.

Order of Data Conversion

Note: Technical Note: The process of converting data from OPPSA to EZ Config Default Data first verifies that the EZ Config Default Data REQ exists in the selected content before attempting to import the Organization, Policy, or Product information. If the REQ file is not located within the selected content, the conversion displays a "File Not Found- Did Not Import" message.
The conversion of data from OPPSA to EZ Config Default Data occurs in the following order.
  1. Creates Organizations.
  2. Removes organization data points that do not exist in EZ Config Default Data.
  3. Creates Policies, which includes the following components:
    • Applies Account Details (jursidictions) to Organizations and Policies.
    • Creates the related applicabilities for the Policies.
    • Moves data to the Organization or other Policies.
    • Removes the Policy data points that do not exist in EZ Config Default Data.
    • Creates Products. The Conversion Details page displays the status for each product after it is converted or if conversion is not successful.
  4. Links the Policies to the Products. (All noted policies have relationship to product created if the policy exists.)
  5. Creates related applicabilities for the Product. (Display on the Product Applicabilities card and on the Assign Applicabilities/Policies page.)
Note: Please note the following conversion exceptions:
  • When converting a Forms Setup Policy from OPPSA, the conversion creates two policies within EZ Config Default Data - a Document Setup Policy and an Account Document Setup Policy. Both of these Policies will be named the same as the Forms Setup Policy in OPPSA.
  • When converting a Truth in Savings Act - Savings or Truth in Savings Act - Checking or Truth in Savings Act - Time Policy from OPPSA, the conversion consolidates these three policies into the same policy type in EZ Config Default Data.
  • When converting an Account Agreement and Safe Deposit Box Lease (SDBL) Policy, the conversion moves the data from the policy to other policy types or the Organization. The following message displays: "Policy Not Created - Data Moved."
  • When converting an IRA/HSA/CESA Policy type from OPPSA, the conversion moves the data from the policy to the Organization. The following message displays: "Policy Not Created - Data Moved."
  • When converting a Substitute Checks Policy type from OPPSA, the conversion moves the data into the Substitute Check Policy (no 's') in Default Data.
  • When converting a Privacy Notice Policy type from OPPSA, the conversion moves the data into the the Privacy Policy in EZ Config Default Data. (Note changed name.)
Note: Due to the logic in which EZ Config Default Data data points are captured verses the logic in which data is collected within OPPSA, there may be certain scenarios in which the OPPSA Conversion process can not successfully transfer data into EZ Config Default Data policies.

In some instances the conversion of the data items is dependent upon values set within OPPSA.

In other instances the conversion of the data items is influenced by changes to state-specific fields between OPPSA and EZ Config Default Data, as well as any customizations that may exist.

In those instances where the value does not convert to EZ Config Default Data, you have to manually update the EZ Config Default Data policy.

Refer to Appendix B: Data Items Not Converting and Appendix C: Conditional Data Conversion for more specific information regarding data fields that may be affected.