Key points
- Freeze source evidence and document field meaning before transforming data
- Reconcile identities, merges, held records and preserved relationships
- Test destination behavior and repair the stage that actually failed
Validate an Apollo data migration by proving what changed between the source snapshot and the intended destination. A completed upload, a populated field or a flattering completeness score does not establish correct identity, preserved relationships or readiness for outreach.
Use a controlled staging store or documented destination interface. Dievio can supply supported search or known-profile results for a separate task; it should not be assumed to provide a generic historical-database import schema.
Freeze the evidence before transforming it
Retain the permitted original export, selected scope, field list, extraction date and record count. Keep a separate working copy for mapping and transformation.
Record destination identity, mapping version, test cases and acceptance requirements. Preserve source record identifiers and the meaning of provider-specific statuses and dates.
The migration checklist establishes this boundary. Apollo's CSV guide helps confirm actual exported fields and spreadsheet-formatting risks.
Check field meaning and representation
| Check | Question | Evidence to retain |
|---|---|---|
| Presence | Did the expected value arrive, or was it already absent at source? | Source and destination values |
| Type and length | Was the value truncated or coerced into another type? | Original representation and destination result |
| Meaning | Does the target field express the same concept and unit? | Mapping definition and any approved transformation |
| Dates | Which event and time zone does the value describe? | Source definition and transformed value |
| Identity | Did the update attach to the intended person and account? | Matching rule and conflict decision |
| Ownership | Was an authorized update applied without erasing confirmed data? | Write policy and before/after state |
A company-size range is not an exact employee count. Revenue is not automatically ARR, and provider funding context is not a native Dievio funding-stage field. Keep unmatched technology or other source-specific values separately rather than inventing a destination taxonomy.
Keep original phone prefixes, extensions and identifiers through the import path. Test accented names, non-Latin text, empty cells, nulls and enumerated values in the actual destination instead of assuming every modern system treats them identically.
Report completeness without hiding critical gaps
Use field-level availability and, where useful, the proportion of records containing all required fields. These answer different questions.
For example, a hypothetical set of one thousand records with five required fields has five thousand possible field values. Four thousand five hundred populated values means ninety-percent field-value completeness; it does not show how many records contain all five required values.
State which fields are required for the specific task. A high average does not make a record usable when its essential identity field is missing, and a null optional phone is not evidence that the migration failed.
Reconcile records, merges and exceptions
- Count distinct source input records under the declared unit.
- Record intended transformations and exclusions.
- Identify created or updated destination records.
- Review merged identities and the retained field provenance.
- Separate rejected records from held cases.
- Explain every difference using nonoverlapping reconciliation states.
- Check that operational relationships and suppression decisions remain intact.
Similar names are matching candidates, not proof of the same person. Shared addresses, reused emails, renamed companies and parent groups can complicate an exact match too. Do not automatically keep the most recently imported row as the truth.
Separate structural email checks from delivery evidence
Syntax, domain resolution and mailbox-checking results answer different questions. They do not independently confirm the intended identity, consent or inbox placement.
A missing MX record is not a complete invalidity test: RFC 5321 describes an implicit-MX case when no MX records are present. Use an appropriate documented checking method instead of a simplistic presence rule.
Retain inconclusive and provider-described catch-all results under their actual meanings. A checking result is not a post-send bounce rate, and a seed message cannot establish how every named recipient will receive a later campaign.
Investigate a changed source value separately from an address that transferred correctly but is no longer suitable. Do not promise a universal ninety-five-percent valid rate or prescribe a new paid enrichment call whenever a check fails.
Test destination behavior before activation
- Required fields and types map correctly.
- Existing confirmed values are not erased by missing input.
- Contacts attach to the intended company and owner.
- Duplicate and conflicting identities route as designed.
- Suppression and active-opportunity decisions persist.
- A repeated run does not create unintended duplicates or activation.
- Partial failure preserves completed work and exposes unresolved cases.
- Personalization fields with missing values do not produce broken messages.
Use a bounded test that covers these conditions. Do not send unsolicited test campaigns to hundreds of people as a migration diagnostic. Disable unintended enrollment while inspecting destination behavior.
Use Dievio only for a supported supplemental operation
Filtered search can discover candidate contacts; known-profile lookup can match a LinkedIn person URL to available records. These operations do not provide generic email-input enrichment, native independent verification or automatic repair of your destination.
A free preview counts matching contact records, not imported data or verified quality. Search retrieval uses one credit per returned lead; empty results use none and repeated retrieval can charge again. Saved-list downloads are free and do not refresh records. API credits are separate from workspace search credits.
Your application owns mapping supplemental results to retained identities and approving changes. Keep source evidence and dates alongside any new values.
Choose remediation from the failed stage
Repair a mapping error, repeat a permitted missing extraction partition or investigate a specific identity conflict. Research a source-data gap only when that is the actual problem.
Do not infer a complete re-migration or replacement from invented sixty/eighty-five-percent bands. Compare the evidence, rights, recoverability, operating effort and unresolved risk.
Produce a validation record with the input and mapping versions, checks performed, counts, limitations, owner and release decision. The coverage guide develops the separate assessment of source suitability after transfer correctness is established.



