{"id":12086,"date":"2023-08-02T17:05:19","date_gmt":"2023-08-02T15:05:19","guid":{"rendered":"https:\/\/www.leaplytics.de\/?page_id=12086"},"modified":"2026-11-06T11:12:10","modified_gmt":"2026-11-06T10:12:10","slug":"%ce%bc%ce%b5%cf%84%ce%ac%ce%b2%ce%b1%cf%83%ce%b7-%ce%b1%cf%80%cf%8c-%cf%84%ce%bf-qlikview-%cf%83%cf%84%ce%bf-power-bi","status":"publish","type":"page","link":"https:\/\/www.leaplytics.de\/el\/%ce%bc%ce%b5%cf%84%ce%ac%ce%b2%ce%b1%cf%83%ce%b7-%ce%b1%cf%80%cf%8c-%cf%84%ce%bf-qlikview-%cf%83%cf%84%ce%bf-power-bi\/","title":{"rendered":"\u039c\u03b5\u03c4\u03ac\u03b2\u03b1\u03c3\u03b7 \u03b1\u03c0\u03cc \u03c4\u03bf QlikView \u03c3\u03c4\u03bf Power BI - \u0397 \u03c0\u03c1\u03bf\u03c3\u03ad\u03b3\u03b3\u03b9\u03c3\u03ae \u03bc\u03b1\u03c2"},"content":{"rendered":"<p><!--\n  WordPress Custom HTML block content.\n  The WordPress page title supplies H1. Set the page title to:\n  QlikView to Power BI Migration\n  Install qlikview-powerbi.css in Additional CSS or enqueue it in the theme.\n  Enqueue qlikview-powerbi.js to enable the optional live estimator.\n  The page remains informative without JavaScript.\n--><\/p>\n<article class=\"lm-migration\" lang=\"en\" aria-labelledby=\"lm-hero-title\">\n<header class=\"lm-hero\">\n<div class=\"lm-hero__copy\">\n<p class=\"lm-eyebrow\">QLIKVIEW TO POWER BI MIGRATION<\/p>\n<h2 id=\"lm-hero-title\">Move to Power BI. Keep your KPIs consistent.<\/h2>\n<p class=\"lm-hero__lead\">We migrate QlikView data models, scripts, calculations, and reports to Power BI. Our software automates supported work. Our engineers review exceptions and validate critical KPIs against approved QlikView results.<\/p>\n<div class=\"lm-actions\">\n        <a class=\"lm-button lm-button--primary\" href=\"https:\/\/www.leaplytics.de\/kontakt\/\">Discuss scope and deadline <span aria-hidden=\"true\">\u2197<\/span><\/a><br \/>\n        <a class=\"lm-button lm-button--text\" href=\"#lm-assessment\">See assessment deliverables <span aria-hidden=\"true\">\u2193<\/span><\/a>\n      <\/div>\n<p class=\"lm-hero__note\">We confirm scope, delivery dates, and suitable automation after we review your QlikView applications.<\/p>\n<\/p><\/div>\n<figure class=\"lm-hero__figure\" aria-label=\"Conceptual flow from QlikView source files through migration and validation to Power BI project files\">\n<p class=\"lm-figure-label\">CONTROLLED MIGRATION PIPELINE<\/p>\n<div class=\"lm-pipeline\">\n<div class=\"lm-pipeline__stage lm-pipeline__stage--source\">\n          <span class=\"lm-pipeline__tag\">SOURCE<\/span><br \/>\n          <strong>QlikView<\/strong><br \/>\n          <small>QVW \u00b7 project XML \u00b7 load scripts<br \/>QVD dependencies \u00b7 KPI expressions<\/small>\n        <\/div>\n<div class=\"lm-pipeline__connector\" aria-hidden=\"true\"><span>\u2193<\/span><\/div>\n<div class=\"lm-pipeline__stage lm-pipeline__stage--engine\">\n          <span class=\"lm-pipeline__tag\">LEAPLYTICS ACCELERATOR<\/span><\/p>\n<div class=\"lm-mini-steps\"><span>Analyze<\/span><span>Convert<\/span><span>Validate<\/span><\/div>\n<p>          <small>Traceable mappings and review flags<\/small>\n        <\/div>\n<div class=\"lm-pipeline__connector\" aria-hidden=\"true\"><span>\u2193<\/span><\/div>\n<div class=\"lm-pipeline__stage lm-pipeline__stage--target\">\n          <span class=\"lm-pipeline__tag\">TARGET<\/span><br \/>\n          <strong>Microsoft Power BI<\/strong><br \/>\n          <small>SQL \/ Power Query M \u00b7 DAX<br \/>TMDL \u00b7 PBIR \u00b7 PBIP<\/small>\n        <\/div>\n<\/p><\/div><figcaption>Conceptual workflow. Supported conversions and required manual work depend on the source application.<\/figcaption><\/figure>\n<\/header>\n<section class=\"lm-section lm-outcomes\" aria-labelledby=\"lm-outcomes-title\">\n<div class=\"lm-section-heading lm-section-heading--wide\">\n<p class=\"lm-eyebrow lm-eyebrow--dark\">WHAT YOU CAN REVIEW BEFORE YOU COMMIT<\/p>\n<h2 id=\"lm-outcomes-title\">Make the migration decision with clear evidence.<\/h2>\n<p>Our assessment turns your QlikView files and business requirements into a defined migration plan. The result supports budget approval, delivery planning, and technical review.<\/p>\n<\/p><\/div>\n<div class=\"lm-card-grid lm-card-grid--three\">\n<div class=\"lm-card lm-card--topline\"><span class=\"lm-card__index\">SCOPE<\/span><\/p>\n<h3>See the work<\/h3>\n<p>Receive an application inventory, shared dependencies, conversion options, and a list of cases that need manual work.<\/p>\n<\/div>\n<div class=\"lm-card lm-card--topline\"><span class=\"lm-card__index\">DELIVERY<\/span><\/p>\n<h3>Plan the release<\/h3>\n<p>Review a proposed sequence, estimated consultant effort, major risks, and any limits set by your deadline.<\/p>\n<\/div>\n<div class=\"lm-card lm-card--topline\"><span class=\"lm-card__index\">ACCEPTANCE<\/span><\/p>\n<h3>Define what passes<\/h3>\n<p>Agree on critical KPIs, reference results, security tests, and the people who approve the final reports.<\/p>\n<\/div><\/div>\n<p class=\"lm-footnote\">These are assessment outputs, not a guarantee that every QlikView feature can be converted automatically.<\/p>\n<\/section>\n<section class=\"lm-section lm-assessment\" id=\"lm-assessment\" aria-labelledby=\"lm-assessment-title\">\n<div class=\"lm-section-heading\">\n<p class=\"lm-eyebrow lm-eyebrow--dark\">SCOPED ASSESSMENT<\/p>\n<h2 id=\"lm-assessment-title\">Get a migration plan before you commit to the full build.<\/h2>\n<p>We start with your QlikView application list and one representative application. We assess dependencies, conversion options, effort, and delivery risks. You can review the plan before you approve implementation.<\/p>\n<\/p><\/div>\n<div class=\"lm-card-grid lm-card-grid--two\">\n<div class=\"lm-card lm-card--soft\">\n<h3>What we need for the assessment<\/h3>\n<ul class=\"lm-checklist\">\n<li>List of QVW applications and required reports<\/li>\n<li>One representative QVW application and its project export, where available<\/li>\n<li>Load scripts, QVD dependencies, and source system overview<\/li>\n<li>Critical KPI definitions and example results<\/li>\n<li>Target Power BI environment and security requirements<\/li>\n<li>Priority reports, deadline, and available business reviewers<\/li>\n<\/ul>\n<p class=\"lm-footnote\">Share sensitive files through an approved secure channel. QlikView project files do not contain loaded application data, but some project artifacts can contain sensitive settings.<\/p>\n<\/p><\/div>\n<div class=\"lm-card lm-card--soft\">\n<h3>What you receive<\/h3>\n<ul class=\"lm-checklist\">\n<li>Application, script, and KPI inventory<\/li>\n<li>Data lineage and shared model dependencies<\/li>\n<li>Conversion classification and manual review list<\/li>\n<li>Candidate target architecture and pilot scope<\/li>\n<li>Prioritized implementation plan with assumptions<\/li>\n<li>Budget range, delivery risks, and acceptance approach<\/li>\n<\/ul>\n<p class=\"lm-footnote\">For a fixed-price proposal, the scope, exclusions, access conditions, test criteria, and change process must first be agreed.<\/p>\n<\/p><\/div>\n<\/p><\/div>\n<\/section>\n<section class=\"lm-section lm-section--intro\" aria-labelledby=\"lm-unit-title\">\n<div class=\"lm-section-heading lm-section-heading--wide\">\n<p class=\"lm-eyebrow lm-eyebrow--dark\">THE CENTRAL MIGRATION RISK<\/p>\n<h2 id=\"lm-unit-title\">Report counts alone do not show the migration effort.<\/h2>\n<p>Several reports can use one data model and the same KPI definitions. One report can also require complex data transformations. We estimate the work from the underlying logic and its dependencies.<\/p>\n<p>The new reports must return the approved business results. They must also preserve required access controls and user functions. Matching the old layout is not enough.<\/p>\n<\/p><\/div>\n<div class=\"lm-card-grid lm-card-grid--three\" aria-label=\"Three technical dimensions of a QlikView migration\">\n<div class=\"lm-card lm-card--topline\"><span class=\"lm-card__index\">01 \/ DATA<\/span><\/p>\n<h3>Data preparation<\/h3>\n<p>Map SQL sources, QVD chains, joins, incremental loads, and transformations. Identify logic that should move to SQL, Power Query, or a data platform.<\/p>\n<\/div>\n<div class=\"lm-card lm-card--topline\"><span class=\"lm-card__index\">02 \/ LOGIC<\/span><\/p>\n<h3>Business semantics<\/h3>\n<p>Track KPI definitions, Set Analysis, AGGR, variables, filter behavior, and the grain of each calculation before translating them to DAX.<\/p>\n<\/div>\n<div class=\"lm-card lm-card--topline\"><span class=\"lm-card__index\">03 \/ USE<\/span><\/p>\n<h3>Reports and access<\/h3>\n<p>Rebuild the required views and interactions. Review Section Access, Power BI roles, refresh processes, and the rules for business acceptance.<\/p>\n<\/div><\/div>\n<\/section>\n<section class=\"lm-section\" aria-labelledby=\"lm-process-title\">\n<div class=\"lm-section-heading\">\n<p class=\"lm-eyebrow lm-eyebrow--dark\">PROPRIETARY MIGRATION SOFTWARE<\/p>\n<h2 id=\"lm-process-title\">Automate repeatable work. Review every exception.<\/h2>\n<p>Our software records the source definition for each generated item. It also reports unsupported patterns. Our engineers review those cases before release.<\/p>\n<\/p><\/div>\n<ol class=\"lm-process\" aria-label=\"Migration process\">\n<li><span class=\"lm-process__num\">01<\/span><br \/>\n<h3>Extract<\/h3>\n<p>Read supported application metadata, object definitions, scripts, expressions, and dependencies.<\/p>\n<\/li>\n<li><span class=\"lm-process__num\">02<\/span><br \/>\n<h3>Classify<\/h3>\n<p>Find shared components, complex logic, feature gaps, and migration priorities.<\/p>\n<\/li>\n<li><span class=\"lm-process__num\">03<\/span><br \/>\n<h3>Generate<\/h3>\n<p>Create candidate data transformations, models, measures, and report definitions.<\/p>\n<\/li>\n<li><span class=\"lm-process__num\">04<\/span><br \/>\n<h3>Reconcile<\/h3>\n<p>Compare selected source and target results with the same data and filter conditions.<\/p>\n<\/li>\n<li><span class=\"lm-process__num\">05<\/span><br \/>\n<h3>Approve<\/h3>\n<p>Resolve exceptions, test access rules, and obtain business sign-off before deployment.<\/p>\n<\/li>\n<\/ol>\n<\/section>\n<section class=\"lm-section\" id=\"lm-coverage\" aria-labelledby=\"lm-coverage-title\">\n<div class=\"lm-section-heading lm-section-heading--wide\">\n<p class=\"lm-eyebrow lm-eyebrow--dark\">PRACTICAL CONVERSION SCOPE<\/p>\n<h2 id=\"lm-coverage-title\">Know what the software can convert and what needs review.<\/h2>\n<p>Use this table to plan the migration. It shows candidate automated outputs and the checks needed before release. Support depends on the source application.<\/p>\n<\/p><\/div>\n<div class=\"lm-table-scroll\" role=\"region\" aria-label=\"QlikView to Power BI conversion planning matrix\" tabindex=\"0\">\n<table class=\"lm-table\">\n<caption>Conversion planning matrix for a technical assessment<\/caption>\n<thead>\n<tr>\n<th scope=\"col\">QlikView component<\/th>\n<th scope=\"col\">Candidate automated output<\/th>\n<th scope=\"col\">Review before release<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<th scope=\"row\">Load scripts and QVD chains<\/th>\n<td>Source inventory, dependency map, suggested SQL or Power Query M transformations.<\/td>\n<td>Incremental logic, external jobs, dynamic paths, and target data refresh.<\/td>\n<\/tr>\n<tr>\n<th scope=\"row\">Associative data model<\/th>\n<td>Table and field mappings, candidate relationships, semantic model definitions.<\/td>\n<td>Cardinality, fact grain, link tables, synthetic keys, and filter propagation.<\/td>\n<\/tr>\n<tr>\n<th scope=\"row\">Set Analysis and variables<\/th>\n<td>Proposed DAX measures for supported patterns, with links to source expressions.<\/td>\n<td>Nested sets, possible and excluded values, alternate states, and dynamic variables.<\/td>\n<\/tr>\n<tr>\n<th scope=\"row\">AGGR calculations<\/th>\n<td>Candidate DAX calculations and explicit grouping requirements.<\/td>\n<td>Outer aggregation, DISTINCT behavior, sorting, and calculation context.<\/td>\n<\/tr>\n<tr>\n<th scope=\"row\">Sheets and charts<\/th>\n<td>Report structure and candidate Power BI visual definitions.<\/td>\n<td>Custom extensions, user interactions, bookmarks, and visual differences.<\/td>\n<\/tr>\n<tr>\n<th scope=\"row\">Section Access<\/th>\n<td>Permission inventory and proposed Power BI security roles.<\/td>\n<td>Role assignments, workspace permissions, and negative access tests.<\/td>\n<\/tr>\n<tr>\n<th scope=\"row\">Critical KPIs<\/th>\n<td>Source-to-target test cases, comparison results, and an exception register.<\/td>\n<td>Reference data, accepted tolerances, and approval by the KPI owner.<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/div>\n<p class=\"lm-footnote\">Technical context: Qlik documents <a href=\"https:\/\/help.qlik.com\/en-US\/qlikview\/September2025\/Subsystems\/Client\/Content\/QV_QlikView\/QlikView_Project_Files.htm\">project exports<\/a>, <a href=\"https:\/\/help.qlik.com\/en-US\/qlikview\/September2026\/Subsystems\/Client\/Content\/QV_QlikView\/ChartFunctions\/SetAnalysis\/set-analysis-expressions.htm\">Set Analysis<\/a>, and <a href=\"https:\/\/help.qlik.com\/en-US\/qlikview\/September2026\/Subsystems\/Client\/Content\/QV_QlikView\/ChartFunctions\/aggr.htm\">AGGR<\/a>. Microsoft documents <a href=\"https:\/\/learn.microsoft.com\/en-us\/power-bi\/guidance\/star-schema\">semantic model design<\/a> and <a href=\"https:\/\/learn.microsoft.com\/en-us\/power-bi\/developer\/projects\/projects-report\">PBIR<\/a>.<\/p>\n<\/section>\n<section class=\"lm-section lm-semantics\" aria-labelledby=\"lm-semantics-title\">\n<div class=\"lm-section-heading lm-section-heading--wide\">\n<p class=\"lm-eyebrow lm-eyebrow--dark\">SEMANTIC VALIDATION<\/p>\n<h2 id=\"lm-semantics-title\">A valid DAX measure can still return the wrong result.<\/h2>\n<p>A simple Set Analysis expression may have a direct DAX equivalent. More complex expressions may use a different selection scope, nested aggregation, or alternative state. Each critical measure must be checked against defined source results.<\/p>\n<\/p><\/div>\n<figure class=\"lm-code-figure\">\n<div class=\"lm-code-grid\">\n<div class=\"lm-code-panel\"><span class=\"lm-code-label\">QLIKVIEW \/ ILLUSTRATIVE EXPRESSION<\/span><\/p>\n<pre><code>Sum({&lt;Year={2026}&gt;} Sales)<\/code><\/pre>\n<\/div>\n<div class=\"lm-code-panel\"><span class=\"lm-code-label\">POWER BI \/ CANDIDATE DAX<\/span><\/p>\n<pre><code>CALCULATE(\n    SUM(Sales[Amount]),\n    'Date'[Year] = 2026\n)<\/code><\/pre>\n<\/div><\/div><figcaption>Illustrative mapping, not a verified conversion. The model relationships and existing filter context determine whether the two expressions return equivalent results. See the <a href=\"https:\/\/learn.microsoft.com\/en-us\/dax\/calculate-function-dax\/\">Microsoft CALCULATE reference<\/a>.<\/figcaption><\/figure>\n<div class=\"lm-principle\"><span class=\"lm-principle__mark\" aria-hidden=\"true\">\u2713<\/span><\/p>\n<p><strong>Release rule:<\/strong> A critical KPI passes only when its agreed test cases meet the accepted results and tolerances. Generated code alone does not pass this test.<\/p>\n<\/div>\n<\/section>\n<section class=\"lm-section\" aria-labelledby=\"lm-decision-title\">\n<div class=\"lm-section-heading lm-section-heading--wide\">\n<p class=\"lm-eyebrow lm-eyebrow--dark\">READER TOOL \/ SCOPE DECISION<\/p>\n<h2 id=\"lm-decision-title\">Move the reports that the business still needs.<\/h2>\n<p>Use this matrix with the report owner. Check business needs and technical dependencies before you agree on scope.<\/p>\n<\/p><\/div>\n<div class=\"lm-table-scroll\" role=\"region\" aria-label=\"Migration decision matrix\" tabindex=\"0\">\n<table class=\"lm-table lm-table--decision\">\n<caption>Migration decision matrix. The conditions are practical guidance, not automated scoring rules.<\/caption>\n<thead>\n<tr>\n<th scope=\"col\">Decision<\/th>\n<th scope=\"col\">Suitable condition<\/th>\n<th scope=\"col\">Action<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<th scope=\"row\"><span class=\"lm-chip lm-chip--green\">Migrate<\/span><\/th>\n<td>The report is used, its logic is understood, and its required behavior maps to Power BI.<\/td>\n<td>Reuse approved data and KPI definitions. Validate each critical result.<\/td>\n<\/tr>\n<tr>\n<th scope=\"row\"><span class=\"lm-chip lm-chip--blue\">Redesign<\/span><\/th>\n<td>The business need remains, but the QlikView model or interaction has no suitable direct mapping.<\/td>\n<td>Agree on target behavior and new acceptance tests before implementation.<\/td>\n<\/tr>\n<tr>\n<th scope=\"row\"><span class=\"lm-chip lm-chip--gray\">Retire<\/span><\/th>\n<td>The report has no confirmed owner or need, or its purpose is already served elsewhere.<\/td>\n<td>Confirm dependencies and obtain owner approval before removal.<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/div>\n<\/section>\n<section class=\"lm-section\" id=\"lm-estimator-section\" aria-labelledby=\"lm-estimator-title\">\n<div class=\"lm-section-heading lm-section-heading--wide\">\n<p class=\"lm-eyebrow lm-eyebrow--dark\">READER TOOL \/ BUDGET WORKSHEET<\/p>\n<h2 id=\"lm-estimator-title\">Turn an existing effort estimate into a budget.<\/h2>\n<p>You do not need to estimate the days yourself. Our assessment defines the work. If you have an effort plan, use this worksheet. It applies EUR 800 per consultant day, excluding VAT.<\/p>\n<\/p><\/div>\n<div class=\"lm-estimator\" data-lm-estimator data-day-rate=\"800\">\n<div class=\"lm-estimator__top\"><strong>Preliminary services worksheet<\/strong><span>Rate: EUR 800 \/ consultant day<\/span><\/div>\n<div class=\"lm-table-scroll\" role=\"region\" aria-label=\"Effort worksheet\" tabindex=\"0\">\n<table class=\"lm-table lm-table--inputs\">\n<caption>Enter days from an existing effort plan. Leave unknown values blank.<\/caption>\n<thead>\n<tr>\n<th scope=\"col\">Work package<\/th>\n<th scope=\"col\">Your estimate in days<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<th scope=\"row\">Discovery and source analysis<\/th>\n<td><input type=\"number\" min=\"0\" max=\"100000\" step=\"0.5\" inputmode=\"decimal\" placeholder=\"0\" aria-label=\"Discovery and source analysis days\" data-lm-days><\/td>\n<\/tr>\n<tr>\n<th scope=\"row\">Data pipelines and transformations<\/th>\n<td><input type=\"number\" min=\"0\" max=\"100000\" step=\"0.5\" inputmode=\"decimal\" placeholder=\"0\" aria-label=\"Data pipelines and transformations days\" data-lm-days><\/td>\n<\/tr>\n<tr>\n<th scope=\"row\">Semantic model and KPI migration<\/th>\n<td><input type=\"number\" min=\"0\" max=\"100000\" step=\"0.5\" inputmode=\"decimal\" placeholder=\"0\" aria-label=\"Semantic model and KPI migration days\" data-lm-days><\/td>\n<\/tr>\n<tr>\n<th scope=\"row\">Report build and interactions<\/th>\n<td><input type=\"number\" min=\"0\" max=\"100000\" step=\"0.5\" inputmode=\"decimal\" placeholder=\"0\" aria-label=\"Report build and interactions days\" data-lm-days><\/td>\n<\/tr>\n<tr>\n<th scope=\"row\">Validation and defect correction<\/th>\n<td><input type=\"number\" min=\"0\" max=\"100000\" step=\"0.5\" inputmode=\"decimal\" placeholder=\"0\" aria-label=\"Validation and defect correction days\" data-lm-days><\/td>\n<\/tr>\n<tr>\n<th scope=\"row\">Deployment and handover<\/th>\n<td><input type=\"number\" min=\"0\" max=\"100000\" step=\"0.5\" inputmode=\"decimal\" placeholder=\"0\" aria-label=\"Deployment and handover days\" data-lm-days><\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/div>\n<div class=\"lm-estimator__result\" aria-live=\"polite\">\n<div><span class=\"lm-estimator__result-label\">Total consultant days<\/span><strong data-lm-total>Not calculated<\/strong><\/div>\n<div><span class=\"lm-estimator__result-label\">Illustrative services budget<\/span><strong data-lm-budget>Enter days above<\/strong><\/div>\n<\/p><\/div>\n<p class=\"lm-footnote lm-estimator__disclaimer\">Formula: total estimated consultant days \u00d7 EUR 800. This worksheet converts a known effort estimate into a budget. It does not estimate the work or provide a quotation. It excludes VAT, licenses, infrastructure, and other agreed project costs. Fixed-price work requires a defined scope.<\/p>\n<\/p><\/div>\n<\/section>\n<section class=\"lm-section\" aria-labelledby=\"lm-accept-title\">\n<div class=\"lm-section-heading lm-section-heading--wide\">\n<p class=\"lm-eyebrow lm-eyebrow--dark\">ACCEPTANCE AND DELIVERY<\/p>\n<h2 id=\"lm-accept-title\">Approve the results, not just the converted files.<\/h2>\n<p>We agree on test data, expected results, and approval roles before release. We record each critical test against its source definition.<\/p>\n<\/p><\/div>\n<div class=\"lm-card-grid lm-card-grid--three\">\n<div class=\"lm-card\"><span class=\"lm-card__index\">RESULTS<\/span><\/p>\n<h3>KPI reconciliation<\/h3>\n<p>Compare defined measures under equivalent periods, filters, and source data snapshots. Record tolerances and unresolved differences.<\/p>\n<\/div>\n<div class=\"lm-card\"><span class=\"lm-card__index\">ACCESS<\/span><\/p>\n<h3>Security tests<\/h3>\n<p>Verify user roles and restricted data. Power BI row-level security applies to workspace Viewers, not workspace Admins, Members, or Contributors.<\/p>\n<\/div>\n<div class=\"lm-card\"><span class=\"lm-card__index\">OPERATIONS<\/span><\/p>\n<h3>Go-live readiness<\/h3>\n<p>Check refresh, report behavior, performance, ownership, documentation, and cutover conditions with the responsible team.<\/p>\n<\/div><\/div>\n<p class=\"lm-footnote\">The Power BI security distinction is documented in <a href=\"https:\/\/learn.microsoft.com\/en-us\/power-bi\/service-admin-rls\">Microsoft&#8217;s row-level security guidance<\/a>. Functional acceptance remains specific to the agreed project.<\/p>\n<\/section>\n<section class=\"lm-section lm-section--commercial\" aria-labelledby=\"lm-commercial-title\">\n<div class=\"lm-section-heading lm-section-heading--wide\">\n<p class=\"lm-eyebrow lm-eyebrow--dark\">COMMERCIAL APPROACH<\/p>\n<h2 id=\"lm-commercial-title\">Know the rate. Define the work. Then agree on the price.<\/h2>\n<p>We can discuss your scope in a short call. Our consulting rate is <strong>EUR 800 per consultant day, excluding VAT<\/strong>. The assessment gives us a basis for an initial budget range. We can also offer a fixed price when we agree on scope, assumptions, and acceptance criteria.<\/p>\n<p>We confirm team availability and delivery dates for each project. A fixed deadline may require a smaller scope or a phased release. We identify these limits before we commit to a date.<\/p>\n<p>For broader Power BI delivery and support services, see our <a href=\"https:\/\/www.leaplytics.de\/services\/power-bi\/\">Power BI consulting overview<\/a>.<\/p>\n<\/p><\/div>\n<\/section>\n<aside class=\"lm-final-cta\" aria-labelledby=\"lm-final-title\">\n<div>\n<p class=\"lm-eyebrow\">NEXT STEP<\/p>\n<h2 id=\"lm-final-title\">Start with a scope discussion, not a full project commitment.<\/h2>\n<p>A short call helps us understand your applications, critical KPIs, and deadline. You do not need to provide full system access for this first discussion. We can then agree on the assessment inputs and next steps.<\/p>\n<\/p><\/div>\n<p>    <a class=\"lm-button lm-button--primary\" href=\"https:\/\/www.leaplytics.de\/kontakt\/\">Request a 30-minute scoping call <span aria-hidden=\"true\">\u2197<\/span><\/a><br \/>\n  <\/aside>\n","protected":false},"excerpt":{"rendered":"<p>QLIKVIEW TO POWER BI MIGRATION Move to Power BI. Keep your KPIs consistent. We migrate QlikView data models, scripts, calculations, and reports to Power BI. Our software automates supported work. Our engineers review exceptions and validate critical KPIs against approved QlikView results. Discuss scope and deadline \u2197 See assessment deliverables \u2193 We confirm scope, delivery &hellip; <\/p>","protected":false},"author":2,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-12086","page","type-page","status-publish","hentry","latest_post"],"_links":{"self":[{"href":"https:\/\/www.leaplytics.de\/el\/wp-json\/wp\/v2\/pages\/12086","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.leaplytics.de\/el\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.leaplytics.de\/el\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.leaplytics.de\/el\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.leaplytics.de\/el\/wp-json\/wp\/v2\/comments?post=12086"}],"version-history":[{"count":2,"href":"https:\/\/www.leaplytics.de\/el\/wp-json\/wp\/v2\/pages\/12086\/revisions"}],"predecessor-version":[{"id":14861,"href":"https:\/\/www.leaplytics.de\/el\/wp-json\/wp\/v2\/pages\/12086\/revisions\/14861"}],"wp:attachment":[{"href":"https:\/\/www.leaplytics.de\/el\/wp-json\/wp\/v2\/media?parent=12086"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}