Migrate from Asure to Bullhorn ATS & CRM

Asure Employee records map to Bullhorn Worker. Core fields (firstName, lastName, email, hireDate, terminationDate, department, jobTitle, employmentStatus) migrate directly. Compensation rate from Asure maps to Bullhorn custom fields on Worker because Bullhorn's standard pay structure is placement-centric (Bill Rate, Pay Rate on Placement) rather than employee-centric. We preserve the Asure employment type (full-time, part-time, contractor) as a custom field on Worker.

Asure Company records map to Bullhorn ClientCorporation. The companyName becomes name, address fields map to the standard Bullhorn address block, and phone/website migrate as-is. ClientCorporation is created before Worker import so the ClientCorporationId lookup is satisfied at the moment of Worker insert. If the customer's Asure tenant is their own organization (internal HR use), we treat it as a special 'Internal' ClientCorporation in Bullhorn for reporting purposes.

Asure departments migrate as Bullhorn Department records and are linked to Worker via the workersDepartmentId lookup. Department is populated before Worker import to avoid orphaned references. If Bullhorn's department structure is not yet configured, we create the department records during the schema phase.

Asure's reporting structure (manager-employee relationships) maps to Bullhorn's supervisorWorkerId lookup on the Worker entity. We resolve the supervisor reference by matching manager Employee IDs to Bullhorn Worker IDs after the Worker batch is loaded. Circular references and managers not yet in the system go to a reconciliation queue for the customer to resolve before finalization.

Asure PTO and leave balances are stored as accrual ledgers per employee. Bullhorn ATS has no native accrual ledger; we create a PTO_Balance__c custom object (up to 10 on Front Office Growth/Enterprise, 2 on Bullhorn ATS) attached to the Worker record. Each accrual type (vacation, sick, personal) becomes a separate custom object instance. The accrual method (front-loaded, per-hours-worked, anniversary-based) is preserved in a custom field accrualMethod__c so the customer's Bullhorn admin can configure the correct accrual rules post-migration.

Asure health, dental, vision, and voluntary benefit elections map to Bullhorn Benefits_Enrollment__c custom objects attached to Worker. Plan names, carriers, coverage tiers (employee, employee+spouse, family), and effective/termination dates migrate as fields. Bullhorn has no native benefits administration; these records serve as a reference archive for the customer's HR admin. Mid-year enrollments are flagged with a closed plan year marker to prevent recalculation triggers.

Asure historical payroll register files (earnings, deductions, taxes, net pay per pay period) migrate to Bullhorn Payroll_Register__c custom objects. Bullhorn BackOffice (a separate module for staffing firm payroll) handles live payroll processing; the register history from Asure serves as an audit archive. We batch by pay period, map earnings codes to a custom Earnings_Type__c field, and attach each register record to the Worker. The customer's Bullhorn BackOffice admin uses this as reference when setting up pay rules.

Asure federal, state, and local tax withholding profiles per employee migrate to Bullhorn Tax_Profile__c custom objects attached to Worker. The jurisdiction codes, filing status, and allowances migrate as fields. Bullhorn does not process payroll tax calculations natively; these records are a migration artifact that the Bullhorn BackOffice admin or the customer's external payroll system uses to configure withholding in the destination. We audit the Asure export schema for truncated tax codes and request a manual jurisdiction list if the export appears incomplete.

Asure document repository files (W-4, I-9, offer letters, performance records) migrate as Bullhorn ContentDocument records linked via ContentDocumentLink to the Worker record. We extract attached files from Asure, match them to the corresponding Worker by employee ID or email, and attach them to the Bullhorn Worker. Note records with document summaries are created as supplementary references where file extraction is not feasible.

Asure clock-in/clock-out logs, shift codes, overtime rules, and time-off request statuses normalize to Bullhorn Time_Entry__c custom objects attached to Worker. Because Bullhorn ATS does not include a native time and attendance module, these migrate as historical reference records. Shift codes map to a custom shiftCode__c field, overtime flags to overtimeEligible__c, and time-off request status to a custom status__c picklist.

Pending or recent self-service changes (address updates, direct deposit preferences, emergency contacts) from Asure's employee portal are flushed to a staging queue before migration. We apply these as direct field updates on the corresponding Worker record during import rather than importing them as separate notes. Any unresolved pending changes are reported in the reconciliation output for the customer to address manually.

Asure custom fields on Employee, Company, and Benefits migrate to Bullhorn custom fields of matching type (text, number, date, picklist, checkbox) on the equivalent Bullhorn entity. Bullhorn supports custom fields via the Admin Field Mappings interface; we pre-create the field definitions during the schema phase using Bullhorn's metadata API. Picklist values migrate as-is; any Asure picklist values not in Bullhorn's allowed set are flagged for the customer's admin to validate.

Asure's background screening partnership with MyHRScreens does not expose records via standard export APIs. We flag this as a manual retrieval step: customers must request their screening history directly from MyHRScreens and upload the reports to Bullhorn as Notes or ContentDocument attachments on the corresponding Worker record. We include a data retrieval checklist in the migration handoff document.