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.

After you convert

Confirmation emails will be sent. It is important for staff accounts to be used for all post-conversion testing of orders, event registrations, and so forth. If this is not feasible, another option is to reset the preferred email address for selected contacts.

1. Ensure expected numbers of Individual and Organization records were created.
2. Review your committees, chapters, and so forth and compare rosters. Review roles that were assigned to members.
3. Set Membership Groups: Decide which groups make their members eligible for discounted prices, and mark those groups as IsMember by opening the group’s landing page and editing the group settings.

Post-conversion data validation scripts

Upon request, ASI Hosting can run these queries and provide the results for ease in reviewing some of your data post-conversion:

• Primary Institutes: Run this query to identify contacts with Organization names, but having no PrimaryInstituteKey. This indicates that they’re not on that company’s roster). If any of the resulting listed company names represent companies that have an ID in iMIS, open the roster for that company and add the contact to that group. You can also edit the contact’s organization on their MyAccount page to select the primary organization, which will do the same thing).

  select ind.primaryinstitutename, ind.lastname, ind.firstname, cm.ContactStatusCode  
  from Individual ind, ContactMain cm  
  where ind.ContactKey=cm.ContactKey and PrimaryInstituteName is 
  not null and PrimaryInstituteName <>'' and PrimaryInstituteName not  
  in(select InstituteName from Institute)  
  order by PrimaryInstituteName

• Duplicate organizations: Run this query to see any duplicate Organizations that were created in iMIS (multiple companies 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

• Group memberships: Run this query to view all group memberships created in iMIS database except companies:

  select gm.Name, ind.LastName, ind.FirstName, cm.ContactStatusCode,*  
  from GroupMember gmbr, GroupMain gm, Individual ind, ContactMain cm 
  where gmbr.GroupKey = gm.GroupKey and 
  gmbr.MemberContactKey=ind.ContactKey and 
  ind.ContactKey=cm.ContactKey and 
  gm.GroupKey in(select groupkey from groupmain 
  where grouptypekey in(select GroupTypeKey from GroupTypeRef where IsSystem=0))  
  order by gm.Name

• Company memberships: Run this query to see all Company group memberships:

  select gm.Name, ind.LastName, ind.FirstName, cm.ContactStatusCode,*  
  from GroupMember gmbr, GroupMain gm, Individual ind, ContactMain 
  cm where gmbr.GroupKey = gm.GroupKey and  
  gmbr.MemberContactKey=ind.ContactKey and 
  ind.ContactKey=cm.ContactKey and gm.GroupKey  
  in(select groupkey from groupmain 
  where grouptypekey in(select GroupTypeKey from GroupTypeRef 
  where IsSystem=1 and  
  GroupTypeName=’Company’)) order by gm.Name, ind.LastName, 
  Ind.FirstName

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.