Migrate an unknown entity to an entity

An unknown entity is a record which has not been validated and which is not normalized data.  When migrating an unknown entity to a known entity, we validate the data and create entity, contact, address, history and other records as appropriate.

The initial migration is done client side giving the user an opportunity or responsibility to validate the record before saving it.  When they click save then, the new entity and related records are created.

Initiate migration from unknown entity to an entity

When an unknown entity has been validated, click the unknown entity icon on the unknown entity list, or on the unknown entity details page.

{screenshots here }

This will give a preview of the migration so that the user can verify the record before it is saved.  In future releases, the preview option can be configured to be turned off.

Migration process

When the migrate button is clicked an API call is made which does the following:

  1. Checks to see if there are any related unknown entities which should be also converted or combined into the new entity record set.
  2. Check to see if an entity, contact, contact method, or address which already exists for possible duplicates.
  3. If duplicates are found for either of the above, then a suggestion is made to the user to combine the records.
  4.  If no duplicates are found then the preview screen is displayed allowing the user to validate the migration and save the new records.

Similar unknown entity 

Unknown entity records are flat.  They may look like this for example


James  Cluff | iBCScorp | phone | address | etc.

Maren Sibbett | iBCScorp |phone |address |etc.

For example if adding James Cuff's record from above, say iBCScorp was just validated and we want to add this company as a potential lead, then we might also want to add Maren as a contact also for the new entity iBCScorp from a different unknown entity record.

The unknown entity list is checked for these kinds of related records so that the operator may combine them if desired.

{screenshot here}

Existing entity which is similar

Likewise if the unknown entity record was for a company which already existed, or if the person already existed in the database, then rather than adding a duplicate, we would give the option to combine those records.

Convert to entity preview screen

The convert to entity preview screen has all of the details on one page for the new entity so they can be easily reviewed.  After clicking save, the entity and related records are stored.

In the preview screen, the relationships can be added ,as well as tags, categories or keywords if desired.  Additionally any special fields or data that pertains to a relationship type.  The relationship type is associated with a template which provides all of the necessary fields and layout for that particular type of entity.

Redirect after saving

After the record is saved, if the migration was from the unknown entity list page, then the user is returned to the list, but the record that was there as an unknown entity before is no longer there because it is marked as migrated.

If the migration happened from the unknown entity details page, then the user is directed to the entity details page for the entity which was just converted.