Connect, check, run: move your MDS models across
Connect Primentra to your MDS database once. Select the models you want and click Run. Your models, entities and members come across in one run, and a typical migration takes under an hour.
A dry run goes first. It shows what will change and writes nothing.
MDS Direct Migration
Primentra connects to your MDS database and only reads from it. Five steps the first time, one click after that.
Enter the server and a SQL login that can read the MDS database. Click Test connection. Primentra saves the connection.
Tap or click the picture to see the full screen.
Every next run is one click. Pick the saved connection and click Run again with the same settings. Primentra starts the dry run with the database, options and selections of the last run, and brings over what changed in MDS.
What you need
- A SQL login that can read the MDS database. Windows logon is not available yet.
- A network path from the Primentra server to the MDS server.
- MDS 2016 or later. MDS 2014 and older cannot be picked.
- The Administrator role in Primentra.
No connection to the MDS server?
Use MDS Manual Import. Someone runs two scripts on the MDS server with sqlcmd, and you upload the two files they write. Options, Select and Run work as in MDS Direct Migration.
What moves, and what stays in MDS
Primentra only reads from MDS. Undo this run puts back what a run changed.
Moves to Primentra
- Models, entities and attributes, with their data types
- Domain links between entities
- Active members, with Code, Name and every attribute value
- Explicit hierarchies
- Requires approval
- Subscription views of the leaf attributes, as Integration Views
- MDS users and groups, as Primentra users and roles with their permissions
Stays in MDS
- Business rules. The problem list names each one with its MDS text.
- Derived hierarchies and collections
- Other subscription view formats
- Member security
- Version flags, annotations, staging batches and the transaction log
- File attributes
- Deactivated members
Migration comparison
See the difference yourself
Traditional MDM migration
The old way
Migration with Primentra
The modern way
Built for SQL Server Master Data Services (Microsoft MDS) 2016 and later. With no network path to the MDS server, MDS Manual Import reads two files instead.

