Dove l'architettura dei dati incontra la realtà

Disponibile anche in 19 lingue

English · Español · 日本語 · Português (Brasil) · Français · Deutsch · 한국어 · 简体中文 · Português (Portugal) · 繁體中文 · Bahasa Indonesia · Türkçe · Polski · Tiếng Việt · ไทย · Українська · Español (México) · Français (Canada) · Deutsch (Schweiz)

Capitolo 10 di Data Architect, Parte 2: Architettare su larga scala. Precedente: Integrazione e movimento dei dati.

La migrazione è il punto in cui l’architettura dei dati incontra la realtà. Ogni decisione di modellazione, qualità, dati master e volume che abbiamo preso viene messa alla prova il giorno in cui arrivano milioni di record tutti insieme. E una migrazione “caricata con successo” può comunque essere un fallimento: titolari sbagliati, relazioni rotte, clienti duplicati, un milione di email di benvenuto, record bloccati, o un fine settimana di cutover che finisce il tempo.

On a new distribution center's first morning, a forklift carries the first pallet in from a truck at the dock, while the next truck backs in.

Image generated with AI. ⟲

Every CTA scenario has a legacy system to bring across, and the candidate has to say how the data comes in, how it’s cleaned and how it’s de-duplicated. This chapter is that answer, from the source extract to the moment the old system stops mattering, and then the copies that keep going. ⟲

One example runs through all five modules: Steve Trucking retiring RouteDesk, its old dispatch tool, with eight years and about 5 million deliveries. What comes into Salesforce, how it’s prepared, how it loads, what the automation does about it, and the weekend it all happens. Then the other direction: Salesforce, now the system of record, keeping Snowflake’s copy in step. ⟲

Le idee di questo capitolo

Migration is a quality project first, and a migration is an integration with an end. ⟲
Migrate, archive or discard, and know why every class of data moves, or doesn’t. ⟲
Prepare outside, then load the result: a preparation data store, the raw source kept, no step that loses fidelity, and three sets of keys (the source’s, the transformations, Salesforce’s). ⟲
The model sets the load order, and every child finds its parent by a key, never by a name. ⟲
The Bulk API is the loading dock behind the bank, and the dock still needs a plan: insert before upsert, sort by parent, the load user, and the IDs brought back. ⟲
Any time you turn automation off, you own that business logic not happening. The bypass is part of the original design, tested on and off and deployed long before it’s needed. ⟲
Production cutover should be boring: rehearsed, run from a runbook, loaded early and hidden by sharing, with go/no-go and a rollback clock decided in advance. ⟲
Dimostralo in quattro modi: conteggi, totali, controlli a campione e report aggregati.
Getting data out isn’t leaving Salesforce. Migration has a defined start and end; synchronization is ongoing, and the mirror is never the master. ⟲

Il percorso di questo capitolo

Cinque moduli, ognuno si regge da solo.

Migration Is a Quality Project First. RouteDesk on the landscape; migrate, archive or discard; the preparation data store; Steve’s five steps; loading by keys; merged records and their children; three sets of keys. ⟲
Loading at Volume. The teller window and the loading dock; Bulk API 2.0 and 1.0; insert, update or upsert; sorting by parent; the load user; bringing the keys back; rehearsing the whole run. ⟲
Automation During the Load. The arrows a load sets off; don’t need it, simulate it, defer it; what a bypass looks like in Apex, flows and validation rules; sharing; the automation inventory. ⟲
Cutover Weekend. The runbook; Day −7, Day −1, Day 0 and the rollback point; locking users out; the four proofs; authority moves on Day 0. ⟲
Getting Data Out: Keeping Another System in Step. Salesforce stays the system of record; Snowflake needs a mirror. The ways out, PK chunking, keeping it current, a copy once or a copy forever. ⟲

Cosa decide qui un architetto

Cosa si sposta davvero: migrare, archiviare o scartare, e perché.
Come i dati vengono resi adatti prima che arrivino, e come ogni record resta tracciabile fino alla sua sorgente.
Il piano di caricamento: sequenza, chiavi, concorrenza, identità e titolarità.
Cosa può scatenare il caricamento, e come torna il funzionamento normale.
Come si esegue e si dimostra il cutover, e quando il rollback smette di essere un’opzione.
Where migration ends, what keeps another system’s copy in step afterward, and who owns each value. ⟲

Oltre l’esame: l’IA accelera la metà “analisi” di una migrazione: profilazione, mappatura, rilevamento delle anomalie, scrittura degli script. Usala passo dopo passo, tracciando ogni comando generato. Validazione, riconciliazione e go/no-go restano deterministici e affidati a persone. Ogni modulo si chiude con cosa cambia l’IA.

Per approfondire

Salesforce, General Guidelines for Data Loads (si apre in una nuova scheda) and Bulk API and Bulk API 2.0 Limits and Allocations (si apre in una nuova scheda), checked 2026-11-01. ⟲
Salesforce, Best Practices for Deployments with Large Data Volumes (si apre in una nuova scheda), Winter ‘27, checked 2026-11-01. ⟲
Il corso Integration Architect: Bulk (coming soon).

Next: Transactions, Concurrency, and Reliability ⟲