%402x.svg)
Models, hierarchies, business rules, users and every downstream feed, migrated to Profisee on Azure or wherever you run it. Our two MDS migrations went live in 10 and 12 weeks, with no disruption to daily operations.
It starts with an inventory: every MDS model, entity, attribute, hierarchy, business rule, subscription view and the systems that read them, mapped before anything moves.
Entities, attributes, hierarchies, relationships, users and groups and the data itself transfer with Profisee's MDS Migration Utility, included in every Profisee subscription.
Data quality rules, business rules, workflows and the attribute and hierarchy types the utility does not support, rebuilt and tested in Profisee.
Matching and survivorship in Profisee's matching engine, so every customer, product or legal entity has one authoritative record. At the bank, five matching strategies and more than ten data quality rules replaced custom-built tools.
ERP, CRM, the data platform and Power BI read from Profisee through orchestrated pipelines, and each consuming system is validated inside its own workflow.
Both systems run in production, outputs are compared daily, and every discrepancy is closed before the switch.
Stewardship workflows, access roles, and one deployment pipeline for Profisee models from development to production, handed over with the knowledge to change them.
Profisee as SaaS or PaaS on Azure, bought through the Azure Marketplace, or on AWS, Google Cloud or on-premises.
Your ERP and CRM systems, for example Microsoft Dynamics 365 and SAP, plus the spreadsheets and side databases that feed MDS today.
Mastered data delivered to Databricks, Snowflake, BigQuery or Microsoft Fabric, where Profisee also runs as a native Fabric workload. Power BI reads it through Profisee's own connector, and Microsoft Purview keeps the catalogue and lineage.
An inventory of models, rules and consuming systems, the list of what the utility will not move, the target architecture, and a fixed price for the migration.
Model, rules, matching, integrations and the deployment pipeline, built and tested in Profisee.
Both systems in production, with outputs compared every day by the operations teams until every discrepancy is closed.
The switch, MDS decommissioned, and workflows, roles and runbooks handed over to your team.
From assessment to cutover, our two MDS migrations took 10 and 12 weeks.
The first return is risk: the unsupported component leaves the audit scope and the SQL Server upgrade is unblocked. The second is what the golden record makes possible afterwards.
Top-tier Dutch commercial bank
Up to 500,000 master data records from six systems in one golden record per commercial client, for KYC, sanctions and lending. A three-week parallel run proved every data point before cutover. Five matching strategies and more than ten data quality rules replaced custom-built tools.
Global financial trading institution
Trading data, cost structures, legal entity hierarchies and reference data moved in 12 weeks across ten entity types, with five hierarchies and ten automated data quality rules. The client team now runs the platform on its own.
Eastern European beverage manufacturer
Profisee integrated with Dynamics 365 in 15 weeks: product launches 40% faster, 16% fewer SKUs and 23% procurement savings.
Yes. Microsoft states that MDS is removed in SQL Server 2025 and remains supported in SQL Server 2022 and earlier. Extended support for SQL Server 2022 ends on 12 January 2033.
You can, until its support ends. The instance that hosts MDS then stays on 2022, and Data Quality Services blocks the upgrade too. Planning the move alongside your next SQL Server upgrade keeps it to one project.
It moves entities, attributes, hierarchies, relationships, users and groups and the data. Data quality rules and some attribute and hierarchy types are rebuilt by hand. We list these in the assessment, so the price covers them.
Our two MDS migrations took 10 and 12 weeks, including a three-week parallel run at the bank. The timeline scales with the number of models, rules and downstream systems.
Microsoft's own Purview documentation calls Profisee “the premier upgrade and replacement solution” for MDS. It runs as SaaS or PaaS on Azure, as a native Microsoft Fabric workload, and connects to Purview, Power BI, Databricks and Snowflake. Astral Forest is a Profisee partner.
The ones you already run: Databricks, Snowflake, BigQuery, Microsoft Fabric and Power BI on the analytics side, and ERPs such as Dynamics 365 and SAP on the operational side.
We look at your models, rules and downstream feeds, and tell you what the migration takes and what the utility will not move.
Every migration starts with a fixed-price assessment of one to two weeks.
