Scan Business Cards to Excel on iPhone: One Row per Card

To scan business cards to Excel on iPhone, capture the cards with a camera-scan app that turns the whole stack into one table, one row per card. Name the columns you want (name, title, company, email, phone, website, address) and export the result as Excel or CSV. The CSV imports into Google Contacts, Contacts on a Mac, Outlook or a CRM. The Excel file stays as a lead list you can sort and share.

The app that does this on iPhone is ignitai. It reads each card with Apple’s on-device text recognition, and an AI turns that text into the exact columns your plain-English instruction asks for. The page images stay on the phone; only the recognized text goes to ignitai’s servers, where the spreadsheet is built. Photos you already took work the same way.

In this guide11 sections

Why a stack of cards is a spreadsheet problem

One business card is easy on an iPhone. Live Text in the Camera and Photos apps picks out a phone number or an email address on the card and offers to call it, write to it, or add it to a contact. That works one detected item at a time and one card at a time, and nothing it produces is a row.

The real job is rarely one card. It’s sixty cards from a trade show, the fishbowl from a booth giveaway, or ten years of cards in a drawer that someone wants in the CRM by Friday. Each needs the same fields in the same columns:

• A consistent shape. Card layouts vary wildly: name at the top or the bottom, the title under the name or next to it, three phone numbers labeled M, T and D, or none labeled at all. A spreadsheet needs “mobile” in the same column on every row.
• Split fields. Contact imports want first and last name apart, and the address split into street, city, region and postal code. Cards print them as one block.
• One file. Sixty cards should be sixty rows in one spreadsheet, not sixty contact records to export and merge later.

Dedicated card scanners are built around a contact database of their own, and getting a spreadsheet out is an export step you have to check for and sometimes pay for. If the destination is a spreadsheet or a CSV import, it’s quicker to start there.

Scan business cards to Excel on iPhone: the steps

1. Capture the cards. Open ignitai and scan with the camera. Lay each card flat on a dark surface (most cards are white), fill the frame with it, and capture one card per page. Keep going card after card; the whole stack is one scan. Cards you’ve already photographed can be picked from your photo library instead, several at once, and card images someone emailed you can be sent to ignitai from Mail or Files with the share sheet.
2. Say what you want. A prompt is required, so the Convert button stays disabled until you type something. Start from the Form starter or write your own; the next section has one that fits most cards. Save it and it’s one tap away next time.
3. Convert. Before anything runs, ignitai shows how many pages the batch will use and how many you have left. It’s usually ready in under a minute. Converting needs an internet connection, because the spreadsheet is built on ignitai’s servers. On iPhone, progress shows on the Lock Screen and in the Dynamic Island, and a notification arrives when the file is ready.
4. Check the table. Every row is numbered, so the last row number should equal the number of cards you scanned. Open Original Pages to compare any row with the card it came from. If a column you asked for came back empty (fax, say, which almost nobody prints any more), ignitai tells you instead of leaving you to find out in Excel.
5. Share it as Excel or CSV. Share… is in every finished file’s menu. Pick CSV for an import into Contacts, Google Contacts or a CRM, and Excel for a list people will read and sort. Cells are edited in the spreadsheet app, not in ignitai.

Get ignitai on the App Store — free download; your first document (up to 4 pages) converts free with Sign in with Apple, and one subscription covers iPhone, iPad, Mac, and Vision Pro.

A prompt that fits most business cards

This instruction covers the fields nearly every card prints and the decisions that make a list importable:

“One row per business card. Columns: first_name, last_name, job_title, company, email, mobile, office_phone, website, street, city, region, postal_code, country. Put a number labeled M, Mobile or Cell in mobile and one labeled T, Tel, Office or D in office_phone. Keep phone numbers as printed, including the country code. Leave a field blank if the card doesn’t print it. Ignore slogans, logos and social-media handles.”

The choices behind it, and when to change them:

