How to export iPhone contacts to Excel

"Export to Excel" almost always means "produce a CSV file that Excel can open without breaking it". Excel handles its native .xlsx format too, but for contact data the CSV path is what people actually use because it works across every CRM, every email tool, and every database. This guide covers both, and the format settings that stop Excel from quietly destroying your phone numbers.

Path A: CSV (recommended)

The fastest route on iPhone is Pluck: tap Load My Contacts, pick countries, choose CSV, share. Done in under a minute on your phone with no Mac involved. Full walkthrough in how to export iPhone contacts to CSV.

Once you have the CSV, open it in Excel via the import wizard, not by double-clicking the file. The wizard lets you set column types, which is the only way to keep phone numbers intact:

1. Open a blank workbook.
2. Data → From Text/CSV.
3. Pick the file. Excel previews the data.
4. Click Transform Data.
5. For the phone column, click the data-type icon in the column header and pick Text.
6. Hit Close & Load.

Path B: Native .xlsx (also fine)

Pluck can output .xlsx directly, with one sheet per country if you have multiple. The advantage: no import wizard required. The file already has correct cell types because Pluck writes them. The disadvantage: .xlsx is bigger than CSV and Pluck doesn't include formulas (just data), so for some workflows CSV is still simpler downstream.

Format gotchas Excel will hit you with

Leading zeros disappear

A phone number like 0207 946 0958 (UK landline) becomes 2079460958 when Excel decides it's a number. The fix is the column-type-on-import step above. If the damage is already done, the file is fine — only the in-Excel display is broken — but you'll need to re-import to get the zeros back.

The plus sign is treated as a formula

An international number like +14155552671 can trigger a #NAME? error or get evaluated as a math expression. Same fix. Pluck additionally guards against this by escaping potentially dangerous leading characters (=, +, -, @) when followed by non-digits, which mitigates a class of CSV injection issues.

Non-Latin names look like garbage

Names in Arabic, Cyrillic, or with accents can render as é-type mojibake. The cause: Excel guessed the wrong encoding. The CSV is fine — it's UTF-8. Re-import via the wizard and pick Origin: 65001 — Unicode (UTF-8).

How many contacts can Excel handle?

Officially, Microsoft caps a worksheet at 1,048,576 rows. If you have more contacts than that, you have a different problem. Realistically, anything under ~50,000 contacts loads instantly.

What about Numbers?

Numbers (Apple's spreadsheet) opens CSVs natively and handles UTF-8 correctly out of the box. Phone numbers still get the same number-vs-text treatment, so format the column as Text first if you care.