Migration Overview
On this page
Primentra moves your Microsoft Master Data Services (MDS) models, entities, attributes and members in one flow. The flow has two sources: MDS Direct Migration and MDS Manual Import. Both run on the same engine. Only the first step differs.
Watch a direct migration in 6:57: a copy of an MDS database read with a read-only login, a dry run that refuses 107 members and says why, the run, and the result checked in the grid.
Which source to use
| MDS Direct Migration | MDS Manual Import | |
|---|---|---|
| How Primentra reads MDS | It connects to the MDS database | It reads two files that you upload |
| What you need | A SQL login that can read the MDS database from the Primentra server | Someone who can run sqlcmd on the MDS server |
| Version choice | Newest, pick per model, or every version as its own model | One version per model. The data script picks it |
| First steps | Connect, then Database | Files |
Use MDS Direct Migration when the Primentra server can reach the MDS server. Use MDS Manual Import when it cannot, or when nobody can give you a login.
The steps
Both sources share the same last three steps.
- Connect and Database (direct), or Files (manual). Primentra learns where your MDS data is.
- Options. You decide what happens to members that are gone from MDS, and to values that do not fit.
- Select. You tick the models and entities to migrate.
- Run. A dry run first. Then the run itself.
A dry run reads MDS and compares it with Primentra. It writes nothing. The run can start only after a dry run has finished.
Only administrators can open the migration screens.
Where to find them
- MDS Direct Migration: Settings › Migration › MDS Direct Migration, or
/admin/migration/mds. - MDS Manual Import: Settings › Migration › MDS Manual Import. The URL is
/admin/migration/models.
See MDS Direct Migration and MDS Manual Import for the steps of each.

