Migration

    Move Crystal Reports and keep the documents people still use

    Crystal Reports files often hold the invoices, statements and operational documents that someone prints or emails every week. Rig inventories the reports that still run, rebuilds them as paginated reports or dashboards in the tool you choose, and checks each output against the original.

    By Rig · Last updated

    Get a migration plan

    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.
    01Inventory

    Records, logic and owners

    02Map and rebuild

    Source to target definitions

    03Run in parallel

    Counts, totals and access

    04Accept and switch

    Sign-off and rollback plan

    Each wave ends with an acceptance check. This diagram shows the delivery process.

    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.

    SourceTarget or retained outputChecks and known traps
    .rpt files, formulas and subreportsPaginated reports or rebuilt BIRewrite Crystal formulas and test grouping, totals and page breaks.
    Parameters and selection formulasTarget parameters and filtersCheck default values, cascading parameters and date handling.
    Scheduled runs and distributionTarget subscriptions and deliveryInventory recipients, formats such as PDF and Excel, and timing.
    Database connections and SQL commandsWarehouse views or governed modelsReplace embedded SQL with tested models where you can.

    Crystal Reports support dates from SAP

    SAP lists the end of mainstream maintenance for Crystal Reports 2020 as 31 December 2026, and for Crystal Reports 2025 as 31 December 2027. The developer version for Visual Studio is listed to 31 December 2027 as well. Check SAP’s page for the exact version and service pack you run.

    Choose a target for each kind of report

    Documents with a fixed layout, such as invoices and statements, suit paginated reporting, for example Power BI paginated reports or Power BI Report Server. Summary reports that people read on screen are better rebuilt as dashboards on a governed model. The inventory shows which reports have no recent runs or recipients, and those can be retired.

    Report typeLikely targetTest before cutover
    Invoices, statements and lettersPower BI paginated reports or Power BI Report ServerPage layout, totals and PDF output
    Operational lists and exportsPaginated reports or scheduled extractsFilters, parameters and file formats
    Management summariesDashboards on a governed modelTotals against the Crystal output
    Reports with no runs or recipientsRetireConfirm with the owner before switching off

    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.

    PhaseInitial planning allowanceExit check
    Assessment3 to 5 working daysOwners, access and inventory agreed
    Sample and mapping5 to 10 working daysSample records and exceptions reviewed
    Build and parallel validation2 to 6 weeks per waveCounts, totals and permissions accepted
    Final sync and cutover1 to 3 working days per waveBusiness 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.

    1. 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.

    2. 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.

    3. 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.

    4. Scope the work

      Choose the objects, fields and history to migrate. Record what stays, what changes and the dependencies the migration needs to preserve.

    5. 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.

    6. Prepare the destination

      Track the target preparation needed before loading data, including its configuration and the relationships your mapped records will use.

    7. 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.

    8. Reconcile and sign off

      Compare source and target records, relationships and business totals. Review exceptions with the system owners and record acceptance before proceeding.

    9. Cut over

      Work through the agreed cutover tasks in Rig. Coordinate the final load and user switch with the people who own the systems.

    10. Check after cutover

      Track the checks after the switch, confirm that reporting and processes work, and resolve outstanding issues before retiring the old setup.

    Rig migration task list showing the systems map, setup, connection, scope, design, destination preparation, rehearsal, reconciliation, cutover and after-cutover stages
    Migration stages and task progress in Rig. View the full-size screenshot.

    Inspect source values and target previews

    The migration workbench shows source fields, target previews and the rule for each mapping. Your team can review translated values, linked records and calculated fields before signing off the mapping and rehearsing the load.

    Rig Migrate workbench mapping a Dynamics 365 CE quote to Salesforce CPQ, with source values, target previews and translation, link and calculation rules
    A D365 CE to Salesforce CPQ example. The workbench shows mapping decisions and migration tasks; this is not a completed cutover. View the full-size screenshot.

    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 study

    Common questions

    Is Crystal Reports end of life?

    SAP lists the end of mainstream maintenance as 31 December 2026 for Crystal Reports 2020 and 31 December 2027 for Crystal Reports 2025. Check SAP’s maintenance page for the version and service pack you run.

    Can Crystal Reports move to Power BI?

    Yes, as paginated reports or as rebuilt dashboards. Rig rewrites Crystal formulas, subreports and selection formulas in the target, then compares each output with the original.

    What happens to scheduled Crystal Reports?

    Rig records each schedule, recipient and output format during the inventory and recreates them as subscriptions in the target. Both versions run in parallel until the owners accept the new outputs.

    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.

    Sources and product details

    Vendor information checked on 20 November 2026. Confirm current editions, licence terms and prices with the vendor before buying.

    Talk to Rig

    Plan the move around the work you need to keep

    Tell us where your team spends time, loses money or needs better information.
    In a 30-minute call, we’ll discuss the data and systems work that could help.

    Get a migration planUse the platform with your team, or add our engineers.