Goal

This article explains the end-to-end process to migrate from the legacy environment (version 1) to the new environment (version 2). It describes each phase, responsibilities, approvals, and what happens at go-live.

Procedure

Step 1: Plan the migration

Our team and your organization create a detailed migration plan together. The plan lists all activities, estimated time, responsibilities, and deadlines. It is documented in a migration contract and signed by both parties before the project starts.

A new license contract is also signed by both parties.

A 20-hour migration retainer is included at no extra cost. Any extra needs (for example, premium support, additional training, consultancy, or development) are offered separately.

Step 2: Perform the first migration

Our team sets up a new account in version 2 and migrates data from version 1 according to the agreed migration plan.

Step 3: Run the parallel phase

During the parallel phase, both parties test and validate the new account:

• Our team performs general system tests.
• Your team tests your specific configuration and requirements.

All tests are performed using a dedicated checklist to ensure standards and best practices are followed.

Step 4: Approve the results

When the checklist from the parallel phase is accepted, the contract is signed again by both parties to confirm readiness for go-live.

Step 5: Perform the final migration

Our team runs the final migration with the latest data from version 1 to version 2.

Any data updated in version 2 during the parallel phase will be overwritten by the data from version 1 during the final migration.

Step 6: Go-live

After the final migration completes, your organization is ready to go live on version 2.

From this point, the version 1 environment is kept only as a historical archive. All new business must be carried out in version 2.

No further data migrations from version 1 will be performed after go-live.