GTG INTEGRATION & MIGRATION EXAMPLE / PUBLIC SAMPLE PLAYGROUND
Map the Move. Prove What Arrived.
Transform a fictional legacy service ledger into a target contract. Change a status mapping, replay the batch, and see why reconciliation must pass before a cutover can be considered.
Explore This Workflow
Select a step, change its settings, then run the example to see what changes. The workflow follows a fixed sequence. No login is needed. Changes reset when you reload or leave this page.
This public playground uses fictional data. Your changes affect this fictional example only.
Showing the result for the current connections and settings.
THE STARTING POINT
GTG Plans a Fictional Service-Ledger Migration
A legacy system uses short client codes and status names. The replacement requires verified client IDs, supported states, and matching values.
- Batch scope
- All three fictional clients
- REVIEW mapping
- Unmapped; hold the source row
- Target fixture
- Empty target, except an explicit conflict situation
- Situation
- One unsupported REVIEW status and one exact repeat
Illustrative GTG workflow with fictional data. Nothing is sent to GTG, a CRM, an email service, or a calendar.
Select a step to explore its role and settings. This walkthrough follows a fixed sequence.
SOURCE TO TARGET / SELECTED CONTEXT
Map Contract
Translate legacy client and status codes only through explicit mappings.
NST → C-104; PIN → C-207; SUM → C-310. OPEN → active; CLOSED → archived. Only the selected policy maps REVIEW.
Configure Map Contract
These settings apply to fictional sample data. Run the configured sample after a change.
2 record(s) staged, 0 already present, 1 exact repeat(s) excluded, 1 source row(s) held. Cutover readiness is withheld.
- Source rows
- 4
- New records staged
- 2
- Existing records reused
- 0
- Rows held
- 1
THE BUSINESS OUTPUT
Migration Reconciliation & Cutover Readiness — Example
- Selected-batch readiness
- Held until mappings and target differences are resolved
- Mapped source total
- $3,900
- Matching-key target total
- $3,900 · $0 difference
- Scope of totals
- Unique records with a valid mapping only. Unmapped rows are listed separately and always prevent readiness.
- Recovery boundary
- Source data and existing target values remain intact. Staging is browser-local; retry uses the stable legacy key. A real cutover also needs access, backups, operational acceptance, and rollback testing.
Fictional local source and target fixtures. Repeated-run mode seeds a prior target for comparison; no data is persisted between page visits.
Source-to-Target Reconciliation
Scroll horizontally to see all columns. Keyboard: focus the table, then use the arrow keys.
| Source row / key | Legacy → target fields | Source amount | Target amount | Decision / reason |
|---|---|---|---|---|
| L-01 / LEG-401 | NST / OPEN → C-104 / active | $1,500 | $1,500 | Staged. Explicit client/status mapping applied; amount preserved in integer cents. |
| L-02 / LEG-402 | PIN / REVIEW → Mapping required | $4,500 | Not staged | Held. Missing client/status mapping or invalid source amount. Define the source-to-target contract first. |
| L-03 / LEG-403 | SUM / CLOSED → C-310 / archived | $2,400 | $2,400 | Staged. Explicit client/status mapping applied; amount preserved in integer cents. |
| L-04 / LEG-401 | NST / OPEN → C-104 / active | $1,500 | $1,500 | Duplicate excluded. Exact source repeat of L-01; counted once by migration key. |
Staged Target Fixture
Scroll horizontally to see all columns. Keyboard: focus the table, then use the arrow keys.
| Migration key | Client ID | Target state | Amount |
|---|---|---|---|
| LEG-401 | C-104 | active | $1,500 |
| LEG-403 | C-310 | archived | $2,400 |
What Needs Clarification
- L-02 · Missing client/status mapping or invalid source amount. Define the source-to-target contract first.
Bring your own business problem, systems, and constraints into a GTG discovery conversation.
Build Your Discovery Brief