---
title: "Verify sync mapping changes affect the intended fields"
description: "Test a sandbox integration field-map update, checking the next synchronized record and the documented treatment of previously imported data."
canonical_url: "https://vostride.com/agent-library/integrations-sync/field-mapping-change.md"
md_url: "https://vostride.com/agent-library/integrations-sync/field-mapping-change.md"
content_kind: "recipe"
topic: "integrations-sync"
---

# Verify sync mapping changes affect the intended fields

Test a sandbox integration field-map update, checking the next synchronized record and the documented treatment of previously imported data.

## Risk

A mapping editor can save labels while retaining stale internal field identifiers. Use source values that differ clearly between fields and verify both new imports and any promised backfill semantics independently.

## Fixtures

- An owned sandbox source with separate department and cost-center fields containing distinct synthetic values.
- A disposable destination schema with Team and Accounting code fields, a test administrator, and a documented mapping-change backfill policy.
- A source/destination oracle recording field identifiers and an external source fixture able to create one new record after the mapping change.

## Steps

1. Open the connector mapping editor and verify the original source-to-destination field associations against the fixture baseline.
2. Change the intended association, save, reopen the editor, and verify the underlying displayed field choices remain the new mapping.
3. Create the prepared new source record externally, complete a sync cycle, and verify its destination fields contain the correctly mapped distinct values.
4. Inspect the independent mapping and record oracle, then check the earlier imported record and verify it follows the documented preserve-or-backfill policy without changing unrelated fields.

## Expected results

- The saved mapping binds the intended source and destination field identities.
- New data follows the updated mapping with no swapped or stale field value.
- Existing records follow the stated backfill policy and preserve unrelated attributes.

## False-pass traps

- Identical source values in both fields make a swapped mapping invisible.
- A saved mapping label can conceal a stale internal destination field identifier.

## Cleanup

- Restore the original mapping and remove the new sandbox source and destination records.

## Use with agent-qa

Adapt this test design to your application's acceptance criteria and configured target using the [recipe execution guide](/agent-library/software-factory/turn-a-recipe-into-an-agent-qa-test.md). External fixture setup and non-UI checks require your own supported hooks or test tooling. Validate the authored test, execute it, and inspect the completed evidence; this recipe is not a recorded test result.

## References

- [agent-qa first test](/docs/agent-qa/guides/first-test.md)
- [agent-qa hooks](/docs/agent-qa/guides/hooks.md)
- [agent-qa test](/docs/agent-qa/configuration/test.md)

- [Integration and synchronization QA recipes](/agent-library/integrations-sync.md)
- [Software factory QA library](/agent-library.md)