A handshake symbolizes a partnership in an integrated data platform connecting databases, documents, cloud services, and analytics.
Kanerika says it has signed a memorandum of understanding (MOU) with Microsoft to look at moving legacy ETL and data-integration workloads onto Microsoft Fabric. The agreement is a partner go-to-market arrangement, not a Fabric feature or a migration tool. For IT teams it is a signal of how Microsoft's partner ecosystem is lining up behind Fabric as the landing zone for older data pipelines.

A handshake symbolizes a partnership in an integrated data platform connecting databases, documents, cloud services, and analytics. What was announced​

According to Kanerika's release, Kanerika is a Microsoft Fabric Featured Partner and Microsoft Solutions Partner for Data and AI. The MOU covers Microsoft's fiscal year 2027, and the language is deliberately tentative. The two companies plan to explore three things:

  • Joint go-to-market planning.
  • Co-sell alignment with Microsoft field teams.
  • Technical collaboration on Fabric migrations.

Nothing in the release describes a launch, a customer commitment, specific commercial terms, or a guaranteed migration program. I also found no separate Microsoft announcement confirming the MOU, so every term here rests on Kanerika's own statement. Treat it as intent, not an operating program.

Which legacy platforms are in scope​

The release names these migration sources:

  • Informatica PowerCenter and IDMC
  • Alteryx
  • Talend
  • SAP BusinessObjects Data Services
  • IBM DataStage
  • Qlik Replicate
  • Microsoft's own SQL Server Integration Services (SSIS), Azure Data Factory and Azure Synapse pipelines

That list is a focus area. It is not a statement that each source has a mature, automated path to Fabric. The inclusion of Microsoft's own tools is notable. Kanerika's marketing material says Microsoft has announced the retirement of Azure Synapse Analytics and recommends migrating to Microsoft Fabric. That is Kanerika's characterization, so check Microsoft's current lifecycle guidance for your own timelines.

The 80% automation claim, in context​

Kanerika says its FLIP platform automates up to 80% of conversion effort across supported paths, and that migrations can shrink from months to weeks. The release gives no methodology, sample size or per-platform breakdown. "Up to" is also doing a lot of work in that sentence.

Kanerika's own services page is more candid. It says that on ETL paths such as Informatica to Microsoft Fabric, its consultants review and redesign the 20-30% of logic that FLIP cannot automate. That is roughly consistent with the 80% ceiling. It also shows that a human-led remainder is expected, and it is often the hard part: undocumented business rules, edge-case transformations and orchestration quirks.

Another Kanerika blog post cites a lower figure. It describes a 50 to 60% reduction in overall migration effort on SQL Server, SSIS and ADF paths. It also says the pipeline and ETL layer typically accounts for 50 to 60 percent of total effort. These are vendor-authored numbers measured differently, so don't read them as contradictions. They do show how much the headline depends on which path and which metric you pick.

The release also lists the factors that decide whether a migration pays off:

  • Legacy licensing and support costs retired.
  • Migration and validation investment.
  • Parallel-running requirements.
  • Ongoing Fabric consumption.

It adds that savings and payback vary by workload and by the systems decommissioned.

What Fabric actually provides​

Microsoft Learn describes Fabric as an analytics platform whose workloads share OneLake. Per Microsoft's overview, OneLake is a unified logical data lake built on Azure Data Lake Storage that lets workloads share data without moving or duplicating it. Data Factory in Fabric offers more than 200 native connectors.

Microsoft's data-lifecycle documentation lists several ways to get data in:

  • Pipelines for batch loads.
  • Eventstreams for real-time data.
  • Mirroring for continuous replication.
  • Shortcuts for referencing external storage in place.

For transformation it offers Dataflow Gen2, a low-code Power Query interface, and notebooks for Python, T-SQL and Scala.

This range matters for migration planning. A legacy ETL job rarely maps one-to-one onto a single Fabric item. Teams must decide between pipelines, dataflows, notebooks and warehouse SQL for each workload, then prove the outputs match.

