Preparing an anonymized database copy

Choose a development database

Before you start, check that the project uses a copy intended for testing, not the client’s production database. Keep a backup of the current state; the panel reminds you about it before running the operation.

Match the rules to the schema

A profile defines the columns, replacement values and replacement conditions. Profiles are available for PrestaShop and WooCommerce. For your own database, prepare conditional rules or order a profile tailored to your system.

Preview the scope before writing

Do a dry run first. You will see the number of rows affected and the expected result. Compare the plan with the scan report, especially the columns not covered by the profile.

Check the database afterwards

Anonymization is followed by another scan. Its result goes into the project log. Review the findings and check the application: data relationships and test scenarios should still work.

Checking files is a separate task

Database anonymization does not change attachments, logs, PDF invoices or earlier backups. Check them separately before sharing the environment.

When the last measurement shows real data, clicking “Connect” requires confirmation before the agent starts. The message helps you decide based on the saved result.