CenterBase Injections: Read Me First

CenterBase Injections: Read Me First

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.

Use the PartnerTemplate Template

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.
 

Create a Detailed Playbook

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.
 

Except as Specified: Add, Do Not Rename

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.
 

Pre-Restore Requirements

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).

 

Contact Customizations

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:

  • Sort the list of CenterBase address fields by name.
  • Sort the list of Universal address records by Location, Type (if it exists), and Display Order.
  • For each CenterBase address field
    • Find the first unused matching Universal Address record
      • Find the first unused Universal Address record whose Label exactly matches the CenterBase field's label.
      • If none exist, find the first unused Universal Address record whose Location and (and Type if it has one) are contained it the CenterBase field's Label.
      • If none exist, and the CenterBase field's label contains the word "Primary", find the first unused Universal Address record that is flagged as Primary.
      • If none exist, and the CenterBase field's label contains the word "Work", find the first unused Universal Address record that has a location of Work.
      • If none exist, and the CenterBase field's label contains the word "Home", find the first unused Universal Address record that has a location of Home.
      • If none exist, and the CenterBase field's label contains the word "Bill", find the first unused Universal Address record that has a location of Billing.
      • If none exist, and the CenterBase field's label contains the word "Mobile", find the first unused Universal Address record that has a location of Mobile.
      • If none exist, and the CenterBase field's label contains the word "Other", find the first unused Universal Address record that has a location of Other.
    • If a match was found using the above, algorithm, mark the CenterBase address field and the Universal Address record as "Used".
  • After the above algorithm is run, if there are any unused CenterBase address fields and there are unused Universal address records, just fill them in any way they can.

Prior to restoring data, you should customize the Contact's phone, address, email, and URL fields to provide the greatest accuracy for matching.
 

Matter Customizations

Matter Participating Contacts

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.
 

Matter Participating Users / Originating Users

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.

Special Data Restore Notes

Practice Areas

Practice Areas are not restored into CenterBase - they are resolved to existing values that live inside the Matter table's Practice Area field picklist.

Users

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.

 

 


    • Related Articles

    • Centerbase Backups: Read Me First

      When data is backed up from Centerbase, there are a few nuances you should be aware of: Document Assignments Like many other systems, in Centerbase, each object (like a Contact or a Matter) may have a folder associated with it. Any documents within ...
    • NetDocuments Data Restore: Read Me First

      Create Profile Attributes The Universal Migrator requires certain profile attributes to exist in NetDocuments. Please create the following Profile Attributes. Property Value Client Name Client Type Text Maximum Length 50 Use Lookup Table True Hide ...
    • Amicus Cloud Extractions: Read Me First

      When backing up data from Amicus Cloud there are a few things you should be aware of. Data is Deduplicated and Merged In the Amicus Cloud database, the contacts are stored multiple times. An algorithm is used to detect duplicate items and merge them ...
    • Practice Panther Backups: Read Me First

      WARNING: Practice Panther is Messy Unfortunately, Practice Panther does not do a very good job of preventing users from inputting bad data. For example, in Practice Panther, a user can click "Add Contact" > "Save" (without typing in ANY information ...
    • Clio Data Restore: Read Me First - Matter Numbers

      In order for Universal Migrator to create matters with specified matter numbers, additional configuration is required. Log into Clio as an Administrator Go to Settings > Firm Preferences > Matter Numbering Take a screen shot of the current matter ...