CRM & spreadsheets
Prepare clean lead files for Apollo or Clay
Check a few rows where work email and company site use different hosts to decide which domain reflects the account.
Start with a small representative sample
A researcher has many directory rows and wants an intermediate file with clean company domains, profile links, and visibly available contacts for a downstream workspace.
Choose a source page you are authorized to use. Make a named list for the job so you can compare new rows with earlier entries from the same source. Include a typical row, a row with a missing or ambiguous value, and a row with formatting that tends to break the next step. A sample can be just a few rows as long as it gives you a way to verify the process before using a whole campaign.
Inspect a row from a directory hosted on the same domain as other providers. Put the real company domain and directory URL into separate staging properties.
Check the source before export
Use a blank staging sheet, a test workspace, or a small destination sample you can inspect before applying a mapping to live data. Review the file as a table and compare it with the source on screen. A separate staging location helps isolate failures when a CRM importer interprets empty values, skips a column, or offers to update an existing contact. Write down the selected identifier before importing so reviewers can tell how duplicates or existing records should be handled.
Subsidiaries can operate under a brand domain distinct from the parent company. Keep evidence for the choice that fits your workflow.
Write down the number of source records you expect to review. If only part of a source table renders at once, make sure your count describes the portion you actually captured. The evidence can be simple: a distinct first row, a last visible row, and a field you can find again later. On a repeated run, these reference points help explain the difference between a bad mapping and a changed source page.
Work through an example
The table shows what a useful before-and-after check looks like for Company Domain. Use it as a model for your own field map. Inspect the visible input first. Look at the output in its intended form, then consider what an operator would do if the source value turned out to be unavailable or different. When the field has more than one legitimate interpretation, include a second example with a different expected result.
| Field | Visible example | Expected result |
|---|---|---|
| Company Domain | https://www.studio.example/about | studio.example |
Check a few rows where work email and company site use different hosts to decide which domain reflects the account.
Select a small batch with both profile links and empty profiles to see how the workspace handles sparse records. Verify identity before downstream enrichment steps.
Try a sample with a clear website domain, one marketplace-hosted profile, and one prospect row with neither website nor verified email. Compare how much useful identity each row will carry to the destination.
Review the cases that can slip through
Mapping a top-level directory page as the company domain makes thousands of unrelated rows look like the same organization.
Start with a narrow import that provides strong identifiers. Meaningful unknowns can remain blank while a researcher verifies them. Review the account linked from the destination record after import, because a correct company name on the sheet does not guarantee the downstream service associated it with the company you intended.
Check the sample after filtering and editing. Search should return both the ordinary case you expect and the exception you selected deliberately. If the exception is hard to find, add a review note or place it in a separate list. Keep an original source reference where it is useful. The goal of this pass is a repeatable decision about those few ambiguous rows before the selection takes on a life of its own.
Prepare the destination
Use Standard Clean CSV when you need the source table fields, and consider a tailored preset when the destination needs a smaller column set. For a clipboard workflow, select the starting cell once before pasting the TSV and review the resulting shape. Download exports preserve a file you can compare to future revisions. Keep track of the input and output row counts and treat default handling of formatting or identity fields as something to verify in your own workspace.
Use the Apollo / Clay Import preset, then review the destination mapping manually and only pass fields appropriate to that workspace.
Label the first output a trial and record the list name, selection, target format, and the field that determines whether the row can be used. Compare at least one expected blank and an ordinary populated row after export. Keep test changes easy to roll back. For larger jobs, measure the number of rows that need manual handling so you know where the remaining review will take time.
Validate what the recipient will use
After the preview, check the actual imported record with a known identifier. A mapping screen can look correct even when a destination adds formatting or applies an existing-record rule. If a value is surprising, compare the originating page, the intermediate file, and the resulting value in order. That comparison usually tells you whether the extraction, cleanup, or destination conversion introduced the difference. Make a separate decision about what changes go into the production account.
Report which fields came from direct capture and which were later added by the destination. This makes the data trail reproducible.
A blank can be the correct choice when the only source value is a directory profile. Place it in a specific review group before constructing account keys. If enrichment later adds a domain, keep the new value distinguishable from the one acquired on the original page.
Review one result where the converted value looked straightforward and one where your team had to choose between plausible interpretations. Give the recipient the updated row count and a practical next action. If review exposed a source inconsistency, note the observable issue and include enough context for the recipient to reproduce it. Close the loop by storing or removing the trial material according to how long your team needs it.
Record the minimum needed for a repeat run
Save a simple checklist with your source path, list name, review filter, format, and destination fields. Keep the choices about Company Domain near the top so the next operator can pick a meaningful test row. A useful recurring process records the fields that affected the outcome and the points where someone needed judgment. It can be rerun when the source layout changes without forcing every old decision into a script.
LeadSheet Clean keeps captured rows and derived values in the browser. Start with Standard Clean CSV or copy TSV when you need a quick review sample. Lifetime Pro adds unlimited export rows, specialized presets, PDF briefs, and multi-list ZIPs. Select the path that produces the format and selection required for your handoff, and verify the license or Free allowance before repeating a large export.