• Split the name. Google Contacts, Contacts on Mac and every CRM import first and last names as separate fields. A single full_name column works for a printed list and costs you a split later if you import it.
• Label the phones. Cards print mobile, direct and switchboard numbers with a letter or not at all. Telling the AI which label goes where is what keeps mobile numbers in one column. If your team only calls mobiles, drop office_phone.
• Keep numbers as printed. International cards carry +44 or +81 prefixes; reformatting them to a local pattern breaks them. Keep them as printed and your CRM or phone can normalize them.
• Blank beats a guess. “Leave a field blank if the card doesn’t print it” keeps the AI from filling a company column from an email domain. Where you need the company for a card that only shows a logo, the domain in the email address is the clue; fill it in yourself.
• Add what your pipeline needs. Name a linkedin or industry column in the prompt and it appears.

Some cards resist any prompt. A company name that exists only as a graphic wordmark isn’t text, so it may not come through. A QR code is an image, not text, so the link it hides won’t become a URL. And handwritten notes on the back (“wants a quote in March”) are outside what this guide promises; type them into a notes column after export. For a two-sided card, capture the side with the contact details. A second side is a second page against your allowance, and it rarely adds a field.

From the spreadsheet to Contacts, Google and your CRM

The iPhone Contacts app has no CSV import, so the route into your phone’s address book goes through a Mac or through Google. Choose CSV when you share the file.

• Contacts on Mac. Choose File ▸ Import and pick the CSV. Contacts shows the first card and asks you to check each column’s label; set any column you don’t want to “Do not import”, and choose “Ignore first card” so the header row doesn’t become a contact. The new contacts sync to your iPhone through iCloud.
• Google Contacts. On contacts.google.com, choose Import and pick the CSV. Google matches columns by their header names, so the reliable trick is to export one existing contact as a Google CSV, read its header row, and use those exact names as the columns in your ignitai prompt. The contacts then appear on any iPhone signed in to that Google account with Contacts turned on.
• A CRM. HubSpot, Salesforce and Pipedrive all import a CSV and let you match each column to a field during the import. Import five rows first: a mapping mistake caught on five records is cheaper than one found on two hundred.

If the list is headed for people rather than an import, pick Excel. It opens in Excel, Numbers and Google Sheets; the header row is bold and the columns fit their content. Sort by company, filter by region, and run Data ▸ Remove Duplicates on the email column in Excel before anyone starts calling. If the team lives in a shared Google Sheet, the handoff is covered in the PDF-to-Google-Sheets guide for iPhone.

Tagging cards by event, without a source column

Batch output has no column that says which photo a row came from: filenames never leave your iPhone, so the AI never sees them. Two habits give you the traceability anyway:

1. One batch per event. Convert the trade show’s cards as one batch and the customer dinner’s as another. After export, add an event column in the spreadsheet and fill it down. The event name was never on the cards, so this column is yours to add, not the AI’s.
2. Original Pages for disputes. When someone swears the email on row 23 is wrong, open the converted pages in ignitai and compare; they stay on your device for exactly this check.

A worked example: sixty cards from a two-day trade show

You come home from a two-day show with 34 cards from the first day and 26 from the second. The sales team wants them in HubSpot by Monday, tagged by show.

1. Prove the prompt first. Scan four cards and run them with the prompt above. Fix whatever the output shows you: a job title that swallowed the department, or a phone column you don’t need. A test of four pages or fewer costs almost nothing against your allowance.
2. Day one, 34 cards. Camera scan, one card per page. Tap your saved instruction and convert. ignitai shows 34 pages before it starts; the last row number in the table should be 34.
3. Day two, 26 cards. Same saved instruction, second batch. Last row number: 26.
4. Combine and tag. Open both files in Excel, paste day two under day one, add event and day columns, and remove duplicate emails; someone who gave you a card on both days is the usual repeat.
5. Import. Save the combined sheet as CSV and run HubSpot’s import, matching each column to a property.

