Post-conversion tasks

The following tasks can help you ensure the quality of your data conversion, and some tasks must be performed to ensure proper processing.

Post-conversion data validation scripts

You can use the following queries with iMIS Workbook Converter migrations to check for any issues:

  • Committees: Run this query on a source database to get a list of all the committees and their members, and check resulting data in 20-300 (search for the committee and check against the roster there). Compare names, roles, and in cases where the membership is date-limited, the effective and expiration dates of membership:
    • SELECT Activity.Product_Code, Committee_Position.TITLE, 
Name.FULL_NAME, Name.COMPANY, Activity.ACTION_CODES, 
Activity.EFFECTIVE_DATE, Activity.THRU_DATE, 
committee_Position.RANK, Activity.TRANSACTION_DATE 

from Activity INNER JOIN Name on Name.ID = Activity.ID LEFT 
OUTER JOIN Committee_Position on Committee_Position.POSITION_CODE = Activity.ACTION_CODES 

Where Activity.ACTIVITY_TYPE = 'COMMITTEE' AND 
Activity.PRODUCT_CODE LIKE 'COMMITTEE/%' 
order by Product_Code
  • Duplicate organizations: Run this query to determine whether any duplicate Organizations that might have been created in 20-300 (for example, multiple companies were created having the same name) and investigate the cause:
    • select COUNT(i.ContactKey) as CompanyRecords, InstituteName as CompanyName 
from Institute i, ContactMain cm where i.ContactKey = cm.ContactKey 
group by InstituteName having COUNT(i.contactkey)>1

Once the data conversion is complete, open a Support Ticket through the ASI Support Portal, and request Cloud Services to retrieve the database from the SQL sandbox and restore the database back to production. This only applies if you are running the conversion on a test environment.

If running the conversion on a production environment, update the ticket with ASI hosting to remove access to the application server.