Can SSAS Multidimensional cubes be migrated directly to Microsoft Fabric?

SSAS Multidimensional cubes do not have a direct import path to Fabric. They generally need to be redesigned as Tabular semantic models, including rebuilding dimensions, relationships, measures, hierarchies, security, and MDX-based calculations.

How does SSAS role-based security migrate to Microsoft Fabric?

SSAS database roles can be rebuilt as Power BI row-level security roles using DAX filters, while Windows security groups can be replaced with Microsoft Entra ID security groups. Cell-level security requires a redesigned approach because Power BI row-level security operates at the row level.

What happens to SSAS partitions when migrating to Microsoft Fabric?

Import-mode semantic models can use XMLA-based partitions. With Direct Lake, the semantic model reads Delta tables from OneLake, so organizations may be able to simplify semantic-model partitioning and rely more heavily on the storage layer.

How should SSAS migration be validated?

SSAS migration should be validated by running equivalent queries against the existing SSAS environment and the Fabric semantic model, comparing key measures and results, testing security roles and downstream clients, and running the environments in parallel before cutover.

What should be assessed before migrating SSAS to Microsoft Fabric?

Before migration, assess whether each model is Tabular or Multidimensional, compatibility level, data sources, measures, MDX or DAX calculations, roles and security rules, partitions, processing schedules, and downstream clients such as Power BI, Excel, SSRS, and third-party reporting tools.

31 Aug 2026

SSAS to Microsoft Fabric Migration: Complete Enterprise Guide

Q: Can SSAS Tabular models be directly deployed to Microsoft Fabric?

Yes. SSAS Tabular models at compatibility level 1500 or above can generally be deployed to Fabric through the XMLA endpoint, followed by connection, security, and validation changes. Models below the required compatibility level need to be upgraded before deployment.

Q: Can MDX be converted to DAX during SSAS migration?

Many MDX calculations can be reproduced in DAX, but the conversion is based on business logic rather than direct syntax translation. Complex MDX involving subselects, custom members, scope assignments, unary operators, or cell-level security requires individual analysis and validation.

Q: Can Direct Lake replace Import mode for SSAS-migrated models?

Direct Lake can be used when the required source data is available as Delta tables in OneLake. It allows a Fabric semantic model to read data directly from OneLake rather than relying on traditional Import-mode processing and refresh.

Quick Summary

SSAS Tabular to Fabric: Models at compatibility level 1500 or above can be deployed to Fabric's Analysis Services endpoint with connection updates and validation. For Direct Lake, the model connects to OneLake Delta tables instead of importing data.

SSAS Multidimensional (OLAP) to Fabric: There is no direct import path. The cube architecture must be rebuilt as a Tabular star schema model, with DAX replacing MDX calculations, dimensional hierarchies redesigned, and MDX-consuming reports assessed for compatibility.

Both migration paths require: security redesign, partition assessment, downstream client testing, and parallel validation before decommissioning the existing SSAS environment.

SSAS to Microsoft Fabric migration moves SQL Server Analysis Services semantic models, either Tabular or Multidimensional, to Microsoft's unified analytics platform. Tabular models can be deployed to Fabric's Analysis Services endpoint or converted to Power BI semantic models using Direct Lake. Multidimensional OLAP cubes require a broader redesign, rebuilding dimensions, measures, hierarchies, and MDX logic as a Tabular model using DAX.

The migration scope therefore depends heavily on the source architecture and can include MDX to DAX conversion, hierarchy redesign, SSAS partition migration, role-based security to Fabric RLS, and validation against existing SSAS query results.

SSAS Multidimensional vs SSAS Tabular: Two Different Migration Paths

The first step in any SSAS to Microsoft Fabric migration is identifying whether the source environment uses Tabular models or Multidimensional cubes. The two architectures have different storage engines, query languages, and migration requirements.

Dimension	SSAS Tabular	SSAS Multidimensional
Storage engine	VertiPaq (columnar, in-memory)	MOLAP (multidimensional, cube-based)
Query language	DAX (also supports MDX for compatibility)	MDX (native)
Data model	Relational tables with relationships	Dimensions, measures, and hierarchies
Fabric migration effort	Moderate: deploy or convert	High: full redesign required
Direct Fabric path	Deploy to Fabric as endpoint or Power BI semantic model	No direct import; must be rebuilt as Tabular

For organizations planning a migration, this distinction determines the level of redesign required and the appropriate migration strategy.

Why Organizations Are Migrating SSAS to Microsoft Fabric

Organizations are moving from SSAS to Microsoft Fabric to reduce infrastructure management and consolidate analytics workloads. Traditional SSAS environments require server management, SQL Server Analysis Services installation, service administration, and capacity planning. Fabric provides a managed analytics platform that brings semantic modeling together with Lakehouse, Warehouse, Power BI, and other analytics capabilities.

