SimpleVMS Mapping

SimpleVMS mappings within BOLD are essential for ensuring jobs, contacts, and skills are aligned between the two platforms. Follow this article to complete the SimpleVMS Mapping Setup.

Chapters:



Locating SimpleVMS Settings

  1. Click Account & Settings, then Utilities



  2. Type 'SimpleVMS' in the search bar and click on the SimpleVMS Settings Utility

 

Company Mapping​

Buyers mapped to the staffing agency vendor record in SimpleVMS will be displayed in the Company Mapping screen. There are two approaches to mapping SimpleVMS companies to receive jobs in BOLD:

  1. Direct Company Mapping: Map the VMS company directly to a BOLD company
  2. Worksite-Only Mapping: Use "Map by Worksite" without mapping the parent VMS company

If needed, you can create a new BOLD company from this screen.

Default Job Owners must be configured for each mapped BOLD company.

Note: If the company mappings are updated, it will only be reflected for new jobs moving forward. Existing jobs will remain under the original BOLD company.​


Map by Worksite: This feature allows mapping individual worksites to different BOLD companies, and can be used in two ways:

  • With mapped parent company: When a VMS company is mapped to a BOLD company, worksites can be mapped to different BOLD companies for multi-regional employers. Jobs from unmapped worksites will be created under the parent company's mapped BOLD company.
  • Without a mapped parent company: Worksites can be mapped directly to BOLD companies without mapping the parent VMS company. Jobs will only be created for mapped worksites - jobs from unmapped worksites will not be created in BOLD.

Important: When using worksite mapping without a mapped parent company, unmapped worksites will display a warning icon. Jobs from these unmapped worksites will not flow into BOLD automatically.

Manually Create Placements: Checking “Manually Create Placements” - The nomination stage in BOLD is updated to 'Hired' and the user is able to manually place the talent in BOLD. Leaving unchecked - The nomination stage in BOLD is updated to 'Hired', and the talent is automatically placed.

Job Template Override: This allows job details to be overridden based on templates when jobs are created. Job templates at the company level with exact name matching to the job title will use the template details instead of the job posting from SimpleVMS.

 

Contact Status Mapping

Each SimpleVMS manager status must be mapped to a BOLD contact status.​

Note: This will only need to be updated if you add a new BOLD contact statuses and would like to change your SimpleVMS contact status mapping.

 

Job Skill Mapping

Each SimpleVMS job skill must be mapped to a BOLD skill code.​

When a new SimpleVMS job is created in BOLD, the BOLD job will then have the mapped skill codes based on the job skill mapping configuration. This is vital for the purposes of job matching and distribution through 24/7.​

Note: This will only need to be updated if you add a new BOLD skill code and would like to change your SimpleVMS job skill mapping.

 

Job Type Mapping

Each SimpleVMS job type must be mapped to a BOLD job type.​

Note: This will only need to be updated if you add a new BOLD job type and would like to change your SimpleVMS job type mapping.

 

Job Status Mapping

Each SimpleVMS job status must be mapped to a BOLD job status.​

Note: This will only need to be updated if you add a new BOLD job status and would like to change your SimpleVMS job status mapping.

 

Placement End Reason Mapping

Each SimpleVMS worker end reason must be mapped to a BOLD placement end reason.​

Note: This will only need to be updated if: ​
  • You add a new BOLD placement end reason and would like to change your SimpleVMS placement end reason mapping​
  • A newly mapped SimpleVMS buyer has custom worker end reasons configured in SimpleVMS

Articles in this section

Was this article helpful?
0 out of 0 found this helpful
Share

Comments

0 comments

Please sign in to leave a comment.