BambooHR data in BigQuery

[Picasso]

Our finance team builds headcount and labor cost reports in BigQuery, but all employee information still lives in BambooHR. Once a month, someone exports several spreadsheets and uploads them manually. By the time the report is ready, a few employees may have changed departments, started new roles, or left the company, so the numbers don’t always match BambooHR anymore. How can we move the data into BigQuery and keep it updated without repeating the whole export every month?

[Bermudo]

Start by deciding which BambooHR fields the finance team actually uses in its reports. Keep personal addresses, bank details, and other unrelated employee information out of the analytics database. Use the BambooHR employee ID to match each person across both systems, since names and job titles can change. Give access to the resulting tables only to the employees who already work with this information.

[Cabanas]

A fixed set of fields will keep the reports organized, but it won’t remove the monthly exporting and uploading. The connection also has to update existing employee records so that every department change or departure doesn’t create another copy of the same person. You can read how to move BambooHR to BigQuery here: http://datrise.com/en/pipeline/bamboohr-to-bigquery . Begin with employee records and department information before adding the remaining HR data. Run the transfer twice with the same records and confirm that the second run updates them without producing duplicates.