Account Merge NGH Data Cutover

1 · Choose the job

Each job runs a fixed Account-merge data step over Bulk API — archiving or seeding Dupe_Key__c rows, appending a value to Account.Unmergeable_Reason__c (never overwriting), or setting Account.VAT_Customer_Type__c from the Business Unit Company (apex-only). The predicate, object, operation and written fields are locked in code; you cannot edit them here. Recommended order: Archive → Seed → OSP → Primary BU → Carving Exception. VAT Customer Type is independent and can run on its own.

2 · Run settings

Org type Auth mode How the tool connects to the org. jwt uses the configured key (headless); username-password uses the credentials below (per run). Bulk chunk size (records per Bulk API 2.0 ingest job) Concurrency (chunks in flight; ≤ 25) Write mode How the DML is issued. Bulk API fires all Account automation on every record (quiesce it first — see RUNBOOK §2). Anonymous Apex (Account jobs only) bypasses the Account Apex triggers per transaction — no org-wide change. The block embeds only the Account Ids and computes the field update in Apex; chunks hold up to 800 rows (200 default, cap 800) — the calibrated safe per-transaction CPU size (the residual record-triggered Flows dominate CPU, not the Apex). Dry run (count + sample the first window; no DML)

Reminder: a live run fires Account automation on every update. Quiesce the dedupe after-update handler + merge scheduler first — see the RUNBOOK. Each run ends with the job's read-only COUNT() checks against the org (the source of truth), reported in the log below.

Account Merge NGH Data Cutover

1 · Choose the job

2 · Run settings

3 · Progress

Production org targeted