Migrate from Mitratech Circa to Crelate

Circa Jobs are the primary container holding requisition details, location data, EEO-1 category classifications, and OFCCP compliance flags. We map Circa Job records to Crelate Job records including status, posted date, and custom employer fields. Circa-specific OFCCP compliance flags (AAP-related classifications, ESDS posting requirements) transfer to Crelate custom fields since Crelate has no native OFCCP workflow; these flags are noted for the customer's compliance team to verify post-migration. The job's posted_date and closing_date migrate as standard Crelate date fields.

Circa Applicant records map to Crelate Candidates with full field preservation: name, contact, application stage, source attribution, and diversity sourcing tags. Circa captures diversity intake tags during the application workflow; we map these to Crelate custom multi-select fields or tags depending on the customer's preferred segmentation approach. Any Circa application status (applied, screened, interviewed, offered, hired, rejected) maps to the corresponding Crelate stage, with the original Circa stage preserved as a custom field for AAP flow-log reconstruction.

Circa stores Outreach Records as separate entities linked to Jobs by ID rather than embedded in the applicant record. Each outreach record holds partner name, outreach date, outreach type, and response status. We denormalize these into Crelate Activity records or Notes attached to the relevant Candidate or Contact, preserving the original Circa Job ID as a custom field so the relationship can be reconstructed in Crelate's association model. Multiple outreach records for the same candidate merge into a chronological activity timeline in Crelate.

Circa Community Partner Directory entries are external contacts who receive job postings and diversity outreach communications. Each partner record includes organization name, contact name, email, diversity focus tags, and outreach history. We map these to Crelate Contacts (for individual partner contacts) and Companies (for partner organizations), with diversity focus tags transferred to Crelate custom fields and the original Circa partner ID preserved for relationship continuity. This is one of the highest-value object mappings because Community Partner data represents years of DEIB relationship investment.

Circa's AAP data is derived from applicant flow logs and workforce composition snapshots. We export the AAP metrics—job group analysis, placement goals, contractor veteran and disability metrics—as structured data mapped to Crelate custom fields on the Job or as a separate custom object if Crelate's data model supports it. Circa's AAP plan generator does not migrate; we deliver a written AAP data inventory document listing the exported metrics, their source fields in Circa, and the recommended external reporting tool (AAP generator, HRIS, or compliance consultant) for rebuilding the plan. AAP data integrity is the most audit-sensitive object in this migration and receives dedicated reconciliation during cutover.

Circa posts jobs to external boards including state unemployment ESDS sites via automated scraping. Job board subscription configurations and posting history are tracked internally. We export the posting configuration data (board names, posting frequency, subscription status) as a written record for the customer's admin to reconfigure in Crelate's job distribution settings or in the relevant ESDS portal directly. Circa's ESDS scraping automation does not have a Crelate equivalent; this is documented as a rebuild item, not a gap.

Circa maintains a searchable resume repository tied to sourcing pipelines. Resume records include parsed candidate profiles and source attribution. We export resume metadata (parsed fields, source, date added) and the resume document attachments. In Crelate, resumes attach to the corresponding Candidate record via Crelate's Resume Toolbox feature, with source attribution preserved as a custom field.

Circa Employer Profile settings include company description, diversity commitments, featured tags, and branding used on job postings. We extract profile text, tag configurations, and logo/branding assets as a written specification and asset package. Crelate's branded job portal settings are reconfigured by the customer's admin using this package; we do not configure Crelate's employer branding as part of standard migration scope.

Circa user accounts include name, role, and access level to the specific feature modules the organization has licensed. We export the user roster (name, email, role, assigned modules) as a provisioning specification. Crelate User accounts are provisioned by the customer's admin using this specification; we do not create Crelate User records directly. Access-level mapping is documented as a step in the Crelate onboarding checklist.

Circa supports custom fields on Jobs, Applicants, and Community Partners depending on the feature tier. We catalog all active custom fields during discovery, verify them against an account with full feature access (to avoid silent drops from tier-gated exports), and map them to Crelate custom fields of equivalent data type. Field-level mapping is documented in a field mapping spreadsheet that the customer reviews during sandbox validation before production migration.

Circa's Diversity Badge system captures sourcing attribution across multiple diversity categories (veteran status, disability, race/ethnicity self-identification, etc.) attached to applicants. We map these to Crelate custom multi-select fields on Candidate and optionally to Crelate Tags for segmentation. The original Circa badge values are preserved as field values to maintain EEOC audit readiness. This mapping is critical for organizations with active AAP reporting obligations.

Circa tracks the full pipeline stage progression for each applicant including timestamps at each stage. We export the stage history as Activity records in Crelate (one Task per stage transition with the original timestamp and stage name) attached to the Candidate. This preserves the application timeline that feeds AAP applicant flow analysis, which federal contractors need for OFCCP audit defensibility.