Data Enrichment and Data Archiving Strategy

Overview
Data Enrichment and Data Archiving Strategy sits inside the Advanced Data and Analytics Management domain of the Salesforce Advanced Administrator exam. It tests whether you can keep an org's data complete, accurate and trustworthy (enrichment) while also keeping it lean, performant and compliant (archiving). These two disciplines are two sides of the same coin: a mature administrator continuously improves the data that matters and systematically removes or relocates the data that no longer belongs in primary storage.

Why It Is Important
1. User adoption and trust – If reps open an Account and see blank Industry, outdated phone numbers or three duplicate records, they stop trusting Salesforce and keep spreadsheets instead. Enrichment and deduplication directly drive adoption.
2. Reporting and analytics accuracy – Dashboards, forecasts and Einstein features are only as good as the underlying data. Missing or inconsistent values corrupt grouping, filtering and AI predictions.
3. Storage limits and cost – Every org has finite data storage (base allocation plus a per-user amount) and file storage. Exceeding limits blocks record creation, breaks integrations and forces expensive storage purchases. Archiving keeps you under limits.
4. Performance – Large data volumes (LDV) slow list views, reports, SOQL queries, sharing recalculations and data loads. Archiving aged records is a primary LDV mitigation technique.
5. Compliance and governance – Regulations such as GDPR, CCPA, HIPAA and industry retention rules dictate how long data must be kept and when it must be deleted. A documented retention and archiving policy is a compliance requirement, not a nice-to-have.
6. Exam weight – Scenario questions frequently present a business problem (storage warning, poor data quality, audit requirement) and ask for the most appropriate solution. Knowing the tool-to-problem mapping is essential.

Part 1 – What Is Data Enrichment?
Data enrichment is the process of improving existing records by adding missing information, correcting inaccurate values, standardizing formats and removing duplicates. It can be sourced internally (business rules, user input, automation) or externally (third-party data providers).

Key Enrichment Mechanisms on the Platform
• Lightning Data and Data Integration Rules – Lightning Data packages from the AppExchange (for example Dun and Bradstreet, ZoomInfo, Clearbit and similar providers) install Data Integration Rules found in Setup. These rules match your Accounts, Leads and Contacts to the provider's dataset and automatically update or fill fields such as Industry, Annual Revenue, Employee Count and D-U-N-S Number. Admins activate the rule, choose field mappings, decide whether to overwrite existing values and control whether updates happen on record creation and on a schedule. Note that the legacy Data.com Clean and Data.com Prospector products were retired; exam questions now expect you to think of Lightning Data, Data Integration Rules, Data Cloud or AppExchange partners.
• Geocoding Data Integration Rules – Standard built-in rules add latitude and longitude to Account, Contact and Lead addresses so you can use location-based features and reports.
• Duplicate Management – Matching Rules define how records are compared (exact or fuzzy matching on fields such as Name, Email, Phone, Address). Duplicate Rules define what happens when a match is found: Allow or Block, Alert the user, Report the duplicate, and whether to bypass sharing rules when comparing. Duplicate Jobs (Performance and Unlimited Editions) scan existing records and produce Duplicate Record Sets that can be merged. Remember: Matching Rule equals how to find; Duplicate Rule equals what to do.
• Merging – Accounts, Contacts, Leads and Cases can be merged natively (up to three at a time). Merging consolidates related records and preserves the master record you select.
• Validation Rules, Required Fields and Picklists – Preventive enrichment. Restricted picklists, dependent picklists, field-level requirements and validation formulas stop bad data at entry time, which is cheaper than cleaning later.
• Automation – Record-triggered Flows can normalize values (uppercasing state codes, formatting phone numbers), populate defaults, look up related data and flag incomplete records for review. Scheduled Flows can run periodic quality checks.
• Bulk Cleanup Tools – Data Loader, Data Import Wizard and Mass Update capabilities let you export, correct in bulk and reload, or use external IDs for upsert operations. Mass Transfer and Mass Delete also support cleanup projects.
• Einstein and Data Cloud – Einstein Activity Capture and Data Cloud identity resolution unify profiles across sources; these appear occasionally as the modern answer for large-scale enrichment and unification.

Measuring Data Quality
Admins build data quality dashboards using formula fields that score record completeness (for example, add 20 points for each key field populated), then report on records below a threshold and assign cleanup to owners. The exam may describe this as a Data Quality Analysis Dashboard approach.

Part 2 – What Is Data Archiving?
Data archiving is the planned movement of inactive, aged or low-value records out of primary Salesforce storage into a secondary location where they remain retrievable if needed, or the controlled deletion of data that has exceeded its retention period. It is driven by a retention policy: a documented statement of which objects, which criteria (for example Closed Cases older than 3 years, Tasks older than 2 years, Opportunities Closed Lost older than 5 years), how long to keep, where to store and who approves.

