CenterBase is a highly customizable platform. Universal Migrator takes a standardized approach to injecting data into CenterBase. As such, there are a few things that you should be aware of.
When you request an empty CenterBase account, you should specify that it should be a fresh, empty account created using the PartnerTemplate - 2023-01-03 .
In the event that a newer template exists, please contact us so we can review compatibility.
Universal Migrator will restore data into CenterBase but currently does not restore schema changes.
As you work with CenterBase, you should create a detailed log of all schema/object customizations you want to do. When you are ready to go live with CenterBase, a complete, fresh data restore should be completed into a brand new account and that will require that you manually recreate all your schema modifications.
Because CenterBase is completely customizable, Universal Migrator must make some assumptions about what fields are named. If you rename fields, Universal Migrator may stop restoring data to the fields. As such, except as specified below, you should only rename fields after the data restore is complete.
Prior to restoring data into CenterBase, the following steps should be done.
Using the CenterBase Admin Console, make the following adjustments:
Matters Table > Responsible Attorney Field Make this field NOT required. |
Matters Table > Practice Area Field Add all Final_Subject values from the __M_PracticeAreas table. |
Contacts Add any specialized phone/address/email/URL fields (details below). |
Matters Add any specialized User and Contact fields (details below). |
An advanced heuristic is used to match Phone Addresses (phone numbers), Postal Addresses, Email Addresses, and Web Addresses from the Universal Migrator database to CenterBase fields.
In general, the algorithm works like this for each type of Address:
Prior to restoring data, you should customize the Contact's phone, address, email, and URL fields to provide the greatest accuracy for matching.
If the participating contact has a role, the role must exactly match a matter contact-picklist field's label. If multiple contacts share the same role on a matter, one will be arbitrarily chosen. If the contact does not have a role, it will simply be linked to the matter. In the event that a contact has a specified role but a field with that label does not exist, an error will be logged.
The user must have a role that exactly matches a user-picklist field's label. If multiple users share the same role on a matter, one will be arbitrarily chosen. In the event that a user has a specified role but a field with that label does not exist, an error will be logged.
Practice Areas are not restored into CenterBase - they are resolved to existing values that live inside the Matter table's Practice Area field picklist.
When users are restored into CenterBase, they are restor using "Resolve, Inject, or Squash" semantics.
Please read this article for more information regarding working with legacy users.