Under Database on the navigation pane, open the Migrate company view.
The Migrate company view is used to migrate company data from Opera 3 (Visual Foxpro database) or Opera 3 (SQL Server database).
Pegasus Opera II data must first be migrated to either Opera 3 (Visual Foxpro database) or Opera 3 (SQL Server database) before it can be migrated to Opera 3 SQL SE.
The company data is copied followed by any associated files (for example, statements and remittances).
A 'Health check' must be done before the migration.
A new company is created automatically in Opera 3 SQL SE by the migration.
If a problem is found during the migration the changes in Microsoft SQL Server can be rolled back.
If companies are linked to other companies (for example, Sales Ledger in company A is linked to the Nominal Ledger in company B), all those companies must be migrated together.
After the migration the Read/Write permissions for the Windows user account must be removed.
Option |
Description |
---|---|
System data | Relevant company records from the companies table (SEQCO),
plus the following tables:
|
Company data | All company data apart from spool files
The migration includes files saved by Opera in a Windows folder - like statements and remittances. These are migrated to the Opera 3 SQL SE Repository or to the Migration folder below the Common folder. |
The Migration folder below the Opera 3 SQL SE common folder is used for files from the source company that do not have an equivalent folder in Opera 3 SQL SE. Examples are emails and spool files. Please check that folder after the migration.
The root migration folder on the server is 'C:\ProgramData\Pegasus\O3 Server SE\Common\Migration'. A folder is created for each system and company beneath Migration.
The company data must be 'health checked' before the migration. This is important because the database rules in Opera 3 SQL SE are more strict than Opera 3 (Visual Foxpro database) or Opera 3 (SQL Server database).
All checks are advised.
Mandatory checks |
Example |
---|---|
Valid numeric rule |
A numeric overflow; a value of 100 has been added to a field which can only store the maximum value 99. A decimal place numeric overflow; a value of 999.9 has been added to a field which has been defined as 99.99. |
Valid date rule |
Dates prior to 01/01/1753 will error as they are not allowed in Microsoft SQL Server. Warnings are shown for dates prior to 1899. |
Minimum value rule |
Checks that fields do not contain values less than the defined minimum value if one has been defined. |
Maximum value rule |
Checks that fields do not contain values greater than the defined maximum value if one has been defined. |
Optional checks |
Example |
Named value rule |
A field entry is one of the list of specified values; for example, for a sales transaction type is it 'I' (invoice), 'C' (credit note), 'A' (adjustment) and so on. |
Pattern matching rule |
Entries must match a particular pattern; for example, a document reference must match 'XXXX9999' (where XXXX is a letter and 9999 is a number). |
Mandatory value rule |
A field must not be empty; for example, a customer record must have an account number. |
Unique value rule |
Checks that field entries are unique in a table if the field is defined as must be unique. For example, within the customer table, the customer code must be a unique. |
Referential integrity rule |
Checks table joins. Do child records have a parent record? For example, does a invoice transaction record have an invoice header record? |
Source |
|
---|---|
Opera folder |
Select the main Windows folder for Opera 3 (Visual Foxpro database), for example, 'C:\ProgramData\Pegasus\O3 Server VFP' or Opera 3 (SQL Server database), for example, 'C:\ProgramData\Pegasus\O3 Server SQL'. |
System |
Select the additional system required, if used. |
Companies |
Select the company or companies from the chosen system to migrate. |
Destination |
|
SQL Server |
Select the Microsoft SQL Server to be used for the Opera 3 SQL SE databases. |
Repository folder |
The default Repository folder is displayed. This can be changed to a different location. |
Common folder |
Administrators must create a network share and grant the necessary permissions to the users who will need access to this location in Windows Explorer, for example, to give access for banking software. The default Common folder is displayed. This can be changed to a different location. |
Migration log file |
The migration will save a log file in this folder. |
Migrate options |
|
Migrate system data |
Select to migrate users and reports from Opera 3 (Visual Foxpro database) or Opera 3 (SQL Server database). |
Migrate associated users |
Select to migrate users for the companies chosen for migration. This includes their menu access and menu favourites. |
Migrate reports |
Select to migrate company-specific reports. |
Migrate company data from Opera 3 (Visual Foxpro database)
Migrate company data from Opera 3 (SQL Server database).