Migrate from Alpha Hire to Crelate

Alpha Hire Candidate profiles (including screening data, vetting records, AI-generated match ratings, and application history) map to Crelate Person records. The Person object in Crelate handles both candidate and client-contact records; we set a candidate_flag custom field during import to distinguish talent pool records from client contacts. Historical timestamps (application_date, screening_date) migrate as custom fields on the Person record.

Alpha Hire Job Orders map to Crelate Job records with source attribution preserved (VMS-sourced vs manual). Job Order status (active, filled, cancelled) migrates as Crelate Job Status values. Any VMS-sourced orders with incomplete metadata (a known Alpha Hire gap) are flagged during import validation and queued for customer review before final load.

Alpha Hire Talent Partner records are distinct entities who assist throughout the hiring process and may have multiple associated clients. Crelate does not have a dedicated Talent Partner object; we map Talent Partners to Person records (with a talent_partner_flag custom field) and create Company association records linking each partner to their client companies. The many-to-many relationship resolves through Crelate's association object model during import.

Alpha Hire stores the client-to-talent-partner relationship as part of the Talent Partner record. We decompose this into Crelate Company records (one per client) and Person records (one per talent partner) with a linking association type field. If a talent partner works across multiple staffing clients, we create separate association records for each client relationship.

Alpha Hire structures hiring as a refined 3-step process. Crelate Pipelines with configurable Stages replace Alpha Hire's process templates. We map the 3-step process definition to a Crelate Pipeline with 3 Stages during import, using the stage names the customer has configured. Any proprietary stage names or custom stage logic is flagged for the admin to refine in Crelate's pipeline builder post-migration.

Alpha Hire's custom rule engine handles auto-assignment of job orders based on configurable logic. These rules are not exportable from Alpha Hire. We document every active rule during scoping by interviewing the customer's admin and reviewing any internal rule-documentation the team has maintained. We deliver a written inventory of each rule's trigger conditions, assignment logic, and recommended Crelate Workflow equivalent. The customer's admin rebuilds these in Crelate's workflow builder post-migration.

Alpha Hire subscription metadata (plan tier, billing model, start dates) migrates as a read-only record in Crelate's account notes or a custom Subscription_History__c object. We do not replicate billing relationships; Crelate subscription is re-established directly on Crelate's pricing page post-migration.

Alpha Hire integrates with ADP, QuickBooks, and Microsoft Outlook. We document these active integrations during scoping and flag which have Crelate equivalents or supported integrations. ADP and QuickBooks integrations do not migrate as active connections; the customer re-authenticates these in Crelate's integrations settings post-migration. Outlook sync is replaced by Crelate's email sync and activity capture.

Candidate attachments, offer letters, and onboarding documents stored within Alpha Hire migrate as Crelate Documents attached to the corresponding Person record. Export availability depends on Alpha Hire's data export capability (coordinated through their support team). If documents are inaccessible via export, we flag them in the scoping report and the customer manually transfers or re-uploads any critical attachments post-migration.

Alpha Hire captures job orders from VMS feeds, manual entry, and other recruiting channels. We preserve source attribution as a custom field on the Crelate Job record (source_type: VMS, Manual, Referral, etc.). VMS-sourced orders may have incomplete metadata in Alpha Hire; we validate required fields during import and queue incomplete records for customer review.

Alpha Hire Owner records map to Crelate User records. We resolve owners by email match during import. Any Alpha Hire Owner without a matching Crelate User is held in a reconciliation queue for the customer's admin to provision before record import completes.

Alpha Hire engagement records (calls, emails, meetings, tasks, notes) attached to Candidates and Job Orders migrate as Crelate Activity records linked to the corresponding Person and Job. Activity type, timestamp, duration, and disposition migrate directly. Note content migrates as Crelate note entries with the original timestamp preserved for timeline ordering.