Review an Enriched CSV Before Replacing Your Original Data
TL;DR: Treat an enriched CSV as proposed changes, not a replacement for your original data. RevOps and sales teams should preserve the input, match rows with stable evidence, approve specific field changes and inspect the destination after import. Keep ambiguous matches and rejected replacements separate from the file released for operational use.
What should you preserve before comparing the files?
Keep an untouched input file and a separate copy of the enrichment return. Record which input produced the return and retain the settings or request context needed to understand it. Do not edit the only copy of the original while reviewing proposed changes.
Choose a stable input identifier before matching rows. The identifier should distinguish the original records in the working file, and its relationship to any returned identifier should remain available. Row position and a familiar name are not substitutes for a verified match.
Use the bulk CSV preparation workflow for input cleanup, mapping and deduplication. This review begins with the returned data and asks which actual changes should be accepted. Completing the preparation work does not establish that every enrichment result belongs on the original record.
| Workflow | Current limit or requirement | Implication for review |
|---|---|---|
| UI CSV upload | Header row and file size up to 20 MB | Confirm the approved file fits the actual upload route |
| Chat table CSV export | Up to 50,000 rows per export | Use smaller filtered groups for a larger result and reconcile their coverage |
Which identifier reliably pairs original and returned rows?
Use the retained input key when the enrichment result preserves it, then confirm that the returned information refers to the same person or company. If the key is missing, establish a reviewed crosswalk before accepting changes. Do not infer identity solely from the output order.
Check for missing, duplicated or changed keys. A result with several candidate matches needs a review decision rather than an arbitrary first-match selection. A returned row without a reliable connection to the input should remain outside the approved update file.
Treat changes to matching fields carefully. If enrichment proposes a new email or company domain, preserve the original match evidence while deciding whether the new value belongs to the same record. Do not use the changed field as its own proof of continuity.
Distinguish a person from the company attached to that person. Unify’s standard attributes represent a person’s company as a reference, alongside separate contact fields and restrictions. A company-field update and a person-field update therefore need their own meaning and destination checked.
How should you classify the field differences?
Classify each proposed change before deciding whether to accept it. An unchanged value, a blank-fill, a replacement and an unresolved match require different decisions. Treat a returned blank separately from a deliberate request to clear an existing value.
| Change type | Review question | Default handling until reviewed |
|---|---|---|
| Blank-fill | Does this supported value belong to the matched record? | Keep proposed value separate |
| Replacement | Why should this value supersede the original? | Preserve original and compare evidence |
| Returned blank | Does it mean no result, missing data or an approved clearing action? | Do not infer deletion |
| Ambiguous match | Does this result refer to the intended person or company? | Hold the row |
| Unchanged value | Is the retained value still appropriate for the destination? | Preserve it without claiming new verification |
Compare the actual values as well as any normalized representation used for review. Normalization can help identify formatting differences, but it should not hide a change that matters to the destination. Preserve the original spelling and representation so the reviewer can understand what would be replaced.
Check field types before interpreting a difference. In Unify, Text attributes can hold identifiers containing letters or leading zeros. Choose the appropriate type for the field rather than treating every numeric-looking identifier as a quantity.
Which fields deserve protection from routine replacement?
Protect fields whose meaning comes from your own commercial process or an explicit contact restriction. Enrichment can propose descriptive information, but it should not silently redefine ownership, lifecycle decisions or the record of whether outreach is allowed.
Identify protected fields before building the approved output. Preserve their existing values unless the authorized process explicitly approves a change. If the enrichment return includes similarly named columns, inspect the meaning instead of assuming that the names refer to the same business decision.
Separate observed source information from reviewed status. A provider’s confidence label, a current employment claim and your team’s approval are different things. Keeping them in distinct fields avoids turning a returned label into an internal acceptance decision.
If the team stores review information in Unify, custom attributes can extend standard objects. Define the purpose and value type of those fields before use. This is a way to represent your chosen review information, not a claim that a native field-diff approval workflow has been created for you.
What belongs in the approval sheet?
Use a field-level approval sheet that preserves the original value, proposed value and match evidence. Populate it with actual returned data only. Keep the field name with each row in your working file so the decision cannot be mistaken for approval of every value on the contact.
| Row ID | Original value | Proposed value | Match evidence | Approval | Export status |
|---|---|---|---|---|---|
Record who accepted or rejected the change and why. Approval of one field does not approve unrelated replacements on the same row. A reviewer may accept a supported blank-fill while retaining the original value in another field or holding the record’s identity for further review.
Build the operational output from the approved decisions, then reconcile it with the sheet. Rejected replacements should leave the intended original value intact, and held matches should not slip into the release because another field on the row was accepted. Keep the unmodified enrichment return for later investigation.
- Sales: Confirm whether the changed information affects the intended contact or outreach context
- RevOps: Resolve record matching, field meaning and destination behavior
- Data reviewer: Preserve source evidence and record the field-specific decision
- Import owner: Release the approved file and verify the actual destination result
How can Unify help inspect the returned information?
Use Unify company and contact enrichment to research relevant account and person information, while retaining the distinction between proposed data and accepted changes. A completed enrichment step should lead to review, not automatic replacement of the original file.
With list building in chat, start from a CSV or existing list, refine the table and add missing information. When an enriched cell provides supporting evidence, inspect its reasoning and references. Use that evidence to assess the proposed value without assuming every cell has the same level of support.
A chat table’s CSV export follows its current filters, search and sorting. A single export includes up to 50,000 rows, so a larger result needs smaller groups. Record which portion each file contains and check for omissions or overlap before treating the exports as a complete approved set.
Keep acceptance decisions explicit outside the mere act of downloading. An exported table contains the selected result, but a download does not establish that someone reviewed each changed field. Confirm that the released file matches the approvals and that no held rows were unintentionally included.
What changes when you import through the UI or API?
Inspect the exact import route before releasing the approved file. The UI CSV uploader and an API request can use different update behavior, so a protective setting in one route should not be assumed to apply to the other.
In the UI CSV import, Unify matches companies by domain and people by email. Mapped values can update an existing matching record. Review the person and company mappings, preview and warnings before starting the upload; the file requires a header row and must be within the 20 MB limit.
People need a valid email supplied in the file or found through enrichment, and a match is not guaranteed. Required custom fields can also affect acceptance. If a proposed email or domain changes, confirm which destination record will match before allowing the update to proceed.
The separate API CSV company-import workflow uses domain matching and the create_or_update_if_empty property. That property avoids replacing populated values for the request shown. It is a specific API update choice, not a universal guarantee that UI uploads preserve every existing field.
Review downstream HubSpot field mappings separately when imported data will reach a CRM. Read and write behavior are independent, and available write choices can preserve or replace values under different conditions. CSV column mapping does not establish the subsequent CRM write behavior.
How do you confirm the approved result actually landed?
Inspect the destination records and reconcile skipped or unmatched rows before releasing the list for use. In Unify, open the destination list and its Activity entry for the CSV upload to review the operation. Compare the resulting fields with the approved file rather than relying only on a completed status.
Preserve the approved output, approval sheet and operation result together. If a value differs, determine whether matching, mapping, validation or later sync behavior explains it. Do not run an unreviewed reverse upload and describe it as a guaranteed rollback.
Use the partial-enrichment decision guide for the next question: which records can proceed to outreach, which remain held and which require another attempt. Accepted data and outreach eligibility are separate decisions.
Which mistakes should the reviewer avoid?
- Matching returned rows by position after sorting or filtering
- Treating a blank-fill as safe before confirming identity
- Allowing a returned blank to erase a protected value without approval
- Confusing an API fill-only option with every import route
- Calling an exported or completed file a verified destination update
To research and review account data before preparing operational lists, sign up for Unify. Keep the original, proposed change and accepted result distinguishable throughout the workflow.
Frequently asked questions
Should an enriched CSV replace the original file?
Keep an untouched original and review the return as proposed changes. Match rows using a stable input identifier, inspect the field-level differences and build a separate approved output. Do not replace original values simply because the enrichment operation completed.
What if the enrichment provider changes the email used as the row key?
Use a preserved input identifier or another verified crosswalk to establish which original row the result belongs to. A changed email cannot simultaneously be assumed to identify the original person without review. Hold ambiguous matches before accepting any field changes.
Is filling a blank field always safe?
No. A blank-fill still needs a supported match to the intended person or company and a value appropriate for that field. Review its source and meaning, especially when the value affects identity, eligibility or ownership.
Does Unify CSV import preserve all existing values automatically?
No universal fill-only rule should be assumed. In the UI upload workflow, mapped values can update an existing matched record. The separate API company-import tutorial uses create_or_update_if_empty to avoid replacing populated values in that specific request.
Can I use Unify chat to review an enriched table?
Chat can refine tables, enrich missing information and expose reasoning and references when an enriched cell has supporting evidence. Review the actual result before saving or exporting it. Keep your field-level acceptance decisions separately rather than assuming a native diff-and-rollback workflow.
What proves that the approved changes reached the destination?
Inspect the actual destination records and compare the relevant fields with the approved output, while reconciling skipped or unmatched rows. Keep the accepted file, decisions and operation result together. An export or upload completion message alone does not prove every intended value was applied.
Glossary
- Input key: A retained identifier used to connect returned data to its original row
- Field diff: A comparison of the original and proposed value for a specific field
- Blank-fill: A proposed value for a field that was previously empty
- Approved output: A separate file built from accepted changes and retained original values
- Reconciliation: Checking that intended records and values reached the destination while accounting for exceptions
Sources
- Import data from a CSV
- Import data
- Build lists with chat
- Standard objects and attributes
- Objects and attributes
- Attribute value types
- Field mappings
- Your next 100 leads are a prompt away
- Bulk CSV Enrichment Workflow: Validate Before You Import
- Partial Enrichment Before Sequencing: Decide What to Send, Hold, or Retry

