Moving to RolePark from another ATS or spreadsheets
RolePark imports candidates from a CSV or Excel (.xlsx) file that any ATS or spreadsheet can produce, and a whole account from a supported full account export of another ATS. This page lists what each path carries over, its limits, and what stays behind.
In short
- Candidates from any ATS or spreadsheet: a CSV or Excel (.xlsx) file up to 5 MB and 5,000 rows, with automatic column matching.
- A full account export from another ATS (ZIP up to 50 MB): vacancies, candidates, applications with their stages, comments and CV files.
- Up to 15 PDF CVs at once into a vacancy, and job-board notification emails from Work.ua, Robota.ua and Djinni.
- Your data can leave too: a company export is a ZIP with JSON and CSV for every table plus the stored files.
Candidates from a CSV or Excel file
Export candidates from your current ATS or spreadsheet as CSV (UTF-8) or an Excel workbook (.xlsx): an Excel file does not need converting. An old .xls file or a password-protected workbook is not accepted — save it as .xlsx without a password. In Google Sheets, use File → Download → Microsoft Excel (.xlsx) or CSV. Then open Candidates in RolePark and select Import from CSV or Excel.
What a spreadsheet import carries over
- Name, email, phone, LinkedIn, location, current position and company, skills, tags, source, salary expectations, notice period, English level and notes.
- Any column can also go into one of your company’s custom fields.
- Skills and tags are split on commas and similar separators; notes become a team note on the candidate.
- Without a source column, the source is “CSV import” or “Excel import”.
How it works
Limits: 5 MB and 5,000 rows per file. Each row needs a first name and an email, phone or LinkedIn address. Candidates already in your company — matched by email, phone or LinkedIn — are skipped, not merged, and duplicates inside the file are skipped too. The import is all or nothing: if it fails, nothing is half-written.
- Download the sample CSV if you want to see the expected columns.
- Upload your file. If an Excel workbook has several sheets, choose the one you need. RolePark matches the columns automatically and shows the first rows.
- Check each column’s mapping, change it or skip the column, and confirm.
What a spreadsheet import does not carry
Vacancies, pipeline stages, interview history and CV files are not part of a spreadsheet import. Imported candidates start in your database, ready to be added to vacancies.
A whole account from another ATS
A company administrator uploads the full account export (ZIP, up to 50 MB) through Import company data on the company page; that dialog names the export formats RolePark reads. RolePark first shows a preview: counts, errors, the list of source stages and possible duplicates. Nothing is imported until you map the stages to RolePark stages and confirm.
- Vacancies are created as drafts, so nothing is published by surprise.
- Candidates, their applications with the mapped stage and disqualification reason, comments with their original dates, and CV files contained in the archive (PDF, DOC, DOCX).
- Fields that have no place in RolePark are kept as text in a candidate note, and other source records — interviews, ratings, messages, templates — stay in a migration record you can download.
- If an email already exists in your company, you choose whether to create a separate candidate or skip it.
- The import runs in the background; you can close the window. A preview that is not confirmed expires after 48 hours, and a failed import leaves nothing partial behind.
CVs and job-board emails
- Add candidates from CVs: on a vacancy page, upload up to 15 PDF CVs at once. RolePark extracts the contacts, you review the rows, and new candidates land in the vacancy’s New stage.
- A single PDF CV (up to 10 MB) can fill in a new candidate’s form. CV files in PDF, DOC and DOCX can be attached to any candidate.
- Saved notification emails from Work.ua, Robota.ua or Djinni (.eml, up to 10 at a time) become incoming applications with the candidate, CV and cover letter.
Through the API
Developers can add candidates with the RolePark API using a key with the candidates.write scope. If the candidate already exists, RolePark fills in only the empty fields. Vacancies and applications cannot be created through the API.
A practical order of work
Candidate imports need ATS access — the one-calendar-month trial every new company gets at registration, or continued ATS access arranged with the RolePark team. Importing is done by an administrator or a recruiter; a company import is for administrators only.
- Create the workspace and set up your vacancies and pipeline stages.
- Import a small sample first and check the fields you rely on.
- Import the rest, then invite the team: hiring managers and interviewers do not take paid seats.
How long it takes and who does what
- A spreadsheet import happens while you wait: upload the file, check the column mapping and confirm. An account export import runs in the background, so you can close the window.
- You export the data from your current system and check the mapping. RolePark matches the columns, skips duplicates and tells you which rows it skipped.
- If a file does not import as expected, write to the RolePark team at help@rolepark.com with the error message — there is no need to send the file with candidates.
- Free has no time limit and needs no card: 1 recruiter seat and up to 3 published jobs. Candidate imports need ATS access — the one-calendar-month trial every new company gets at registration, also without a card.
Taking your data out of RolePark
A company administrator can export company data at any time, with or without ATS access. The ZIP contains every table as JSON and CSV, the stored files such as CVs and attachments, and a manifest with checksums. Such an archive can be restored into an empty RolePark company.
Frequently asked questions
Can RolePark import from another ATS?
Use a CSV or Excel (.xlsx) export of your candidates: it works with any system that can produce one. A whole-account import is available for supported full account exports; Import company data names them.
Can I upload an Excel file?
Yes. An Excel workbook (.xlsx) uploads as it is, with no conversion; if it has several sheets, you choose one. An old .xls file or a password-protected workbook needs saving as .xlsx without a password first.
What happens to duplicates?
A CSV or Excel import skips candidates that already exist (same email, phone or LinkedIn) and reports them. An account import lets you choose: a separate candidate or skip.
Do interviews and scorecards come across in an account import?
Not as live data. They stay in the downloadable migration record; candidates, applications, comments and CV files are imported.
Can I take my data out later?
Yes. The company export gives a ZIP with JSON and CSV for every table and the stored files, and it stays available without ATS access.