Contact

Microsoft Excel 2013 for Windows; Microsoft 365 differences noted · Import and data cleanup · Beginner

Keep 16-Digit Tracking Numbers Intact in Excel 2013

Import long identifiers as text before Excel changes their digits, verify exact matches, and recover safely from a damaged import.

Official documentation reviewed; sample strings independently checked; not tested in Excel · Editorial standards

Import the identifier column as Text before Excel interprets it as a number. In Excel 2013 for Windows, use the Text Import Wizard and select Text for that column in step 3. A 16-digit tracking ID is a label, even when every character is a digit.

Excel’s numeric precision limit is 15 significant digits. Formatting an already damaged numeric value as Text cannot reconstruct the missing digits. Keep the original CSV unchanged until the imported values have passed exact comparisons. Microsoft: leading zeros and large numbers.

A small file that exposes the problem

Download the synthetic tracking-number CSV. Save it first; do not double-click it into Excel. Its contents are:

TrackingID,Parcel
1234567890123456,Practice-A
1234567890123457,Practice-B
0012345678901234,Practice-C
0000000000000001,Practice-D

The first two IDs differ only at character 16. They must remain different. The last two test leading zeros. Each identifier has exactly 16 characters.

Open the CSV in a plain-text editor if you want to inspect the original. Quotes around a CSV field, by themselves, do not declare an Excel text type. CSV carries characters and separators, not workbook cell types.

Import with the Excel 2013 wizard

Use a blank workbook and an empty destination, such as Sheet1!A1.

  1. On the Data tab, use Get External Data > From Text and select the saved file. This is the legacy Windows ribbon route. If needed, make a separate copy with a .txt extension and open that copy through File > Open to invoke the wizard. Keep the .csv original.
  2. In step 1, choose Delimited. Keep the header row. The sample uses only ASCII characters, so there are no accented-character encoding choices to resolve.
  3. In step 2, select Comma, clear other delimiters, and check that the preview has two columns.
  4. In step 3, click the TrackingID preview column and choose Text. Check that its preview heading changes to Text. The Parcel column can also be Text.
  5. Select Finish, choose the empty destination if prompted, and complete the import.

The essential control is the selected column’s Text setting, not the destination cell’s appearance. The retained wizard documents column-by-column types; Microsoft’s import guide also documents the .txt route. Text Import Wizard; import text and CSV files.

Verify all digits, not just the display

With the header at A1, enter these checks in unused cells:

Check Formula Expected result
Stored as text =ISTEXT(A2) TRUE
Full length =LEN(A2) 16
First original ID =EXACT(A2,"1234567890123456") TRUE
Second original ID =EXACT(A3,"1234567890123457") TRUE
The two IDs are different =EXACT(A2,A3) FALSE
Leading zeros survived =EXACT(A4,"0012345678901234") TRUE
All 15 leading zeros survived =EXACT(A5,"0000000000000001") TRUE

Copy the type and length checks down through row 5. All four type checks should be TRUE and all lengths 16. The formula examples use English names and comma separators; some regional installations use semicolons between arguments.

The quotation marks in the EXACT tests deliberately make the expected IDs text literals. Do not compare against an unquoted 16-digit numeric constant. See ISTEXT, LEN, and EXACT for the individual checks. Microsoft’s IS, LEN, and EXACT references define their behavior.

Save the verified working copy as .xlsx. If you later export a CSV, the receiver must also import its ID column as text: the CSV does not retain the workbook’s Text setting.

If you already opened the CSV

Do not save over the source. Close the damaged import without overwriting it, then import the untouched file again as Text. If the source was overwritten, retrieve a previous version, backup, or fresh export from the system that owns the identifiers.

For the two nonzero-leading sample IDs, numeric import can turn both into 1234567890123450. There is no formula that can determine whether that last original digit was 6, 7, or something else. Changing to Text, widening the column, adding decimal places, or using TEXT only changes what remains; it cannot recover the discarded characters. The lost information must come from another intact source.

Treat these symptoms separately:

  • Scientific notation: a display such as 1.23457E+15 alone does not prove whether digits were lost. Inspect the formula bar and compare with the raw source.
  • Sixteen visible digits but a failed EXACT test: length alone is insufficient. A changed last digit still leaves a 16-character value.
  • Green warning triangle: a number-stored-as-text warning is expected for these IDs. Do not choose Convert to Number.
  • Missing leading zeros: do not guess how many to add unless the source’s fixed-width rule is independently known. Reimporting the intact original is safer.
  • Only one imported column: the delimiter selection is wrong. Restart the import and inspect the preview before finishing.

Microsoft 365 is a different entry point

In Microsoft 365 for Windows, the legacy wizard may need enabling under File > Options > Data > Show legacy data import wizards > From Text (Legacy). It is then available under Data > Get Data > Legacy Wizards > From Text (Legacy). These are modern Windows controls, not Excel 2013 setup steps. Wizard documentation.

Alternatively, use Data > From Text/CSV > Transform Data. In Power Query, inspect Applied Steps and replace or remove an automatic numeric type conversion before setting TrackingID to Text; merely adding a text conversion after a lossy numeric step is too late. Reload from the raw text source, then repeat the checks above. Current Microsoft 365 and Excel 2024 also have Automatic Data Conversion preferences; Excel 2013 does not have that feature. Microsoft’s current import and conversion guidance.

Version and verification notes

This is a legacy Excel 2013 Windows desktop workflow with a separate modern Windows comparison. It does not require the old Power Query add-in. Microsoft’s current wizard help lists newer supported editions; its modern ribbon instructions are not evidence of an Excel 2013 screen. The historical distinction between the old Get External Data wizards and modern Get & Transform is described in About Power Query in Excel.

Not tested in Excel. The documentation was checked on October 16, 2026. The sample strings, lengths, and expected exact comparisons were independently checked outside Excel; no native import or screenshot is claimed.