Migrate from Talent Connects to Crelate

Talent Connects Jobs map directly to Crelate Jobs with title, description, status, and pipeline configuration preserved. The export contains Job ID, title, description, status (active/archived), and pipeline stage names. We map Talent Connects' pipeline stages to Crelate Job Status values during transformation. Note that Talent Connects Growth tier caps at 10 active Jobs — we surface the active job count during scoping and flag whether a plan upgrade or job archival is needed before migration begins.

Talent Connects Candidates map to Crelate Contacts with name, email, phone, and resume attachment preserved. Resume files export from Talent Connects as separate file downloads; we attach them to the corresponding Contact record in Crelate during import. Application timestamps and stage history migrate as Crelate Activity records with a custom activity type 'Application Status Change'. The candidate's current status in Talent Connects maps to a Crelate Contact custom field tc_current_status__c for audit.

Talent Connects Talent Pool records (Enterprise-only at $399/month) migrate as Crelate Contacts with a custom field tc_talent_pool__c set to true. The passive sourcing metadata (date added to pool, source channel) migrates as custom fields on the Contact. The Talent Pool workflow — a discrete passive sourcing interface in Talent Connects — does not transfer; the pool records themselves land as standard Contact records in Crelate's database. Teams must recreate any Talent Pool-based outreach sequences in Crelate manually.

Talent Connects Interview records (date, attendees, outcome notes) stored as activity records migrate to Crelate Activity entries linked to the Contact record. Interview outcome notes migrate as Crelate Activity detail text. Talent Connects' built-in video interview platform links (if any) do not transfer as they are third-party session URLs external to the Talent Connects data model. The customer's admin rebuilds calendar sync and video interview links in Crelate post-migration.

Talent Connects User accounts (email, name, role assignment) map to Crelate Users. Enterprise tier multi-level role permissions in Talent Connects require manual review in Crelate because Crelate's permission model uses a different structure (profile and permission set assignments vs Talent Connects' role-based access). We map the functional role name to a Crelate User custom field tc_original_role__c for reference, but permission set assignment requires the customer's admin to configure in Crelate post-migration.

Talent Connects bulk email campaigns (templates, send history, engagement tracking) map to Crelate as Email Activity records linked to the respective Contact records. Email template bodies and subject lines migrate as Crelate Activity notes. Engagement tracking data (open rates, click rates) does not transfer as structured metrics — these are Talent Connects-internal analytics that are not exposed for export. We flag which Contacts had email activity so the customer's admin can identify historically engaged candidates.

Talent Connects' optional AI-Assistant add-on ($49/month on Growth) provides AI-generated job descriptions and candidate ranking scores. These AI-derived scores do not persist as structured exportable fields — they are computed on-demand and not stored in candidate records. We do not migrate AI scores. We flag which Candidates were AI-ranked in a custom Crelate Contact field tc_ai_ranked__c as a reference indicator, but the ranking values themselves are not available for transfer.

Talent Connects generates hosted career pages from Job data. The career page template, branding settings, URL structure, and styling do not export as structured data — they are system-generated and tied to Talent Connects' hosting environment. We do not migrate career page configuration. We deliver a written inventory of each active career page URL, job listings on each page, and branding theme settings (logo, colors, copy) for the customer's admin to rebuild manually in Crelate's Branded Job Portal at configuration time.

Talent Connects analytics dashboards (funnel metrics, time-to-hire, source performance) are rendered from internal data stores and do not export as raw datasets. We do not attempt to migrate analytics. We instruct the customer to export screenshots of all dashboards before migration day if historical funnel reporting must be preserved. Post-migration, the customer rebuilds reports using Crelate's Advanced Reports and Analytics on Business Plus or Enterprise tier.

Candidate application history — every Job a Candidate applied to, the application date, and the status at time of application — migrates as Crelate Activity records linked to the Contact. The activity type is set to 'Application' with the Job name and status as detail fields. This preserves the candidate's pipeline journey across multiple applications even when they applied to several roles.

Talent Connects pipeline stage names and probabilities map to Crelate Job Status values. We design the Crelate Job Status configuration during the schema design phase, matching stage names from Talent Connects to equivalent statuses in Crelate. Stage probability percentages transfer as Crelate Job custom fields if the customer tracks placement probability by stage.

Talent Connects custom application form questions (beyond standard name/email/phone) are stored as form configuration data, not as candidate record fields. We extract the question text and answer format from Talent Connects' form builder and deliver a written inventory of every custom application question for the customer's admin to recreate in Crelate's Application Forms builder post-migration. The answers to those questions that exist in candidate records transfer as Crelate custom field values.