Contract Migration

The purpose of this document is to document the user workflow in connection with the migration of contracts from the original (source) system of the leasing company to the OC.

In principle, the following are available 2 basic migration methods (in addition to manual contract casting):

• using a migration database ("full" migration)

  • If the migration is carried out via a migration database ("large" migration), the migrations also include the creation of so-called MDD documents (Migration Design Document) with a detailed description of the entities (tables) and fields of the migration database.

  • The process using the migration database (so-called full migration) is always tailored to the specific leasing company and is not part of the OC standard.

• Simple Migration

  • it is a combination of using Rapid Start packages and scripts that are prepared in OC. From now on, we describe only this type of migration.

Contract migration is different for each leasing company, I always have my own specifics. For a general description of the migration process in a specific project implementing the OneCore module, we recommend that you create a document in cooperation with the customer Migration strategy. The content of this document is:

• Prerequisites for a successful migration (necessary settings, rules, and allowed data combinations)

• Definition of the scope of migration (which entities (e.g. financing contracts, insurance contracts), what accounting records, etc.)

• Contract migration method (via migration database, via RapidStart, manually, etc.)

• Posting Records Migration Method (Detto)

• Migration Verification/Acceptance Process

• Processes following the desired target state of the database after the migration and before starting routine processing (taking into account changes and performing procedures not included in the migration)

Best practice:

In general, the vendor recommends establishing:

• Stand-alone Financing Products (other than products intended for new contracts). Here you need to use the special field on the Migration tab.

• Optionally, it is also possible to create specific

  • Financing Product Types,

  • Financing Models           

  • Financing templates, if needed (e.g. different numbering, different billing, etc.).

Later in the document, only the process for a simplified migration is described.

Navigation:

History:

Abbreviations used in the document: