Documentation
Use Primentra
Getting Started
Data Grid
Approvals
Set up
Modeling
Business Rules
Users & Roles
Sign-in & Security
Install and run
Installation
Administration
Integration & API
Architecture
Migrate from MDS
Migrating from MDS

After Migration

On this page

Primentra shows what each run did, but it cannot tell you whether the result is correct. Work through this list before you let users into the migrated data.

1. Read the problem list

The run ends with a problem list. It names every refused row, every value that loaded with a change, and every column that did not migrate. Download it as CSV, Excel or JSON and work through it. The screen shows the first 200 rows. The download holds all of them.

2. Check the row counts

Open each entity in the grid and compare the record count in the status bar with the count in MDS. A gap usually means one of these:

  • The entity was unticked on the Select step.
  • Rows were refused. The problem list says why.
  • The members are deactivated in MDS. Only active members migrate.
  • You chose Skip for that model under Before the run.

3. Check the domain columns

An unresolved domain value is refused, not stored empty. The problem list names each one. Fix the Code in MDS or in Primentra, then run again. A second run adds the missing rows. You can also choose Load the row, leave the link empty on the Options step. See Migration Overview.

A domain attribute whose entity did not come across stays Text. Create the source, then set the attribute back to Domain in the entity form and pick it. See Domain Sources & Links.

See Domain Attributes & Hierarchies for how a resolved reference is stored.

4. Validate the business rules

Business rules do not migrate, and the import does not enforce the rules you already have. Legacy data is expected to break them. A direct migration lists each MDS rule in the problem list, with the text MDS shows for it: use that list as your to-do list.

  1. Create the rules you need. See Creating a Rule from Templates.
  2. Run validation per entity and use the row filter to show only failing rows. See Validating Entities.

5. Finish the entity configuration

The migration cannot carry every setting across. Check each entity:

  • Requires approval is on again where MDS had it, and only Administrators can approve. Assign approvers to those entities. See Configuring Approvers.
  • Required is off and Allow negative values is on for every migrated attribute. The dry run listed each attribute where MDS asks otherwise. Switch them where you need them. See Attributes & Data Types.
  • Unique flags, date and time formats, and column order are worth a second look.
  • Column widths are not migrated.

6. Set up access

With Users and permissions on, the run made the MDS users and groups as Primentra users and roles, with their permissions on what it migrated. The problem list names each user and column where Primentra allows more or less than MDS. With it off, only administrators can see the new entities until you configure roles.

  1. Review the roles the run made, or create them. See Roles & Permissions.
  2. Check the users. A migrated user with an email signs in with Forgot password the first time. See User Management.
  3. Check the result with the Permissions Report.

7. Check the integration views

The migration makes an Integration View for each MDS subscription view of the leaf attributes, with the MDS name and the MDS columns. Point each ETL at the Primentra database: the view name stays the same. A view of another format is in the problem list; set it up again by hand. An entity that had no subscription view in MDS starts without one. The Integration Views screen lists every entity that has no view yet. See Integration Views.

Known difference: Code and Name attributes

An entity that an earlier version of the MDS import created carries two extra rows in its attribute list: one flagged as the code attribute and one flagged as the name attribute. An entity created inside Primentra does not have them, because Code and Name are built-in columns there.

The rows are metadata only. They hold no data.

Where you can see the difference:

PlaceWhat you see
Data gridNo difference. Code and Name are normal columns
Entity formNo difference. The attribute list hides them
Permission treeBoth appear, grayed out, tagged CODE and NAME. They cannot be given a permission
Model schema exportThey are included, so such an entity produces a different export file from an identical native entity

Nothing needs to be done about this. It matters only when you compare a model export of such an entity with one of an entity you built by hand. See Model Export / Import.

Running again and undoing a run

You can run a migration again. A run into a model that an earlier run wrote adds new members and compares the others column by column. A column that changed only in MDS is written. A column that changed only in Primentra stays. A conflict, where the same column changed in MDS and in Primentra, goes to MDS unless you keep the Primentra values under Before the run. You can tick more or fewer columns than the last run: a newly ticked column gets the MDS value where Primentra has it empty, and is a conflict where Primentra holds another value. Switch on Delete members that are gone from MDS to remove members that MDS no longer has.

Undo this run takes a run back. It removes the rows the run added, puts changed rows back as they were, and removes the models and entities the run created once nothing else is in them. A row that someone changed in Primentra after the run stays. Undo goes newest first. If a later run wrote to the same entities, undo that one first.