As a product settings admin, you can export project data from your Talent Hub contract and import hiring projects into your Talent Hub contract.
Data Export
You can export all project data including pipelines, candidate data, attachments, and job descriptions in your LinkedIn Talent Hub contract in CSV formatted files.
Note: To keep your content secure, the links in the exported CSV are specific to the user who downloaded the file. To open the links, you need to be logged into LinkedIn Talent Hub.
Here's a tip
It can take up to 24 hours to complete the export. Please note that any files uploaded within 8 hours prior to the export won’t be included. Once the export is completed, an upload link will appear next to the file export selection and will remain active for 24 hours.
The export.csv file contains the download URL for each file:
- The export.zip file contains csv files for all ATS data entities.
- (If applicable) Attachment <candidateid_1> - <candidateid_N>.zip files contain the download URL for attachments linked to candidate IDs, which can be multiple files depending on the size of the attachments.
Important to know
LinkedIn pulls data from job applications (provided by the applicant directly in the application flow, manually added by the recruiter on behalf of sourced candidates, imported by the recruiter into the ATS directly, or migrated from customer’s previous ATS) and never from LinkedIn member profiles.
Column Field Descriptions for CSV Data Files
The Export.zip file includes the following CSV data files:
| CSV File | Fields (Left to Right) |
|---|---|
| Candidates.csv Includes all applicants and sourced candidates (excludes contact information from sourced candidates for member privacy unless manually added by the recruiter). The candidate ID can be used to map the candidate CSV to the Attachments folder. | candidate_id: uniquely identifies candidates across all exported CSVs for easy lookup project_id: project id relevant for each candidate. The Project_id is specified in the Projects.csv file. first_name: candidate first name last_name: candidate last name emails: separated email ids (;) phone_numbers: separated phone numbers (;) tags: separated tags (;) profile_url: candidate LinkedIn url sourcing_channels: candidate source (e.g. applicant, import, or referral) hiring_state_id: most recent candidate pipeline stage created_time: time of creation, format: milliseconds from epoch created_datetime: date-time of creation, format: yyyy-MM-dd HH:mm:ss last_modified_time: time of last modification, format: milliseconds from epoch last_modified_datetime: date-time of last modification, format: yyyy-MM-dd HH:mm:ss |
| CustomFieldsDefinitions.csv Provides definitions for all custom fields created in Talent Hub. | custom_field_id: uniquely identifies custom fields across all exported csvs for easy lookup entity_type: defines what entity this belongs to (e.g. candidate or project) description: custom field description name: name of custom field state: active or deleted type: format of field (e.g.string, number, multivalue, single value) custom_field_definition_values: separated values (;) created_time: time of creation, format: milliseconds from epoch last_modified_time: time of last modification, format: milliseconds from epoch created_datetime: date-time of creation, format: yyyy-MM-dd HH:mm:ss last_modified_datetime: date-time of last modification, format: yyyy-MM-dd HH:mm:ss
|
| CustomFieldValues.csv Provides a list of all custom field values for each candidate. The candidate ID maps to the Candidate.csv file. | custom_field_id: maps to the CustomFieldDefinitions.csv file entity_type: defines what entity this belongs to (e.g. candidate or project) entity_id: the entity id (e.g. candidate or project id) custom_field_values: the value for this custom field created_time: time of creation, format: milliseconds from epoch last_modified_time: time of last modification, format: milliseconds from epoch created_datetime: date-time of creation, format: yyyy-MM-dd HH:mm:ss last_modified_datetime: date-time of last modification, format: yyyy-MM-dd HH:mm:ss |
| Feedbacks.csv Provides all candidate feedback requested by admins using the Share for review function. | feedback_id: uniquely identifies candidate feedback candidate_id: maps to the Candidate.csv file project_id: maps to the Project.csv file company_id: company ID requester_role: role of the feedback requester message: message associated with the feedback request from the requester feedback_response: feedback response on the candidate recommendation_score: score for candidate’s job fit approved_for_referral: specifies if the candidate was approved for referral (true or false) requester_profile_url: profile url of the requester requestee_profile_url: profile url of the requestee created_time: time of creation, format: milliseconds from epoch created_datetime: date-time of creation, format: yyyy-MM-dd HH:mm:ss last_modified_time: time of last modification, format: milliseconds from epoch last_modified_datetime: date-time of last modification, format: yyyy-MM-dd HH:mm:ss |
| HiringStates.csv Provides all hiring states (i.e. pipeline stages) for all custom pipelines created. The hiring state ID maps to the Candidate.csv file. | candidate_hiring_state_id: uniquely identifies the hiring states (pipeline stages) name: name of the state (stage) type: parent category of hiring state (e.g. interview, or phone screen) created_time: time of creation, format: milliseconds from epoch created_datetime: date-time of creation, format: yyyy-MM-dd HH:mm:ss last_modified_time: time of last modification, format: milliseconds from epoch last_modified_datetime: date-time of last modification, format: yyyy-MM-dd HH:mm:ss |
| InterviewModules.csv Provides interview module data for the modules associated with the scorecards submitted in Talent Hub. | interview_module_id: uniquely identifies candidate interviews description: describes the interview module name: interview module name state: status of interview module (e.g. draft, invitation sent, or feedback pending) start_time: interview start time end_time: interview end time created_time: time of creation, format: milliseconds from epoch created_datetime: date-time of creation, format: yyyy-MM-dd HH:mm:ss last_modified_time: time of last modification, format: milliseconds from epoch last_modified_datetime: date-time of last modification, format: yyyy-MM-dd HH:mm:ss |
| Messages.csv Provides InMail and Email message content sent to candidates from Talent Hub. The candidate ID maps to the Candidate.csv file. Messages marked as private aren't exported for security reasons, only public messages are exported. | message_id: uniquely identifies the candidate message candidate_id: maps to the Candidate.csv file sender_profile_url: message sender’s LinkedIn url subject: message subject body: message body type: InMail, email, reply created_time: time of creation, format: milliseconds from epoch created_datetime: date-time of creation, format: yyyy-MM-dd HH:mm:ss last_modified_time: time of last modification, format: milliseconds from epoch last_modified_datetime: date-time of last modification, format: yyyy-MM-dd HH:mm:ss |
| Notes.csv Provides public notes added to candidate profiles. The candidate ID maps to the Candidate.csv file. No private notes will be included for security reasons. | note_id: unique id project_id: maps to the Projects.csv file candidate_id: maps to the Candidate.csv content: content of note owner_profile_url: note owner’s LinkedIn url visibility: The visibility of the note, such as HiringContext or Project created_time: time of creation, format: milliseconds from epoch created_datetime: date-time of creation, format: yyyy-MM-dd HH:mm:ss last_modified_time: time of last modification, format: milliseconds from epoch last_modified_datetime: date-time of last modification, format: yyyy-MM-dd HH:mm:ss |
| Projects.csv Provides project and job level data for all projects. Also includes imported projects and jobs if applicable. The candidate hiring state ID maps to the HiringStates.csv file. | (project related export data) project_id: uniquely identifies projects across all the exported csvs for easy lookup. project_name: project name visibility: visibility level of project state: state of project: ACTIVE, CLOSED, or DRAFT type: e.g. job posting owner_profile_url: project owner’s LinkedIn url candidate_hiring_state_ids: separated hiring states (e.g. stages) included in the project pipeline (;) sourcing_channels: list of sourcing channels active in this project project_description: project description (job related export data, each project can have many job IDs associated) job_post_id: job post id associated with the project job_post_description: description of job post job_post_created_at: time of job posting job_post_state: job post status (active, or closed) (project related timestamps) created_time: time of creation, format: milliseconds from epoch created_datetime: date-time of creation, format: yyyy-MM-dd HH:mm:ss last_modified_time: time of last modification, format: milliseconds from epoch last_modified_datetime: date-time of last modification, format: yyyy-MM-dd HH:mm:ss |
| Scorecards.csv Provides interview scorecard feedback, recommendation, and scoring. The candidate ID maps to the Candidate.csv file. | scorecard_id: unique id project_id: maps to the Projects.csv file candidate_id: maps to the Candidates.csv file interview_id: candidate interview id interviewer: LinkedIn url of interviewer interview_module_id: maps to the InterviewModule.csv composite_score: total candidate score submitted by interviewer overall_recommendation: candidate recommendation submitted by interviewer (e.g. strong yes, yes, no, or strong no) |
Descriptions for Candidate Attachment Files
Candidate attachments are included in the attachments.zip file.
Statistics in export.csv file have two entries
- Total files: total number of attachment files present for a contract
- Failed files: indicates the number of files that are missing from the export data
Applicant attachments are provided in folders marked public, private, and miscellaneous. For example, resumes in a public folder, offer letters and signing documents in a private folder, and other types of documents in a miscellaneous folder. Each folder holds up to 2 GB of data. Additional folders are created as needed to hold all attachments.
To look up attachments for a given candidate ID, copy the candidate ID and search for that ID across all the attachment folders. Refer to the candidate ID range specified on the attachment.zip file if you have multiple attachment folders.
Here's a tip
To make it easier to look up a candidate ID, after you download and extract all the attachment folders, move all attachment files into a single folder. If a candidate didn't have any attachments stored in Talent Hub, the folder for that candidate would have an empty.txt file.
If there are multiple attachments of the same type found for the same candidate, we’ll export all and append a numeric suffix to the filenames (numeric suffix are added randomly & not in chronological order of upload time).
Important to know
Any attachments uploaded in less than 8 hours from triggering export won’t be included in the export.
Candidate Attachment Folder Descriptions
| Folder Name | Description |
|---|---|
| Public | Includes candidate resumes that have been submitted by the candidate or manually uploaded and tagged as a resume. |
| Private | Includes potentially sensitive documents stored in an e-signature module (e.g., offer letters). |
| Miscellaneous | Includes all attachments not tagged as a resume and other miscellaneous attachments. (e.g., cover letters, and referral letters). |
Import Projects
You can import hiring projects into your Talent Hub contract.