What migrates
| From MDS | What Primentra does |
|---|---|
| Models | Creates them with their MDS description and dates. A model that already exists in Primentra is merged, renamed or skipped, as you choose |
| Entities | Creates them with their MDS description and dates |
| Attributes | Creates them with the name, description, data type, length, decimal places and sort order from MDS |
| Domain attributes | Links them to the migrated entity. A filter between two domain attributes of one entity is kept |
| Members | Loads Code, Name and every attribute value |
Only active members migrate. Deactivated members stay in MDS. Need them in Primentra too? That is custom work: contact us at info@primentra.com.
Codes that differ only in capitals. A case-sensitive MDS can hold the members aa and AA. Primentra does not tell capitals apart in a Code, so they would be one record. The first member loads; the other is refused, and the dry run and the problem list name it.
Data type mapping
| MDS | Primentra |
|---|---|
| Text | Text |
| Number with 0 decimals | Int. Primentra changes it to Decimal when a value is too big for Int |
| Number with 1 or more decimals | Decimal. Primentra keeps up to 10 decimal places |
| DateTime | DateTime |
| Domain-based | Domain. The link points to the migrated entity |
| Link, and every other type | Text |
File attributes do not migrate. The problem list names each one.
Requires approval comes across. The run loads every entity with it off, then switches it on again for each entity that requires approval in MDS. Until you add approvers, only Administrators can approve. An entity that was in Primentra before the run keeps its own setting. An entity that stopped during the load keeps approval off, so you can run it again. A later Merge run skips an entity while Requires approval is on: switch it off before you merge that entity again, and on after. MDS change sets that were never committed hold changes that are not in the members: they do not migrate. The problem list shows both under Approval, per entity.
Subscription views come across as Integration Views. Each MDS view of the leaf attributes becomes an Integration View in [mdm] with the same name and the MDS column names, in the MDS order. An ETL that read the MDS view changes only its connection. ID and MUID are the member's MDS identity; a row you add in Primentra later has them empty. VersionName, VersionNumber and VersionFlag show the version you migrated. ValidationStatus reads Validation succeeded or Validation failed. ChangeTrackingMask is left out, so an ETL that reads it fails at once instead of reading wrong values. When an Integration View or another object in [mdm] already has the name, it stays as it is, and the problem list names it. A later run of the same entity deploys its view again, with the columns the entity has then. Undo drops the views the run made. The problem list shows each view under Subscription view.
Users and permissions
The MDS users and groups come across as Primentra users and roles, with their permissions on what the run migrates.
- Users. Each MDS user with an email becomes a Primentra user with that email and no password. The user signs in with Forgot password. Two MDS accounts with one email become one user. A user who was removed in MDS comes across with Active off. When Primentra already has a user with that email, that user keeps their password and roles and gets the MDS roles too. The run does not link that user to the AD account.
- Users without an email. These are AD accounts. Primentra keeps their AD login and SID, and the roles they should get. They get those roles at their first sign-in with AD (single sign-on), also when Create a user at the first sign-in is off. Until then they cannot sign in. Primentra finds the account by its SID only. An account that MDS kept without a SID never gets its roles this way: give that user a role by hand. Type an email for one on the Select step if that user should sign in with a password.
- Roles. Each MDS group becomes a role with the group's name. Each user with permissions of their own gets a role named
MDS <login>, such asMDS NL\00007892. The problem list names the SID of each group, for the link to Active Directory. - Permissions. Read, create, update and delete on a model, an entity or an attribute come across as they are. Admin on a model becomes Moderator. A Deny becomes None. A permission on an attribute group goes to each of its attributes. To change one attribute, a role needs update on the entity in Primentra. When MDS gave update on an attribute only, the role gets update on the entity. It can then change Code and Name too, which MDS did not allow. The problem list names each such role under More access.
- Administrators. A Super User in MDS gets an Administrator role. A later run never switches Administrator off. When MDS has no Super User for that role anymore, the problem list says so, and you switch it off in Access Management. The other functional areas do not exist in Primentra; the problem list names them per user.
When Primentra already has a role with the same name that a person made, it stays as it is, and the problem list says so. A later run gives the roles a migration made the MDS permissions again, on the models of that run. Members you added in Primentra stay. When MDS removed the group or user of such a role, the role loses its MDS permissions on those models and keeps its members. Undo removes the users, roles and AD accounts the run made. When a later run gave those roles their permissions again, undo that later run first.
Where Primentra and MDS differ
MDS lets a Deny win over every other permission. In Primentra the highest permission of a user's roles wins. So when one group allows an entity and another denies it, the user can read it in Primentra.
The run checks this for you. It compares what each user may do in MDS with what Primentra allows after the run, for every entity and column. The problem list names each difference:
- More access (in red): Primentra allows more than MDS did. Check these first. Usually a Deny in MDS is the cause.
- Less access: Primentra allows less than MDS did.
The dry run lists the same lines beforehand.
What does not migrate
- Business rules. The problem list names each MDS rule under Business rule, with its status and the text MDS shows for it (IF, THEN and ELSE). When a rule mails a user or a group in MDS, the line names them too. Set the rules up again in Primentra. See Business Rules Overview.
- Derived hierarchies and collections.
- Subscription views of any other format: consolidated members, collections, explicit and derived hierarchies, history and type 2. The problem list names each one under Subscription view. Set them up again as Integration Views. See Integration Views.
- MDS functional areas other than Super User, member security, and permissions on hierarchies and member types. The problem list names them.
- Version flags, annotations, staging batches and the transaction log.
- Required and the input mask that allows no minus sign. Primentra leaves Required off and Allow negative values on, so these rules refuse no row during the run. The dry run lists each attribute that has them as Setting left off. After the migration, switch Required on and Allow negative values off where you need them.
- Deactivated members.
Values that do not fit
Both sources keep what MDS has. When Primentra cannot hold a value as it is, the run refuses the row. You can choose otherwise on the Options step, under When a value does not fit:
| Problem | Refuse the row (default) | Other choice |
|---|---|---|
| More than 10 decimals | The row stays out | Round to 10 decimals |
| Text longer than the Primentra column | The row stays out | Cut the text to fit |
| A number Primentra cannot hold (13 or more digits before the point) | The row stays out | Load the row, leave that value empty |
| A link to a member that does not come across | The row stays out | Load the row, leave the link empty |
| A member without a Name | Use the Code as the Name | Leave the Name empty |
Every value that loads with a change is in the problem list as Loaded with a change, with what MDS had and what Primentra stored. A Code that is too long is always refused. Cutting it could turn two members into one.
The brake
Sometimes the database refuses a row for a reason nobody foresaw. The run then finds that one row, refuses it as Unexpected error with the message of the database, and loads the rest.
A full disk, a full transaction log or a lock wait is no fault of a row. The run then stops with an error, and Resume goes on once you fix it.
An entity with more than 100 such rows, or more than 1% of its members, stops. The rows the run inserted into it are taken out again, and the other entities go on. The headline of the run names the entity in red. Fix the cause, then run that entity again. Send the message to us too: an unexpected error can be a fault in Primentra.
Domain values
A domain value links by the Code of the member it points to. MDS Manual Import reads that Code out of the {Code} Name text the data script writes.
A link to a member that does not come across is refused, not stored empty. That member was refused, is deactivated, or has a Code that is too long. Choose Load the row, leave the link empty to load the row anyway.
A filtered domain stays filtered. The filter becomes the Filter of the attribute. A filter whose parent attribute did not come across is left off.
Entities that link to themselves
An entity can link to itself, such as a Cost Center with a parent Cost Center. Primentra loads it in one run, in any row order. It fills the links in a second pass. The same goes for two entities that link to each other.
In that second pass every row is already in. A link to a member that the run refused is left out, and the row stays. The problem list names the row and the link as Loaded with a change.
Three things to know before you start
Questions
Do I run the structure and the data separately?
No. One run creates the models, entities and attributes and loads the members.
Can I run it again?
Yes. A second run into a model that an earlier run wrote adds new members and updates changed ones. You can also undo a run. See After Migration.
Related
- MDS Direct Migration: connect to the MDS database
- MDS Manual Import: run two scripts and upload two files
- After Migration: what to check once the run is done
- Models: how models, entities and attributes fit together in Primentra
- Import from Excel & CSV: the alternative when your source is not MDS
Did not find what you need?
Try the troubleshooting pages, or ask us.