All guides

CRM & spreadsheets

Standardize company domains before account matching

Confirm that the domain is an actual company site and use the original website and source to verify uncertain matches.

Start with a small representative sample

A catalog from several directories has homepages with protocol variations and tracking tags. An account matching rule consumes a domain column.

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.

Separate website URL, hostname, and organizational identity as distinct values in your review notes. A path can be meaningful even when the hostname is shared.

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.

If the only evidence is a personal or generic email host, leave the organizational domain for manual review instead of making it an account identifier.

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 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.

FieldVisible exampleExpected result
Domainhttps://www.harbor.example/pricing?utm_medium=referralharbor.example

Confirm that the domain is an actual company site and use the original website and source to verify uncertain matches.

Check one subsidiary, one hosting-provider subdomain, and a company with region-specific sites against the exact account records involved.

Compare studio.example, consulting.studio.example, and a distinct partner’s profile on a directory host. Review which ones map to an account that your team can identify. A shared hostname can still require different treatment depending on what it represents.

Review the cases that can slip through

Assuming that every subdomain belongs to the same account can collapse hosted storefronts and distinct franchises.

Compare a local branch, an independently operated franchise, and a SaaS company whose business home differs from its support portal. They illustrate why the data type and its meaning matter separately. A hostname can be perfectly normalized while still being the wrong source for account matching.

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.

Document where the domain came from and choose a canonical account rule that fits existing CRM data.

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.

Decide whether to use the public site or the email domain for account matching. Keep the other domain available for source verification.

Look for rows where the email domain belongs to a parent business while the website uses a branded domain. Record the evidence before choosing an account key, since the clean domain field alone cannot distinguish a recent acquisition from an unrelated company.

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 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.