QuerySurge Mapping Studio
Align evolving data requirements with validation
and convert mappings into tests with AI
Bring mapping documentation and data validation together. Create or import mappings, standardize requirements, and generate validation tests through integration with QuerySurge AI.
The Challenge
Data mappings define how data should move and transform.
But when mappings live in spreadsheets and tests are maintained separately, developers and testers must manually connect what the data should do with what the tests check.
Teams must translate transformation logic and business rules into test SQL, track which tests support each requirement, and identify what needs updating when requirements change.
Scattered files and inconsistent documentation make this work difficult to coordinate and maintain.
The Risk
- As requirements evolve, documentation and testing can drift apart.
- Tests continue checking outdated logic while new transformations or business rules go untested.
- Without clear connections between mappings and tests, teams can overlook affected validation assets, spend more time investigating changes, and allow data errors to reach downstream systems and reports.
The Solution
QuerySurge Mapping Studio connects documented data requirements to the tests used to validate them.
Mapping Studio brings mapping documentation and validation assets into one environment, giving developers and testers a shared reference for how data should behave.
Mapping Studio then converts all mappings into tests using QuerySurge AI.
Here’s how Mapping Studio addresses 5 practical problems:
Problem |
How Mapping Studio helps |
|---|---|
Mapping documents are scattered across files |
Brings mappings into QuerySurge alongside the validation assets they support. |
Teams document requirements inconsistently |
Reusable layouts, required fields, and defaults establish common documentation standards. |
Writing tests from mappings takes manual effort |
Integration with QuerySurge Mapping Intelligence generates tests from mappings, reducing manual SQL development. |
It’s difficult to identify tests affected by a change |
Links mappings to related tests so teams can identify what needs to be reviewed. |
Developers and testers lack a shared reference |
Keeps transformation logic, business rules, and validation requirements in the same environment. |
How Mapping Studio Works
- Create and maintain mappings directly in QuerySurge or import existing Excel and CSV documents via a guided wizard that maps spreadsheet columns to layout fields and verifies required values and field compatibility.
- Use the visual layout editor to build reusable Mapping Layouts with configurable fields, required values, and defaults.
- Capture source and target details, transformation logic, business rules, ownership, and validation requirements using your team’s documentation standards.
- Automatically convert mappings to tests, using QuerySurge AI: Mapping Intelligence.
QuerySurge Mapping Studio connects what your data should do with the tests that verify it.
Centralize your mapping documentation, standardize requirements, and generate tests with QuerySurge AI.
Reduce manual effort and keep validation aligned as your requirements evolve.
Frequently Asked Questions
- What is QuerySurge Mapping Studio?
- What is a data mapping document?
- What problem does Mapping Studio solve?
- Who is Mapping Studio for?
- Can I import my existing mapping spreadsheets?
- Can I create mappings directly in QuerySurge?
- What is a Mapping Layout?
- Our teams all document mappings differently. Can Mapping Studio help?
- How does Mapping Studio generate tests?
- How much time does AI-generated testing save?
- Can I review the tests before they run?
- Which AI platforms does it work with?
- What happens when a mapping changes?
- How do Mapping Studio and Validation Lineage work together?
- How does Mapping Studio help with audit and governance?
- Which version of QuerySurge includes Mapping Studio?
- Is Mapping Studio an additional cost?
Mapping Studio brings your data mapping documentation into QuerySurge, alongside the tests that validate it. Your team gets one shared reference for how data should move and transform, and QuerySurge AI turns those mappings into tests.
A data mapping document (also called a source-to-target mapping, or STTM) describes how data moves from a source system to a target. It covers field-level details, transformation logic, and business rules. It's the specification your data validation tests should be checking against.
In most organizations, mappings live in spreadsheets and tests are maintained somewhere else. Teams have to translate mapping logic into test SQL by hand, track which tests cover which requirements, and figure out what needs updating when something changes. Mapping Studio connects the two, so documentation and testing don't drift apart.
Data architects and analysts who write mapping documents, ETL and data engineers who build pipelines, and testers who validate them. It gives all three groups the same reference point.
Yes. Mapping Studio imports existing Excel and CSV mapping documents, so you don't have to rebuild your documentation from scratch.
Yes. You can create and maintain mappings in Mapping Studio, or import them and keep editing them there.
A Mapping Layout is a reusable template that defines how mappings are documented. It has configurable fields for source and target details, transformation logic, business rules, and validation requirements, so every team documents mappings the same way.
Yes. Reusable Mapping Layouts set a common documentation standard across teams and projects, which makes mappings easier to review, maintain, and turn into tests.
Mapping Studio works with QuerySurge AI: Mapping Intelligence, which converts mappings into validation tests written in native SQL, including tests of transformation logic. That cuts down the SQL your team has to write by hand.
Writing a test by hand takes about an hour per mapping. Mapping Intelligence can convert 200 mappings per hour, so 1,000 mappings take about 5 hours instead of 1,000.
Yes. Generated tests are native SQL that your team can review, edit, and approve before they're added to test suites and schedules.
QuerySurge AI supports OpenAI and IBM watsonx as AI endpoints, and it can be deployed as QuerySurge AI Cloud or as Core, which runs on-premises in your infrastructure.
Because mappings are linked to their tests, your team can see which validation assets are affected. Validation Lineage shows the full chain of dependencies, from mapping to query to test suite to schedule.
Mapping Studio is where requirements are documented and turned into tests. Validation Lineage shows how those requirements connect to tests, suites, and schedules, so you can assess what a change affects and see which mappings have no tests yet.
It creates a traceable link from documented requirements to executed tests. That gives governance teams and auditors evidence that requirements were actually validated.
Mapping Studio is new in QuerySurge 15.
No. Mapping Studio is included with every paid QuerySurge license, along with Validation Lineage and QuerySurge AI. See Licensing & Pricing for package details.
