Importing from KPImailer v1

Brings reports from a previous KPImailer installation into this one. A guided import reads the old database, shows every report it finds, and recreates the selected ones here - layout, attachments, filters, recipients, schedules, and the links between chained reports included.

Permissions

The Import from KPImailer v1 button appears on the Reports page for users whose role includes the legacy migration permission, granted under Settings → Users & roles. The importer never changes the old database - it only reads from it.

Before you start

1. Register the old database. Add the previous installation’s database as a SQL Server data destination and make sure its connection test passes. Only SQL Server destinations are offered as import sources.
2. Connect the same Qlik apps. A report can only be imported when the Qlik app it is built on is available here. Add the apps under Repository and sync them - the importer can also trigger a sync inline for apps that are present but not synced yet.

Steps

1. Go to Reports and select Import from KPImailer v1.

2. Step 1 - Choose the legacy database. Pick the connection that points at the previous installation’s database, then select Scan for reports.

3. Step 2 - Select reports to import. Every report found in the old database is listed with its Qlik app, content summary, and a readiness badge:

   • Ready - the app is synced here; the report can be imported.
   • App not synced - the app exists here but has never been synced. Select Sync now to sync it without leaving the wizard.
   • App not found - the app is not configured here. Add and sync it under Repository, then rescan.

   Reports that were brought across before are marked Already imported. Use the filter box and Select all ready to build your selection, then select Continue.

   Chained reports stay together. A report that runs after another report shows a “Chains after” line naming the reports it depends on. Ticking it also ticks every report it chains after, and unticking a report also unticks the reports that depend on it, so a chain is always imported whole. If a report it chains after was already imported earlier, the link simply reconnects to the existing copy; if it cannot be imported here at all, the row says so and only that chain link is skipped.

4. Step 3 - Import options. If any selected report exports data to SQL, choose the data destination those exports should write to, or leave it on Assign later and set it per report in the editor. Tick Import already-imported reports again only if you deliberately want copies.

5. Select Import (the button shows how many reports are selected). Each report is imported separately - parents in a chain first - so one failure never affects the others. The results screen shows the outcome per report - Imported, Imported with warnings, Skipped, or Failed - and how many report-chaining links were restored. Expand a report’s warnings to see exactly what could not be carried over, or select Open to jump straight into its editor.

What the warnings mean

The import is best-effort by design: whatever has a direct equivalent is recreated, and anything that does not is dropped with a warning instead of blocking the whole report. Typical examples are features the previous version had that this one replaces differently - per-report alert settings (use Alerting instead), Telegram delivery, Excel conditional-formatting rules, and day-of-month date overrides. The warning list on the results screen is per report, so you always know what to double-check.

After the import

Imported reports always arrive disabled so nothing starts sending unannounced. For each one: open it in the editor, arrange the email layout (imported content is stacked top-to-bottom, ready to rearrange), review the data scope and recipients, assign a SQL export destination if you chose Assign later, send yourself a test run, and only then enable it in the schedule.

Worked example

After upgrading, an administrator adds the old server’s database as a SQL Server data destination named KPImailer v1, then selects Import from KPImailer v1 on the Reports page. The scan finds 38 reports; 31 are Ready, 5 need a Sync now, and 2 reference an app that was retired years ago and stay unimported. They select all ready reports, pick the warehouse destination for the SQL exports, and run the import: 36 reports arrive disabled, 4 of them with warnings about dropped Telegram delivery. After reviewing each one in the editor, they enable the reports over the following week.