Direct Lake is another major consideration. Instead of importing data into the VertiPaq engine, a Fabric semantic model can read Delta tables directly from OneLake. This can reduce the processing and refresh requirements associated with traditional Import-mode SSAS Tabular models.

Fabric also connects semantic models with the broader Power BI ecosystem, including Power BI Desktop, paginated reports, Excel PivotTables through XMLA, and other reporting tools. This creates a more unified environment for organizations modernizing their existing SSAS and reporting architecture.

SSAS to Microsoft Fabric Asset Mapping

The migration becomes easier to plan when each SSAS component is mapped to its corresponding Fabric implementation.

SSAS Asset	Microsoft Fabric Equivalent	Migration Consideration
SSAS Tabular model	Fabric semantic model via XMLA endpoint	Compatibility level 1500+ required for direct deployment
SSAS Multidimensional cube	Power BI Tabular semantic model	Full redesign required; no direct import
DAX measure (Tabular)	DAX measure in Fabric semantic model	Usually compatible; validate against source output
MDX calculated member	DAX measure	Re-derived by business intent rather than syntax translation
SSAS dimension and hierarchy	Power BI dimension table and hierarchy	Parent-child hierarchies may require redesign
SSAS partition	Fabric semantic model partition or OneLake Delta partition	Direct Lake can reduce partition requirements
SSAS database role	Power BI RLS role with DAX filter	Rebuilt per role and validated with representative users
SSAS data source	Fabric Lakehouse or Warehouse via OneLake	Connection must be reconfigured
SSAS processing schedule	Fabric semantic model refresh schedule	Refresh logic must be rebuilt; Direct Lake can reduce refresh requirements

This mapping provides a practical starting point for determining which assets can be migrated with limited changes and which require redesign.

MDX to DAX Conversion

MDX to DAX conversion is one of the more demanding parts of SSAS OLAP cube migration because the two languages use different calculation models.

MDX is designed around multidimensional spaces, tuples, sets, and dimension hierarchies. DAX works primarily through tables, relationships, filter context, and evaluation context. Because of these differences, MDX logic is generally re-derived according to its business purpose rather than translated line by line.

MDX Pattern	DAX Approach
Calculated member	DAX measure in the semantic model
Named set	Calculated table or DAX filter expression
Time intelligence (YTD, MTD)	DAX time-intelligence functions such as DATESYTD, DATESMTD, and CALCULATE
PeriodToDate functions	CALCULATE with appropriate date filter expressions
Scope assignment	CALCULATE with explicit filter context
MDX CROSSJOIN	DAX CROSSJOIN or SUMMARIZE
Parent-child hierarchy	DAX PATH/PATHITEM functions or a flattened hierarchy table

Complex MDX involving subselects, custom member calculations, unary operators, and cell-level security requires expert review. Some calculations do not have a direct DAX equivalent and may require changes to the underlying data model rather than a simple measure conversion.

SSAS Multidimensional to Tabular Migration

SSAS Multidimensional to Tabular is the more complex migration path because there is no direct import from a Multidimensional cube into a Tabular model. Instead, you must redesign the cube around a relational star-schema approach.

One major difference is the storage engine. Multidimensional SSAS uses MOLAP, where cube data can be pre-aggregated. Tabular models use VertiPaq and DAX to evaluate calculations against relational tables. As a result, existing performance characteristics cannot simply be assumed to carry over to the new model.

Parent-child hierarchies and custom rollups require particular attention. Multidimensional models can use unary operators and custom aggregation behavior that do not have direct Tabular equivalents. These structures may need to be represented using DAX PATH functions or flattened hierarchy tables.

Security is another important consideration. Multidimensional SSAS can use cell-level security, while Power BI RLS works at the row level. Existing cell-level restrictions therefore need to be redesigned rather than directly copied.

Downstream MDX clients must also be assessed. Excel PivotTables and third-party reporting tools may rely on MDX-specific behavior, including custom members. Test these clients against the migrated Fabric semantic model before cutover.

Many-to-many relationships may also require additional redesign. Tabular implementations commonly use bridging tables and DAX calculation patterns to reproduce relationships that were handled differently in Multidimensional SSAS.

SSAS Tabular Model to Fabric Semantic Model

SSAS Tabular to Fabric migration is generally more straightforward than Multidimensional migration, particularly when the source model is already at compatibility level 1500 or above.

You can typically export the model definition using tools such as Tabular Editor or SQL Server Management Studio; update connections to point to Fabric-hosted data or OneLake, and deploy the model to the Fabric workspace through the XMLA endpoint.

Security also needs to be updated. Existing Windows authentication groups can be replaced with Microsoft Entra ID groups, while SSAS roles can be rebuilt as Power BI RLS roles using DAX filters.