Key Archiving Mechanisms
• Storage Awareness – Setup > Storage Usage shows data and file storage by object and by user. Most records consume about 2 KB regardless of fields; exceptions include Campaigns (about 8 KB), Campaign Members (about 1 KB), Person Accounts (about 4 KB), Knowledge Articles (about 4 KB) and Email Messages (actual size). Field history does not count toward data storage. Files, attachments, documents and content versions count toward file storage.
• Recycle Bin – Deleted records stay 15 days and still consume storage until purged. The Recycle Bin can be emptied manually. Data Loader offers a Hard Delete option that bypasses the Recycle Bin, which requires the Bulk API Hard Delete permission.
• Mass Delete Records – Setup tool to delete Accounts, Leads, Activities, Contacts, Cases, Solutions, Products and Reports using criteria, with a limit of 250 records per operation. For larger volumes use Data Loader or Bulk API.
• Automatic Activity Archiving – Salesforce automatically archives Events with an end date more than 365 days old and closed Tasks with a due date more than 365 days old (or created more than 365 days ago if no due date). Archived activities are not visible in standard reports, list views or most dashboards, but can be viewed on the record and retrieved with SOQL using queryAll or isArchived filters. This is a classic exam topic.
• Field History Tracking vs Field Audit Trail – Standard field history tracks up to 20 fields per object and Salesforce retains it for 18 months via the UI (24 months via API). Field Audit Trail (a paid add-on, part of Salesforce Shield) extends tracking to up to 60 fields per object and lets you define a retention policy of up to 10 years, storing the history in the FieldHistoryArchive big object. If a question mentions retaining field history for many years for audit purposes, the answer is Field Audit Trail.
• Big Objects – Custom big objects store billions of records inside Salesforce without consuming standard data storage. Data is written via API, Apex or Data Loader (CSV), queried with SOQL that must respect the defined index, and cannot use triggers, Flows, standard reports or the Recycle Bin. Ideal for an internal archive of historical transactions that must stay on-platform and be queryable.
• Data Export Service – Setup > Data Export provides scheduled weekly (Enterprise and above) or monthly exports of all data as CSV zip files, optionally including files and documents. It is a backup mechanism and a simple archive-before-delete step.
• Salesforce Connect and External Objects – Archived data living in an external database or data lake can be surfaced in Salesforce as external objects via OData, so users still see related archived history on a record without the data consuming Salesforce storage. External objects support list views, lookups via indirect and external lookups, and limited reporting.
• AppExchange Archiving and Backup Solutions – Partner tools (for example OwnBackup, Odaseva, Grax) automate policy-based archiving, retain full relationships and metadata, provide restore capabilities and surface archived records in-app. When a scenario demands automated, relationship-preserving, restorable archiving with minimal custom development, these are the expected answer.
• Custom Automation – Scheduled Flows or scheduled Apex can identify records that meet retention criteria, copy them to a big object or external system through an integration, then delete the originals. Always export before deleting.
• Email Messages, Chatter and Attachments – Case Email Messages and Files are frequent storage hogs. Strategies include moving attachments to external content repositories (Files Connect), limiting Chatter file retention and archiving closed Case emails.

How a Data Archiving Strategy Works – Step by Step
1. Audit – Review Storage Usage to find the largest objects and owners; profile record age and activity.
2. Define policy with stakeholders – Business, legal and compliance owners agree on retention periods, criteria for inactive, and legal hold exceptions.
3. Assess relationships and dependencies – Check parent-child relationships, roll-up summaries, reports and integrations that reference the data to be archived. Deleting a parent may cascade delete children.
4. Choose the mechanism – Keep on-platform and queryable (big object), surface externally (Salesforce Connect), third-party tool, or simple export and delete.
5. Back up first – Run a Data Export or partner backup before any deletion.
6. Test in a sandbox – Validate counts, relationships, report impacts and user experience.
7. Execute in batches – Use Bulk API, consider disabling automation, sharing rule recalculation deferral and running during off-peak hours for LDV.
8. Validate and document – Confirm storage reduction, verify archived data is retrievable, update the data dictionary and communicate to users.
9. Automate and schedule – Make archiving a recurring process rather than a one-time project.

How a Data Enrichment Strategy Works – Step by Step
1. Identify critical fields per object and define data standards (formats, picklist values, required fields).
2. Measure baseline quality with completeness formulas and exception reports.
3. Prevent new bad data with validation rules, duplicate rules, restricted picklists and page layout requirements.
4. Enrich existing data with Data Integration Rules, Lightning Data or a bulk export, cleanse and upsert using external IDs.
5. Deduplicate with Duplicate Jobs and merge, or Data Loader based matching for objects not covered natively.
6. Assign ownership and monitor via dashboards; schedule periodic re-enrichment because external data decays quickly.

