At a glance
- Rig agrees a fixed delivery price after scoping the data, logic and integrations.
- Data moves in checked waves, with a parallel run where the systems allow it.
- History and permission tests are part of acceptance.
- Your system owners approve the mappings and the cutover.
Records, logic and owners
Source to target definitions
Counts, totals and access
Sign-off and rollback plan
Map the data and the logic it carries
The table is a starting inventory, and the target edition, customisations and API access decide the final mapping. Check each object even when the name matches, because an object with the same name can behave differently in the target.
| Source | Target or retained output | Checks and known traps |
|---|---|---|
| Qlik load scripts and QVDs | Warehouse transformation models | Preserve incremental loads, keys and transformations. |
| Set analysis and variables | Target metric definitions | Test selection behaviour and aggregation. |
| QlikView documents and Qlik Sense apps | Target reports | Inventory extensions, Section Access and bookmarks. |
QlikView support dates to plan around
Qlik has not published an end of life for QlikView as a product, but each release has its own end of support. Qlik’s lifecycle table lists support for QlikView 12.90 ending on 31 October 2026 and for 12.100 ending on 30 September 2027. A team on 12.90 or older is now outside support unless it upgrades.
Qlik alternatives: Power BI, Sigma, Omni or Tableau
Power BI suits organisations already on Microsoft reporting that can maintain DAX. Sigma puts a spreadsheet interface on live warehouse data, Omni builds exploration on a shared semantic model, and Tableau suits teams that work in visual analysis. Qlik Sense and Qlik Cloud are the routes Qlik itself offers. Whichever you shortlist, test set analysis and selection behaviour first, because associative filtering does not carry over to another tool by default.
| Target | Fits when | Test first |
|---|---|---|
| Power BI | You already use Microsoft reporting and can maintain DAX | Set analysis rewritten as DAX measures |
| Sigma | Business users want a spreadsheet interface on the warehouse | Load script logic moved into warehouse models |
| Omni | You want exploration on a shared semantic model | Imported definitions against QlikView results |
| Tableau | Analysts work in visual analysis and workbooks | Section Access rebuilt as user filters or row-level security |
| Qlik Sense or Qlik Cloud | You want to stay with the associative model | Converted apps against the QlikView originals |
How a migration runs in Rig
Rig maps the systems and data across your estate, connects the source and target, and maps one schema to the other with previews of real records. Rig engineers agree the objects and history in scope with your team, prepare the destination and rehearse the load before they reconcile the results. Sign-off, cutover and follow-up tasks sit in the same migration workspace.
Agree a timeline against the actual scope
The table gives a planning allowance for each phase, and the assessment turns it into a dated plan for the whole project. Large estates need several waves, and application configuration can add time.
| Phase | Initial planning allowance | Exit check |
|---|---|---|
| Assessment | 3 to 5 working days | Owners, access and inventory agreed |
| Sample and mapping | 5 to 10 working days | Sample records and exceptions reviewed |
| Build and parallel validation | 2 to 6 weeks per wave | Counts, totals and permissions accepted |
| Final sync and cutover | 1 to 3 working days per wave | Business owner signs off; rollback remains available |
Keep the evidence for each migration wave
For each wave you receive the source-to-target mappings, a reconciliation report, an exception log and a cutover checklist. The checks cover duplicates, missing relationships, deleted records, time zones and permissions as well as headline totals, and the old system stays available until the agreed retention and rollback checks pass.
Where Rig may fall short
A migration that only needs a supported CSV import may be simpler to do yourself. Sub-minute operational replication, a full ERP implementation and specialist application redesign need a separate scope or another provider. Where Rig Ingest moves the data, confirm connector coverage for each source before you commit.
Inside Rig Migrate
Run the migration in Rig, from the systems map to cutover
Rig natively maps systems and data across your IT estate, connects source and target systems, scopes the move and maps one schema to another. The same migration workspace tracks destination preparation, rehearsals, reconciliation, sign-off and the work after cutover, so your team can review the decisions and progress in one place.
Map the IT estate
Map systems, data and integration flows across the IT estate. See which reports, processes and teams depend on the systems you plan to change.
Set up the migration
Create the migration in Rig and record the source, destination and work to deliver. Keep the migration tasks and progress together.
Connect and discover
Connect the source and target systems, then inspect their schemas and available data. Confirm access before deciding how each object will move.
Scope the work
Choose the objects, fields and history to migrate. Record what stays, what changes and the dependencies the migration needs to preserve.
Map schema to schema
Map source objects and fields to the target schema. Preview records and review rules to copy, translate, calculate, link, look up and match owners.
Prepare the destination
Track the target preparation needed before loading data, including its configuration and the relationships your mapped records will use.
Rehearse the load
Dry run the whole load and rehearse it in the destination environment. Review the results and resolve issues before the production cutover.
Reconcile and sign off
Compare source and target records, relationships and business totals. Review exceptions with the system owners and record acceptance before proceeding.
Cut over
Work through the agreed cutover tasks in Rig. Coordinate the final load and user switch with the people who own the systems.
Check after cutover
Track the checks after the switch, confirm that reporting and processes work, and resolve outstanding issues before retiring the old setup.
Review reporting definitions before rebuilding
Keep the metric definitions and relationships behind your reporting available while you rebuild. Compare the target reports against the original calculations and access rules.

Reporting migration at Birdie
Birdie reports rebuilding sales and marketing reporting in less than a day. Its team kept Snowflake and the existing Fivetran pipelines; retirement of the Looker licence is not confirmed.
Read the migration case studyCommon questions
Is QlikView end of life?
Qlik has not announced an end of life for QlikView itself. Each release has its own end of support: according to Qlik’s lifecycle table, support for 12.90 ended on 31 October 2026 and 12.100 is supported until 30 September 2027.
What are the main Qlik alternatives?
The targets compared on this page are Qlik Sense or Qlik Cloud, Power BI, Tableau, Sigma and Omni. Compare them on one report that uses set analysis and Section Access before deciding.
Can Rig convert QlikView load scripts automatically?
Rig does not rely on automatic conversion. Its engineers rewrite load scripts as warehouse transformation models and set analysis as metric definitions, then compare the results with QlikView number by number.
How much does a migration cost?
Rig maps the work and agrees a fixed delivery price before the migration starts. Source access, custom logic, history and the number of integrations affect the scope. Platform and third-party licence costs are agreed separately.
Can we keep reporting history?
Yes, where the source lets you extract it. You decide which history the target system needs and which stays in a governed archive, and Rig reconciles both against the original records.
How do you check that the data matches?
Rig compares record counts, identifiers, relationships and business totals for each wave. Every exception goes in a log, and the business owner has to accept the results before cutover.
Will both systems run during the move?
Yes, where the systems and licences allow it. Before the parallel run starts, you agree which system is the source of truth, how final changes are handled, the rollback conditions and the point at which users switch.
Who does the implementation?
Rig engineers do the work with your system owners, and your team approves the mappings, permissions and acceptance checks. Application configuration and specialist ERP or CPQ work is either written into the scope or assigned to your application partner.
Is there a guaranteed completion date?
The assessment produces a dated plan. Access, data quality, target readiness and user acceptance can all move it, so treat any planning range given before the assessment as an estimate.
Sources and product details
Vendor information checked on 20 November 2026. Confirm current editions, licence terms and prices with the vendor before buying.