Next, select the target storage mode. Organizations can continue using Import mode or move toward Direct Lake when their source data is available as Delta tables in OneLake. After deployment, validate DAX measures and model behavior against the original SSAS environment.

SSAS Partition Migration

SSAS partitions divide large fact tables into independently processable segments. They are commonly used to refresh recent data without reprocessing an entire historical dataset.

In Fabric, the appropriate partition strategy depends on the semantic model's storage mode. Import-mode models can use semantic-model partitions managed through the XMLA endpoint and tools such as Tabular Editor. You can recreate existing partition definitions and update their data sources for the Fabric environment.

Direct Lake changes this approach because the semantic model reads Delta tables directly from OneLake. In many cases, the storage-layer partitioning of the Delta tables can reduce the need for semantic-model-level partition management.

Organizations moving to Direct Lake should therefore review their existing SSAS partition strategy rather than automatically reproducing every partition in the new environment.

SSAS Role-Based Security to Fabric RLS

SSAS role-based security must be redesigned when moving to Fabric. The exact implementation depends on how the existing SSAS environment controls access.

SSAS Security Component	Fabric / Power BI Equivalent
Database role	Power BI RLS role with DAX filter expression
Dimension data security	RLS DAX filter restricting dimension rows
Cell-level security	Redesigned using RLS and Object-Level Security (OLS) where appropriate
Windows security group	Microsoft Entra ID security group
Data-level user filter	Dynamic RLS using USERPRINCIPALNAME()

Test each role with representative user accounts before retiring the SSAS environment. This confirms that users continue to see only the data permitted by their existing security model.

Step-by-Step SSAS to Microsoft Fabric Migration Process

Step 1: Inventory and Assessment. Catalog every SSAS database and identify whether each model is Tabular or Multidimensional. Record compatibility levels, data sources, measures, roles, partitions, processing schedules, and downstream clients such as Power BI, Excel, SSRS, and third-party tools.
Step 2: Migration Path Selection. Select the migration approach based on the source architecture. Tabular models at compatibility level 1500 or above can generally be deployed to Fabric with the required connection and security changes. Lower compatibility levels require an upgrade, while Multidimensional models require a full Tabular redesign.
Step 3: Data Architecture Preparation. For Direct Lake targets, provision the required Fabric Lakehouse and make source data available as Delta tables in OneLake. For Import-mode models, configure the appropriate Fabric data connections and gateway requirements where necessary.
Step 4: Model Migration. For Tabular models, deploy through XMLA, update connections, configure refresh, or enable Direct Lake where appropriate. For Multidimensional models, build the star schema, recreate dimensions and relationships, rebuild calculations as DAX measures, and redesign hierarchies.
Step 5: MDX to DAX Conversion. Document the existing MDX calculations, named sets, and scope assignments. Re-derive them as DAX based on the underlying business logic and validate the results against equivalent SSAS queries.
Step 6: Security Migration. Map SSAS database roles to Microsoft Entra ID groups and Power BI RLS expressions. Test each role using representative users rather than relying only on administrator access.
Step 7: Partition Migration. Recreate or simplify partitions according to the selected storage mode. Import-mode models can use XMLA-based partition management, while Direct Lake models may rely more heavily on OneLake Delta table organization.
Step 8: Client Tool Validation. Test downstream clients, including Power BI Desktop, Excel PivotTables, SSRS, and third-party tools. Pay particular attention to applications that rely on MDX.
Step 9: Parallel Validation. Run equivalent queries against SSAS and Fabric and compare key measures and results. Investigate discrepancies before moving users to the new environment.
Step 10: Cutover and Decommission. Update downstream connections and redirect workloads to the Fabric semantic model. Decommission the existing SSAS environment only after the migration has completed its defined parallel-validation period.

Migration Challenges

MDX Complexity

Complex MDX calculations involving subselects, custom members, unary operators, and advanced set functions may not have direct DAX equivalents. These calculations require individual analysis and may require data-model changes.

Parent-Child Hierarchies

Parent-child hierarchies with custom rollup behavior need to be redesigned for Tabular models. DAX PATH/PATHITEM functions or flattened hierarchy tables can be used depending on the required reporting behavior.

Cell-Level Security

Multidimensional cell-level security cannot be directly replicated through Power BI RLS because RLS operates at the row level. Existing restrictions therefore require a redesigned security model.

MDX Client Compatibility

Excel PivotTables and third-party tools that query Multidimensional SSAS through MDX may behave differently when connected to a Fabric semantic model. Test these clients as part of the migration.

Compatibility Level

Tabular models below compatibility level 1500 require an upgrade before direct deployment to Fabric. Validate any compatibility-level change for DAX and model behavior.

Performance Characteristics

Multidimensional MOLAP and Tabular VertiPaq use different approaches to storage and calculation. Workloads that relied on MOLAP pre-aggregation may require DAX optimization or aggregation-table design after migration.

