Bullhorn Recruitment Cloud Data Migration

Summary

The data migration strategy for the BH4SF client A Company is the organization where the contact works. This can also be called the Client. is defined in the SOW The Statement of Work lays out what the customer's project requires, how much effort is involved, and how much it will cost.. It will either be a Full Data Migration where Bullhorn will upload and sync all the client's data or a CV-Only Data Migration where we will just upload and sync CVs to Candidate A person looking for a job. A candidate can also be referred to as a Job Seeker, Applicant, or Provider. records and the client will be fully responsible for uploading all their data.

There will be a test data migration initially onto a Sandbox Non Production Environments are used by customers to test new features prior to them going live. Org, which will be used for Client UAT and Client Training. The Production data migration will happen just before Go-Live. The following content covers the tasks for the preparation and running of data migrations.

Prep: CV-Only Import

The PM will book a Data Engineer (DE) resource and request an FTP account be set up for the client.

Plan a call to review the CV Import Best Practices. Follow the call with an email, including data migration instructions and the data mapping spreadsheet.

Send details of the FTP account to the client.

Quality Check Points for CV Only Data Migration

• Consultant Used mainly in USA recruitment industry, a Consultant is a person placed on a tempory contract/vacancy (Consultant is only used for temporary jobs, not for permanent positions): Send instructions to the client.
• Client: Complete the Data Mapping Spreadsheet.

Prep: Full Data Migration

The PM will book a Data Engineer (DE) resource and request an FTP account be set up for the client.

Refer to the SOW to confirm which objects we will be migrating.

Schedule and host a Data Migration meeting with the client to:

• Explain the data migration process and what the client's responsibilities are.
• Walk through the data mapping spreadsheet of a full migration.

The Data Mapping Spreadsheet should evolve throughout the Design & Build phase and reflect the client's configured Org.

Work with the client to complete the Data Mapping Spreadsheet.

Send details of the FTP account to the client.

Quality Check Points for Full Data Migration

• Consultant: Host Data Migration Workshop.
• Consultant/Client: Complete the Data Mapping Spreadsheet.

CV Only Data Migration

With this option, the client is entirely responsible for extracting the data from their existing system and uploading it to the new BH4SF Org using the Salesforce Data Loader. A Bullhorn DE will upload and sync their CVs, so the client will need to upload these files and the Data Mapping Spreadsheet to an FTP account.

Client Responsibilities

Before we can complete the CV migration, the client needs to do the following:

1. Create CSV extract files of their data based on the Data Mapping Spreadsheet.
2. Load data to the Org using the Salesforce Data loader.
3. Match the Candidate CV to the candidate's SF Salesforce ID and update the Data Mapping Spreadsheet to reflect this.
4. Load the Data Mapping Spreadsheet and CVs (files) to their FTP account.

Bullhorn Responsibilities

When the client has completed their tasks, we can complete the migration:

1. The DE will load the CV files into the AWS and update the URL on the Contact Document Object.
2. Index A collection of files that can be searched by client data entity types. When records can be found in training login, but not the live system, it may require a bootstrap of the index./sync the files in TextKernel A Bullhorn Recruitment Cloud partner. One of the Search and Match / Resume Parsin services providers integrated with Bullhorn Recruitment Cloud.
3. Verify and test the loaded data on the Org.

No data cleansing or manipulation will be done by the Consultant or the DE.

Fix any data transfer issues (DE or Consultant).

Quality Check Points

• Client: Load all data to the Org.
• Client: Match the Candidate CV to the candidate's SF ID and load all CVs & Data Mapping Spreadsheet to the FTP account.
• DE: Load CV files.
• Consultant: Index/sync in TextKernel.

Full Data Migration

With this option, Bullhorn is responsible for uploading all the client's data from their CSV extract files to the new BH4SF Org using the Salesforce Data Loader. The DE will also upload and sync their CVs. The client will have to extract all their data into CSV files and upload them to an FTP along with the Data Mapping Spreadsheet and their CVs.

Client Responsibilities

Before we can complete the CV migration, the client needs to do the following:

1. Create CSV extract files for all their data based on the Data Mapping Spreadsheet.
2. Load the CSV files, Data Mapping Spreadsheet, and CVs (files) to their FTP account.
3. Match the CV files to the candidate SF ID and update the Data Mapping Spreadsheet to reflect.

Bullhorn Responsibilities

When the data is ready, Bullhorn can complete the migration:

1. The Data Engineer (DE) will load all the data to the Org using the Salesforce Data loader.
2. At this point, ask the client to match the CV to the candidate's SF ID and update the Data Mapping Spreadsheet to reflect this.
3. The DE will load the CV files into the AWS and update the URL on the Contact Document Object.
4. Index/sync the files in TextKernel.
5. Verify and test the loaded data on the Org.

No data cleansing or manipulation will be done by the Consultant or DE.

Fix any data transfer issues (DE or Consultant).

Quality Check Points

• Client: Load the CSV files, Data Mapping Spreadsheet, and CVs (files) to the FTP account.
• Consultant/DE: Load all data to the Org.
• Client: Match the Candidate CV to the candidate's SF ID and update the Data Mapping Spreadsheet.
• DE: Load CV files.
• Consultant: Index/sync in TextKernel.

Follow-Up: Data Migration

Client will verify and test the loaded data on the Sandbox Org.

Client to sign off Data Migration by email.