Migrate from Mitratech Circa to BambooHR

Circa Job records (requisition details, location, EEO-1 category classifications, posting status, posted date) map to BambooHR Job records. We preserve Circa's job_id as a BambooHR custom field (circa_job_id__c) so the relationship to AAP data can be reconstructed. BambooHR Jobs support title, description, department, location, and employment status fields natively. Any Circa EEO-1 classification codes migrate to a BambooHR custom text field (eeoc_category__c) for record retention.

Circa Applicant records map directly to BambooHR Candidate records. Standard fields (name, email, phone, application stage, source) migrate via BambooHR API. Circa diversity sourcing tags (from Circa's intake workflow) migrate to BambooHR custom multi-select picklist fields (diversity_source_tags__c). Application date, current stage, and rejection reason transfer to BambooHR standard Candidate fields or custom fields as appropriate. Resume attachments migrate as file uploads linked to the Candidate record.

Circa Outreach Records are linked entities (partner name, outreach date, contact, response status, associated Job) stored separately from Applicants. BambooHR does not have a native Outreach Record object. We denormalize each Outreach Record into a BambooHR Candidate custom field group: one-to-many outreach entries are represented as a structured custom field set (outreach_date_1__c, outreach_partner_1__c, outreach_response_1__c, plus _2, _3 for additional outreach per candidate). We preserve Circa's linking ID (outreach_source_id__c) so the relationship is reconstructible if the customer adds a third-party outreach tracking tool.

Circa Community Partner Directory entries are external contacts who receive diversity job postings and outreach communications. BambooHR does not have a native Community Partner object. We extract the full contact record (organization name, contact name, email, diversity focus tags, outreach history count) and map it to a BambooHR Candidate custom field group (community_partner_org__c, community_partner_contact__c, diversity_focus_tags__c). For organizations with hundreds of Community Partners, we can alternatively create a dedicated BambooHR Candidate custom field type and import Community Partners as a separate candidate pool.

Circa's ESDS job board subscription configurations and automated posting history are internal system settings. BambooHR does not have an equivalent job board scraping or ESDS posting engine. We document the customer's active job board subscriptions from Circa during discovery and deliver a written job board rebuild guide listing the boards, posting URLs, and frequency. BambooHR's native job posting to 20+ boards serves as the replacement; ESDS posting to state unemployment sites requires manual reconfiguration by the customer's admin.

Circa AAP data (job group analysis, placement goals, contractor veteran/disability metrics) is derived from applicant flow logs and workforce composition snapshots. BambooHR does not generate AAP reports. We export AAP metadata as a structured CSV (job_group, placement_goal, current_placement, veteran_rate, disability_rate, snapshot_date) and deliver it to the customer as a reference document. The customer's compliance team rebuilds the AAP in their preferred tool (Circa, a standalone AAP vendor, or internal reporting). We preserve the AAP linkage to Circa job_id__c in the exported CSV so job group data can be tied back to migrated BambooHR Jobs.

Circa maintains a searchable resume repository with parsed candidate profiles and source attribution. We export resume metadata (parsed fields: name, email, phone, work history summary, education) and the resume file attachment (PDF, DOCX, or ATS-native format). Parsed metadata maps to standard BambooHR Candidate fields; source attribution maps to a custom field (resume_source__c). Resume files migrate as file attachments on the Candidate record. We note that BambooHR's resume parsing is limited compared to Circa's sourcing engine, and we recommend the customer evaluate BambooHR's resume parsing capabilities before cutover.

Circa Employer Profile settings (company description, diversity commitments, featured tags, branding used on job postings) are extracted as structured text fields. BambooHR's Company Information section holds organizational-level data. We map Circa employer profile text to BambooHR custom company information fields (diversity_statement__c, employer_brand_description__c, community_partner_tags__c). Employer branding assets (logos, imagery) are exported as files and delivered separately for the admin to upload into BambooHR.

Circa user accounts (name, role, module access level) map to BambooHR Employee records. We extract the user roster with role assignments and map Circa feature-tier access (Starter, Growth, Enterprise) to BambooHR employee permission groups. Circa users who were not applicants or employees (e.g., Community Partner contacts) are excluded from the user migration. BambooHR employee accounts are provisioned via API during migration; the customer assigns BambooHR access levels post-migration.

Circa custom fields exist on Jobs, Applicants, and Community Partners depending on the activated feature tier. We audit the full custom field schema from a full-feature Circa account during discovery, catalog field names, data types (text, picklist, date, number), and picklist value sets. Each custom field is mapped to a corresponding BambooHR custom field (Candidate custom fields for applicant-level fields, Job custom fields for requisition-level fields). Custom field data types must match: Circa picklists map to BambooHR multi-select or dropdown picklists; Circa text fields map to BambooHR short or long text fields. Circa custom fields gated by premium feature tiers that are not activated for the customer do not appear in exports and are excluded.