LEARN. PRACTICE. GROW.Concept and mechanism
A successful load requires correct identity and meaning, not merely a final count. Mapping connects columns to fields; matching criteria identify potential duplicates; duplicate rules define the response. Analytical presentation also depends on the model: report type exposes objects and fields, and dashboard context determines which data is displayed.
Guided application
Preserve the original source, document transformations, and validate a sample containing relevant formats and exceptions. Reconcile rejections and values, including dates, amounts, and keys. For reports, confirm available fields and folder sharing. Distinguish a fixed running user from a dynamic dashboard. For exports, download, retain, and check files against the recovery plan; scheduling does not establish recoverability. For every load, prepare acceptance criteria before execution: preserved keys, required fields populated, reconciled values, and explained rejections. A technically accepted row can still contain an incorrect value. For every metric, also identify execution context and the included population. When two users see different totals, compare filters, permissions, and refresh timing before concluding that the database is inconsistent or broadening privileges. Retain enough evidence to reproduce the comparison later.
A customer sample reveals swapped dates and an unmapped external key. The team is within the tool volume limit but has not established quality. It corrects formats and mapping, repeats the sample, and compares values with the source. The loading go/no-go depends on that evidence, with impact communicated if the window must change.
Common pitfalls
Do not confuse similarity with confirmed identity. A dashboard running as a broadly authorized user may show totals different from the viewer’s reports. A private folder does not change that execution context. An export email does not guarantee unlimited retention.
Related topics: Effective access and user lifecycle · Data model and Lightning experience · Leads, campaigns, and commercial follow-up
Quality comes from reconciliation, known context, and recovery evidence, beyond technical job completion.
Reference: Import Data · Platform Administrator guide Summer 25