SSAS to Microsoft Fabric Migration Checklist

Assessment

Inventory all SSAS databases (Tabular and Multidimensional)
Record model type, compatibility level, data sources, and client tools
Document all SSAS roles, dimension security, and cell security rules
Identify partition structure and processing schedules

Migration

Deploy Tabular models to Fabric via XMLA or rebuild in Power BI Desktop
Redesign Multidimensional cubes as Tabular star schema models
Convert MDX calculated members to DAX measures with expert review
Rebuild SSAS roles as Power BI RLS roles with DAX expressions
Configure Fabric connections, gateway, and Direct Lake or Import mode
Recreate or simplify SSAS partitions based on target storage mode

Validation and Cutover

Compare SSAS and Fabric query results for all key measures
Test all downstream clients (Power BI, Excel, SSRS, third-party)
Test each RLS role with real user accounts
Run parallel environments until each model wave is signed off
Update client connection strings and decommission SSAS server

SSAS to Microsoft Fabric Migration by DataTerrain

17 Years Experience 400+ US Clients SSAS Tabular and OLAP MDX to DAX Conversion Direct Lake Migration

DataTerrain is a specialist data engineering and analytics migration company that delivers end-to-end SSAS to Microsoft Fabric migration: Tabular and Multidimensional model assessment, MDX to DAX conversion, Direct Lake configuration, SSAS role-based security to Fabric RLS, partition migration, and parallel validation. Our Automated BI reports conversion service complements SSAS migration for organizations modernizing both analytical models and report libraries simultaneously. Start with a free assessment of your SSAS estate before committing to a full migration.

Schedule a Free Assessment

Key Takeaways

Tabular and Multidimensional models require different migration approaches. Tabular models can often be deployed to Fabric with targeted changes, while Multidimensional cubes require a broader Tabular redesign.
MDX to DAX is a business-logic conversion. Complex MDX should be re-derived and validated rather than treated as a simple syntax translation.
Direct Lake can simplify the target architecture. When data is available as Delta tables in OneLake, Direct Lake can reduce traditional Import-mode refresh requirements.
Security must be rebuilt and validated. Map SSAS roles to Fabric RLS and test with representative users.
Downstream clients matter. Assess Excel, SSRS, Power BI, and third-party MDX clients before cutover.

Final Thoughts on SSAS to Microsoft Fabric Migration

SSAS to Microsoft Fabric migration is not a single migration pattern. The approach depends primarily on whether the existing environment uses Tabular or Multidimensional SSAS.

Tabular models can often move to Fabric with manageable changes when the compatibility level and data architecture are suitable. Multidimensional OLAP cubes require a more substantial redesign, as Tabular semantic models require MDX to DAX conversion, hierarchy redesign, and security migration that requires particular attention.

A successful migration therefore starts with an accurate assessment of the existing SSAS estate, followed by controlled model migration, security validation, downstream client testing, and parallel query comparison before final cutover.

Contact DataTerrain to discuss your SSAS environment and plan the migration.

Frequently Asked Questions

What is SSAS to Microsoft Fabric migration?

SSAS to Microsoft Fabric migration involves moving SQL Server Analysis Services Tabular or Multidimensional models to Microsoft Fabric through deployment, conversion, or redesign. The process may include MDX to DAX conversion, security migration, partition changes, and validation.

Can SSAS Tabular models be directly deployed to Fabric?

Yes. Tabular models at compatibility level 1500 or above can generally be deployed to Fabric through the XMLA endpoint, followed by connection, security, and validation changes. Lower compatibility levels require an upgrade.

Can MDX be converted to DAX?

Many MDX calculations can be reproduced in DAX, but conversion depends on business logic rather than direct syntax translation. Complex MDX involving subselects, custom members, scope assignments, and cell security requires expert review.

What is the hardest part of SSAS OLAP cube migration?

The most challenging part is generally redesigning the Multidimensional cube as a Tabular model. Parent-child hierarchies, custom rollups, many-to-many relationships, cell-level security, and complex MDX calculations may require significant redesign.

How does SSAS role-based security migrate to Fabric?

SSAS database roles can be rebuilt as Power BI RLS roles using DAX filters, while Windows security groups can be replaced with Microsoft Entra ID groups. Cell-level security requires a redesigned approach because Power BI RLS operates at the row level.

What replaces SSAS partitions in Microsoft Fabric?

Import-mode semantic models can use XMLA-based partitions. With Direct Lake, data is read from OneLake Delta tables, so organizations may be able to simplify semantic-model partitioning and rely more on the storage layer.

Can Direct Lake replace Import mode for SSAS-migrated models?

Yes, when the required source data is available as Delta tables in OneLake. Direct Lake lets the semantic model read data directly from OneLake instead of relying on traditional Import mode processing and refresh.