All guides

CRM & spreadsheets

Keep exported lead data from becoming spreadsheet formulas

Check that the sample appears as text and does not calculate. Also check a plus-prefixed phone for import-as-text behavior.

Start with a small representative sample

A team receives tables from public pages and needs values to stay plain text when opened in a spreadsheet. Directory labels occasionally start with punctuation.

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.

Check how your destination handles text starting with each of four common formula markers. Use a harmless example rather than a command or network function.

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.

Leading whitespace can hide an expression indicator. Test that your workflow stays safe after cleanup, paste, and a downstream re-export.

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 Table · Notes. 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
Table · Notes=1+1'=1+1

Check that the sample appears as text and does not calculate. Also check a plus-prefixed phone for import-as-text behavior.

Review values preceded by spaces or a tab. Simple delimiter quoting and UTF-8 encoding handle different problems from spreadsheet expression interpretation.

Compare an ordinary minus sign in a product label, a plus-prefixed phone, and a simple expression-looking string in a notes field. Each should be reviewed as data in the target spreadsheet, with the value visible and no formula result taking its place.

Review the cases that can slip through

Quoting a cell for CSV format handles delimiters but does not by itself tell a spreadsheet to treat the value as text.

Spreadsheet behavior varies with application and import settings. A standard CSV export guards formula-looking prefixes and leaves the raw values in the Workbench. Review any separate workflow that strips apostrophes or transforms leading signs, because it can reintroduce ambiguity in the file's interpretation.

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.

Keep the original generated CSV and document text formatting rules for any team that modifies or republishes the export.

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.

Recheck text handling after a file is opened, modified, and exported again. A spreadsheet or integration can remove a protective prefix independently of the initial export.

Check the path used in production. Some teams copy from a browser into a cell, others download a CSV and later resave it. Verify interpretation at the last step that opens the data, especially after transformations that trim punctuation or whitespace.

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 Table · Notes 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.