Kattia reads your column headers and maps them to application fields for you, so you don't need to rename columns first.
What you need
A CSV file, or an Excel workbook (.xlsx or .xlsm), up to 12 MB.
A company and a role on every row you want to import.
Optional columns: status, source, notes and a link to the job posting.
If you have an older .xls workbook, save it as .xlsx or CSV first.
Import a file
Select + Add application at the top of the page. On a phone, select the + button.
In the New application window, drop your file onto the box that says "or drop PDF, CSV, or Excel files here". You can also select that box to choose a file.
Select Add application.
Select Import to confirm.
On an empty board, you can select Upload a spreadsheet instead. It opens the file picker straight away.
When you import more than one application, Kattia lists them in an Applications added window. You can change the stage of each one there, then select Done. When you import one application, the window closes and the new card appears on your board.
You can also paste spreadsheet rows straight into the box. Kattia detects them when the first line is a header row, separated by commas or tabs, that names a column such as Company, Role, Position or Title. Select Add application, then Import to confirm.
How columns are mapped
Kattia reads these fields from your sheet:
What Kattia reads | Example headers |
Company | Company, Employer, Organization |
Role | Role, Job title, Title, Position |
Status | Status, Stage, Pipeline |
Source | Source, Via, Channel, Applied via |
Notes | Notes, Comments, Details |
Job link | URL, Link, Job link, Posting, Listing |
Headers don't need to match exactly, and the header row doesn't have to be the first row. Kattia works out which column is which, even when the headers are messy. Other columns, such as dates, salary and location, are not imported as separate fields.
Kattia uses a job link to read the posting, as described under "Job links in your sheet" below. If a row has no job link, Kattia uses the first web link anywhere in that row. Remove other links, such as company websites, from rows that have no job link. Kattia doesn't save the link itself on the application, so add it to the card afterwards if you want to keep it.
Where imported applications land
A row whose status matches a stage goes to that stage. The stages are Sourced, Applied, Interviewing, Offer, Unsuccessful and Ghosted. Kattia also accepts Interview and Hot for Interviewing, Viewed for Applied, and Rejected for Unsuccessful. Capital letters don't matter.
A row with a status that Kattia doesn't recognise goes to Applied. Kattia keeps the original status in the notes, as "Imported status:" followed by your text, so you can change the stage on the card afterwards.
A row without a status goes to Applied. If you opened the import from a stage column's + button, those rows go to that stage instead.
Your notes come across with the application.
A row without a company or a role is skipped. When some rows import, Kattia also tells you how many it skipped, for example "2 rows had no company or role."
Excel files
Kattia reads the first sheet of the workbook only. If your data is on another tab, move it to the first sheet, or export that tab as a CSV and import the CSV.
If some values come through wrong, for example cells that hold links, formulas or formatted text, save the sheet as a CSV file and import that instead.
Limits
File size: each file can be up to 12 MB. The New application window has no fixed number of rows per import.
Applications in your pipeline: Kattia has two plans, Free and Growth. Today every account has Growth, which has no limit on how many applications you hold. To compare the plans, see What is the difference between Free and Growth?.
During onboarding: the onboarding import takes up to 40 rows. See "Import during onboarding" below.
Job links in your sheet
If a row has a link to the job posting, Kattia can fetch the posting and add its details, such as the job description, to the application's notes. Kattia also uses the posting to replace a placeholder company or role, such as "n/a" or "TBD". This is capped per import and per rolling 24 hours:
Plan | Links fetched per import | Links fetched per 24 hours |
Free | 3 | 10 |
Growth | 15 | 30 |
Today every account has Growth, so the Growth numbers apply. Rows over the cap are still imported, without the details from the posting. If the same link appears on more than one row, Kattia fetches it once and adds the details to the first of those rows only. These caps are separate from the daily limit for pasting job links. Sites that need you to sign in, or that block automated reading, may not return any details.
Duplicates
Kattia skips a row when you already have an application with the same company and role. Capital letters and spaces at the start or end don't matter, and Kattia compares against every application in your pipeline. It shows a message that starts "Found", with the number of duplicates it won't import.
Kattia matches on company and role only, not on job links. It doesn't compare rows within the same file, so remove repeated rows from your sheet before you import.
Import during onboarding
When you set up your account, you can import a CSV file or paste CSV rows. This import works differently from the New application window:
It accepts CSV only, up to 40 rows. If the file has more rows, Kattia imports none of them and tells you how many it found.
You match each column to company, role, status, source or notes yourself. This import doesn't read job links from your file.
Every row must have a company and a role. If any row has a problem, nothing is imported, and Kattia lists the rows to fix.
For larger files, Excel workbooks and job links inside a spreadsheet, import from + Add application after onboarding.
If the import fails
Check that each row has a company and a role.
Check that the file is under 12 MB.
For an Excel file, check that your data is on the first sheet, or save it as a CSV file.
If the message says "Couldn't reach Kattia. Check your connection and try again.", select Try again.
If it still fails, add the application with Add details yourself, or contact support.
For more fixes, see What should I check when an import fails?.