Exam Tips: Answering Questions on Data Enrichment and Data Archiving Strategy
Tip 1 – Decode the keyword. Storage warning, slow performance, large data volume, old records equals archiving. Missing fields, inaccurate data, duplicates, third-party data, standardization equals enrichment. Audit, compliance, retention years equals Field Audit Trail or a documented retention policy.
Tip 2 – Know the Field History numbers. Standard tracking: 20 fields per object, 18 months in the UI, 24 months via API. Field Audit Trail: 60 fields per object, up to 10 years, stored in a big object, requires Shield or add-on license.
Tip 3 – Activity archiving is automatic. Events and closed Tasks older than 365 days are archived by Salesforce, do not appear in standard reports or list views, and are retrievable via SOQL queryAll. If a user asks why old activities vanished from a report, this is the answer.
Tip 4 – Big Object versus External Object. Billions of records, must stay in Salesforce, read via SOQL and no reports or triggers needed equals Big Object. Data lives in an external system, must appear in related lists and list views without consuming storage equals External Object via Salesforce Connect.
Tip 5 – Matching Rule vs Duplicate Rule. Matching Rule identifies duplicates (criteria, fuzzy or exact). Duplicate Rule sets the action (Allow, Block, Alert, Report). Duplicate Jobs find existing duplicates in bulk. If the question says users are not being warned, check that the Duplicate Rule is active and set to Alert.
Tip 6 – Data Integration Rules are the enrichment answer. When a question asks how to automatically keep Account Industry, Revenue or Employee Count updated from an external provider, choose Lightning Data and Data Integration Rules, not Validation Rules or Flow.
Tip 7 – Always back up before you delete. If an option deletes records without an export or backup, it is almost never the best answer. Data Export Service or a partner backup is the expected precaution.
Tip 8 – Hard Delete and Recycle Bin. Deleted records sit in the Recycle Bin for 15 days and still count toward storage. To free storage immediately, empty the Recycle Bin or use Data Loader Hard Delete with the Bulk API Hard Delete permission.
Tip 9 – Mass Delete limits. The Setup Mass Delete tool handles 250 records at a time and only specific objects. For thousands or millions of records, the answer is Data Loader or Bulk API, ideally in batches.
Tip 10 – Storage math. Most records are about 2 KB; Campaigns 8 KB; Campaign Members 1 KB; Person Accounts 4 KB; field history does not consume data storage; files and attachments go to file storage. Use this to eliminate wrong answers about which object is driving storage consumption.
Tip 11 – Prevention beats cleanup. When asked for the most efficient long-term approach to data quality, favor validation rules, duplicate rules and restricted picklists at point of entry over periodic manual cleanup.
Tip 12 – Minimal custom code, maximum declarative. The exam rewards declarative and out-of-the-box answers first (Data Export, Data Integration Rules, Duplicate Management, Field Audit Trail, partner apps), then Flow, and only then Apex or custom integrations.
Tip 13 – Watch for relationship impacts. Archiving or deleting parent records (Accounts, Cases) can cascade to children and break roll-ups and reports. The correct answer usually includes analyzing dependencies and testing in a sandbox.
Tip 14 – Governance language. Answers that mention defining a retention policy, assigning data owners, documenting standards and gaining stakeholder agreement reflect the strategic mindset the Advanced Administrator exam expects.
Tip 15 – Eliminate retired products. Data.com Clean and Prospector are retired; if they appear among options alongside Lightning Data or Data Integration Rules, choose the current product.

Quick Reference Summary
• Enrichment tools: Lightning Data, Data Integration Rules, Geocoding rules, Matching and Duplicate Rules, Duplicate Jobs, Merge, Validation Rules, Flow, Data Loader upsert with External IDs.
• Archiving tools: Storage Usage, Recycle Bin and Hard Delete, Mass Delete, automatic Activity archiving, Field Audit Trail, Big Objects, Data Export Service, Salesforce Connect External Objects, AppExchange archiving solutions, Scheduled Flow or Apex.
• Strategy: Audit, define policy, assess dependencies, choose mechanism, back up, test, execute in batches, validate, document, automate.

Master the problem-to-tool mapping above, memorize the key numbers (15 days, 250 records, 365 days, 20 and 60 fields, 18 and 24 months, 10 years, 2 KB) and always favor the declarative, backed-up, policy-driven option, and you will handle any Data Enrichment and Data Archiving Strategy question with confidence.