Migration process

Migration process

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.

Idea
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.

Warning
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.

Warning
No further data migrations from version 1 will be performed after go-live.
    • Related Articles

    • Release Notes Archive - 2025

      New Release: 2025-12-02 This release focuses on usability improvements, purchasing and transport enhancements, extended APIs for BI and reporting, webhooks migration, and stability fixes. Usability and documents: Better handling of dates, currencies, ...
    • Release Notes Archive - 2023

      2023-12-11 A major update regarding report layouts have been implemented. We now have an architecture that allows customer specific report layouts. This will be released over time, starting with the purchase report. Over time this will be supported ...
    • Release Notes Archive - 2024

      2024-12-15 We have added additional support for optimizing the calculation of the number of plates when printing multiple signatures with similar colors. When you specify the editions you can now add information about unique colors. This will be ...
    • How to Add a New Article/Resource

      Goal This article explains how to add a new article in the system for purchasing. You will create the article record, complete key fields, and add pricing and settings. Procedure Step 1: Open the articles overview In the Purchase area, click Article ...
    • Creating an invoice

      Goal This article explains how to create and approve an invoice from an existing order in the system. You will review the order details, add transport cost if needed, convert the order to an invoice, preview it, and then approve it so it receives an ...