Delivery evidence: what the customer stories show​

The release leans on Kanerika's Fabric delivery record. Microsoft's own customer stories give the most independent evidence.

FoodPharma (Microsoft story, June 9, 2026):

  • Kanerika consolidated six systems: NetSuite, RedZone, Parity Factory, UpKeep, Paychex and Outlook.
  • The work covered more than 50 tables and roughly 1 TB of history, delivered in a seven-week implementation.
  • Automated daily loads use Data Pipelines and Dataflow Gen2.
  • Microsoft reports cross-functional reporting dropped from two business days to about 90 minutes.
  • The BI team recovered roughly 15 hours a week.
  • A one-month Proof of Value preceded the build.

Southern States Material Handling (Microsoft story, January 20, 2026):

  • A Fabric and Power BI build connected SQL Server and SharePoint data.
  • It used a Lakehouse architecture, with ingestion orchestrated through Azure Data Factory components.
  • The initial load was about 1 TB, followed by a master pipeline that runs every four hours.
  • Microsoft's summary cites 90% data accuracy and 85% higher operational visibility.

Both are consolidation and analytics-foundation projects. Neither is a documented case of retiring an Informatica, DataStage or Talend estate using FLIP. So they show Kanerika can deliver on Fabric. They don't validate the 80% figure or the months-to-weeks claim. The release's own Informatica-to-Fabric (60% faster processing) and Alteryx-to-Fabric (74% faster reporting) results come from Kanerika's published case studies, not from Microsoft.

Recent FLIP expansion​

Kanerika's October 2026 announcement said five more FLIP pathways became generally available:

  • SAP Crystal Reports to DevExpress
  • IBM DataStage to Fabric
  • Databricks to Fabric
  • Alteryx to Databricks
  • Qlik to Power BI

Of those, only IBM DataStage appears in the MOU's list of sources. The other pathways are related but distinct, and I wouldn't assume every platform in the MOU has a generally available automated path.

What admins and data teams should do​

An MOU is a go-to-market signal. If you run a legacy integration estate, here is how to use it.

  1. Inventory first. Count jobs, mappings and packages by platform, and note which are actively used.
  2. Ask for pathway-specific numbers. Request automation rates for your source platform and your complexity profile, not a blended "up to" figure.
  3. Ask what the remaining work involves. Get the share of logic that needs manual redesign and who does it.
  4. Plan parallel running. Run old and new in parallel and define reconciliation criteria before cutover. The release itself lists validation and parallel running as cost drivers.
  5. Model Fabric consumption. Capacity costs replace license costs, and savings depend on actually decommissioning the old platforms.
  6. Don't assume Microsoft backing. Co-sell alignment may help with funding or field engagement, but the release doesn't promise either. Ask your Microsoft account team what an MOU changes in practice.

Balanced view​

The case for the deal is reasonable. Fabric's integrated design, OneLake storage and Microsoft's published customer evidence give migrations a coherent target. A partner with accelerators and a documented delivery record can shorten some projects.

The caveats are equally clear. The release is a vendor-issued press release that ends with an invitation to request a migration assessment, so it has a lead-generation purpose. The headline metrics are Kanerika's own. The MOU is exploratory and time-boxed to one fiscal year. Fabric is also not the only target: Kanerika says it partners with Databricks and Snowflake too, and its own pathway list includes Databricks destinations.

The practical takeaway is to treat the announcement as a reason to assess your integration estate, not as proof that migration has become push-button.

 

References

  1. Kanerika and Microsoft Sign MOU to Expand GTM on Legacy ETL Migration to Microsoft Fabric - EIN Presswire EIN Presswire 2026-11-17T16:15:00+00:00
  2. Data Migration Consulting Services and Solutions kanerika.com
  3. Southern States Material Handling (SSMH) hits 90% data accuracy and 85% better visibility with Microsoft Fabric and Kanerika | Microsoft Customer Stories microsoft.com