1  POST-MIGRATION WIZARD (PMW)

The Post-Migration Wizard (PMW) is a utility that helps you with some tasks after the migration that cannot be performed automatically.

1.1  Intro

The Intro panel welcomes you to the PMW and warns you that the changes made in it are permanent.

1.2  Company Settings

The Company Settings panel allows you to change general information about of your company. All of these can be changed later in the Subjects register.

1.3  Administrator Setup

The Administrator Setup panel shows a list of all users, from which you can specify administrators and accountants. There must be at least one administrator.

1.4  Referential Integrity Check

1.5  New FX Rate Format

This panel will allow you to convert the old exchange rates into the new format, where central, buy, and sell rates are all under one subject.

More about the new exchange rate format and the conversion to it.

1.6  Uporabniki in kontaktne osebe

More about how users and contacts are handled.

1.7  Disable the Post-Migration Wizard

Teh PMW is automatically started at PANTHEON startup. If you no longer need it, you can disable it in the Administration Panel | Settings | Task Autorun.

In the list on the top, find the PMW, highlight its row and press Ctrl + Delete to remove it from the list.

2  Compare Original and Migrated Database

The procedure PA_MIG50_55_ThroughTables is used to compare data in the original and the migrated database.

It checks all tables that have been involved in the migration and is used only here.

It compares data from the original databases (5.0) with the contents of views in the migrated database (5.5).

The table _MIGALL_table is created.

create table dbo._MIGALL_Table (acTableName VarChar(100), -- table name
	   anStatus Int, -- Status 1 - inconsistent data
	   acSQL VarChar(8000), -- displays errors
	   acNote) -- computed field with error description, related to anStatus field

If inconsistencies are found, primary keys of the conflicting records are saved into the table _MIGERR_<OldTableName>. Possible outcomes:

• If a record does not exist in one of the databases it is saved only once.
  
  
  The image shows a few recrods that haven't been transferred in the migration.
  
• If the original and the migrated records don't match, both are saved.
   
  
  The image shows non-matching records in the table POSLDOGSKLAD; in the original table, the records had NULL in the DATUMZAP field, but the Migrator inserted the dates - the migration date.

You can use the following SQL query to view the contents of the _MIGALL_Table table.

select acTableName, acSQL from _MIGALL_Table where anStatus = 1 order by acTableName

All select statements are shown in the migration log in the phase "Errors when comparing original and migrated data."