What must be inventoried first?
List each product, release, connector, source and target. Export configuration where available and record ownership, schedules, permissions and the expected business results. Separate masking, related subsets and synthetic generation: a replacement may cover only some of these jobs.
How should candidates be compared?
Give each candidate the same representative schema and one rare business case. Check relationships, sensitive-field rules, target support and operational permissions. Ask vendors to demonstrate the licensed edition and migration of a real rule; do not assume a proprietary configuration will run unchanged elsewhere.
What makes cutover reversible?
Run old and new workflows in parallel with permitted, controlled inputs. Compare exact rows, privacy checks and runtime operations. Record ownership and an exit criterion, retain the old setup until acceptance and rehearse rollback. Support and migration depend on the product and version; confirm them with the vendor.
Candidates for this task
- K2view Test Data Management: Selects related business-entity data and supports masking; test the required source systems and targets.
- Solix Test Data Management: Creates reusable database subsets and clones; compare supported systems and masking requirements.
- Redgate Test Data Manager: Prepares masked database subsets through Anonymize and Subsetter; test the exact database versions.
- Synthesized TDK: Transforms and subsets source data in supported workflows; compare connectors and migrated rules.