Record the existing symbol contract
Build a mapping sheet from the actual running configuration. Record the source identifier, destination symbol and suffix, price precision, contract assumptions and relevant session information. Note any reports, automated strategies or integrations which depend on the existing name or specification.
A destination symbol that looks familiar can still receive an unsuitable stream if the upstream identifier or specification changed. Keep mapping changes reviewable and give each exception an explicit decision. Confirm that the source permits the intended use of the data.
Compare feeds without changing the live meaning
| Review item | Test approach | Accept when |
|---|---|---|
| Symbol identity | Match old and proposed identifiers | The intended contract is unambiguous |
| Quote freshness | Observe updates during the expected session | Stale or missing data creates an actionable alert |
| Specification difference | Compare the agreed contract fields | Any difference is approved before release |
| Client dependency | Exercise representative connected tools | The expected workflow still uses the correct symbol |
A parallel observation period can reveal differences before clients depend on the new mapping. Use it to investigate behaviour, not to promise that independent sources must publish identical prices.
Prepare for a missing or interrupted stream
Distinguish an expected market closure from a source failure. Record which monitoring rules account for sessions and which rules identify a disconnected or stale feed. During an interruption, operators should know which symbols are affected and which party owns the upstream investigation.
- Test reconnection using approved test conditions.
- Document how a backup source is selected and how that change is recorded.
- Check mappings again after a connector or source update.
- Retain enough event evidence to explain a gap without storing unnecessary data.
Release a limited instrument group first
An illustrative migration can start with a small approved instrument group, complete the monitoring and mapping review, and then expand after the operating team accepts the result. The release plan should specify what triggers a pause or a return to the previous configuration.
For a branded environment, the MT4 White Label brief should identify who controls symbol configuration and who contracts the feed. Data integration, execution connectivity and platform access remain separate scope items even when coordinated by the same project team.