Sixty cards is 60 pages, inside the plan’s 80 pages a week. A 150-card show is not: the plan includes 80 pages a week (up to 320 a month, with unused weekly pages not carrying over), so either spread the stack across two weeks or buy extra pages while subscribed. Packs run from 5 pages to 1,050, and bought pages never expire. The page count ignitai shows before each conversion tells you where you stand before you commit, and cancelling a run while it’s still going charges nothing.

On iPad and Mac

The same subscription and the same saved instructions work on the other devices:

• iPad. The camera scan works the same way, and on iPad you can sort the finished table by any column, select rows and copy them straight into an email or a Slack message before exporting anything. That’s handy when one colleague only needs the cards from their region.
• Mac. Choose File ▸ Import from iPhone or iPad and scan the cards with the iPhone’s camera straight into the Mac app, or drag card photos onto the ignitai window. Keep photos and PDFs in separate batches: a drop that mixes them imports only the PDFs. A finished spreadsheet can be dragged out of the app into a folder or an email.

Card photos are pictures of printed text like any other. The general photo workflow in the picture-to-Excel guide for iPhone applies to them, a stack you scanned to a PDF with another app goes through the scanned-PDF-to-Excel flow with this same prompt, and the conference’s other paper pile has its own guide: receipts to a spreadsheet on iPhone.

Privacy: whose data is on those cards

A stack of business cards is other people’s contact details, handed to you for business use. The card images stay on your iPhone. The recognized text (names, titles, emails, phone numbers) is sent to ignitai’s servers, where the AI builds the spreadsheet. The finished file is stored in your ignitai account, so it opens on your other devices after Sign in with Apple, until you delete it; any file, or the whole account, can be deleted from inside the app. That’s less than handing a web converter every card image, but it isn’t nothing. If your company has rules about where customer contact data may be processed, check them before you convert, just as you would before importing the list into a new CRM.

When a dedicated card scanner is the better tool

• You want the contact on the spot. To have someone in your phone’s Contacts before they walk away, a card-scanner app that writes straight to Contacts does it in one step. ignitai’s output is a spreadsheet, not a contact record.
• Your CRM already scans. Some CRM mobile apps (HubSpot’s, for one) include a card scanner that creates the record directly. If one card at a time into that CRM is fine, use it.

ignitai is the better tool for a batch: a stack of cards that should become one spreadsheet with the columns you chose.

Bottom line

Scanning business cards to Excel on iPhone comes down to three decisions: capture one card per page, name the columns in one plain-English instruction (names split, phones labeled, blanks left blank), and choose CSV for an import or Excel for a list. In ignitai the stack becomes one spreadsheet with a row per card; the last row number tells you nothing was missed. Reach the iPhone’s address book through Contacts on a Mac or Google Contacts, or use your CRM’s import screen. For one card you want in Contacts right now, a dedicated card scanner is faster. For a stack, start with the spreadsheet.

FAQ

What is the best way to scan business cards into Excel on iPhone?

Scan the cards with a converter that takes a whole stack at once and lets you name the columns. In ignitai you capture one card per page with the camera, type a one-line instruction such as ‘one row per card: first name, last name, title, company, email, mobile, website’, and share the result as Excel or CSV. Every card becomes a row in one spreadsheet.

Can I import the spreadsheet into my iPhone contacts?

Not directly on the iPhone, which has no CSV import. Import the CSV into Contacts on a Mac (File ▸ Import, then check each column’s label) or into Google Contacts, and the new contacts sync to the iPhone through iCloud or your Google account. CRMs such as HubSpot, Salesforce and Pipedrive take the same CSV through their import screens.

How many business cards can I scan at once?

A whole stack goes into one batch and comes out as one spreadsheet. Each card is one page: ignitai shows the page count before it converts, and the plan includes 80 pages a week, up to 320 a month, with extra pages available while subscribed. Try your instruction on four cards or fewer before running a big stack.