New Quattrol365 Laboratory Migration

Description, Purpose and Objective

NOTE

The Quattrol365 New Laboratory Migration console is an administrative tool designed to restructure, standardize and securely transfer the entire configuration and analytical history of a laboratory from the previous architecture (version 1) to the new optimized database model (version 2) on the Quattrol platform.

The purpose of this module is to allow a transparent transition for the end user without loss of information, offering a controlled environment to simulate data transfer and validate the integrity and logical mappings (tests, measurands, methods, instruments, batches, calibrations and historical results) before consolidating the changes in the production environment.

---

Context of Use

This panel is operated exclusively by authorized system administrators, IT support personnel, or quality managers during the client upgrade process. It is used when:

• Migrating a lab whose Quattrol membership version is registered to the old model (version: 'v1') is required.
• A preventive audit of analytical data through technical simulations is needed to mitigate database inconsistencies before an update deployment.

---

Step by Step for Migration

To safely transfer laboratory data, follow the following operating instructions:

1. Select the Laboratory to Migrate

1. Go to the Quattrol365 New Laboratory Migration module screen.
2. Locate the Laboratory* text field and drop-down list.
3. Type the name of the laboratory or select it directly from the autocomplete list.
   • Note: The list will automatically filter only organizations that have their Quattrol membership configured in the previous version (v1).

---

2. Choose and Execute the Migration Mode

Depending on the level of validation required in the procedure, click one of the available action buttons:

Option A: Simulate migration

This action performs a test or technical simulation of the complete transfer of information without altering the production operation of the laboratory.

1. With the lab selected, click the Simulate Migration button.

2. The system will begin the extraction of assays, measurands, methods, instruments, reagent lots, calibrations, averages and analytical results.
3. The simulated data will be temporarily stored in a sandbox (/migration/[ID-Organización]).
4. Wait for the notification to appear on the screen: "The simulation has completed successfully."

Option B: Migrate from simulation

Use this two-step flow after verifying that the presimulation process completed without integrity errors.

1. With the lab selected and having successfully run the previous simulation, click Migrate from simulation.

2. The database engine will take as a source the isolated backup generated in the simulation and inject it directly into the final productive collections.
3. Upon completion, the organization membership will be automatically updated to the new version (v2).
4. Check the confirmation: "The migration has completed successfully."

Option C: Migrate

This action executes the migration directly, immediately and definitively towards the new model.

1. Make sure the selected lab is not currently operating critical transactions.
2. Click the Migrate button.
3. The system will extract and transform historical records in real time, writing them in direct block to the new database architecture.
4. Wait for the console to process all batches of data and display the notification: "The migration has completed successfully."

---

Roles and Permissions Required

To access and interact with this advanced administration module, the user must have a IT Support or Super Administrator role and have the following specific permissions active:

• Access and display: data_migration_read (for general restructuring consoles) or migrate_lab_new_model_read (for updating laboratories to v2).
• Write and execute operations: data_migration_create / data_migration_update or migrate_lab_new_model_create / migrate_lab_new_model_update that allow scripts to be launched on the production database.