Migrate from SupportFinity to Crelate

SupportFinity Job records map to Crelate Job records with title, description, department, location, and status preserved. The unlimited job postings on SupportFinity Growth map to Crelate's no-per-job-limit structure on all paid tiers. Job status (Open, Closed, Draft, On Hold) maps to Crelate's Job status field. Job-specific screening questions from SupportFinity migrate to Crelate Activity Forms or Application Forms scoped to the Job.

SupportFinity Candidate profiles map to Crelate Contact records. We preserve name, email, phone, resume/CV, work history, education, and custom profile fields as typed Crelate custom fields. The 2.4 billion-profile talent cloud enrichment is read-only enrichment on SupportFinity and does not generate a transferable data asset; candidate records created from talent cloud matches export as standard Contact records with source attribution preserved in a custom field.

SupportFinity Application records (linking Candidate to Job with timestamps, source channel, and pipeline stage) map to Crelate Opportunity records. The Opportunity's Job reference is preserved via a custom lookup field. Application status (Applied, Screening, Interview, Offer, Hired, Rejected, Withdrawn) maps to Crelate Opportunity Stage with a configuration pass to align stage names and counts to the destination's pipeline structure.

SupportFinity DISC+ assessment scores (Dominance, Influence, Steadiness, Conscientiousness subscores) migrate as custom numeric fields on the Crelate Contact record. We map each subscale to a dedicated Crelate custom field. For multi-question DISC+ responses, we use a Crelate Activity Form with Field Mappings to capture detailed response data against the Contact.

Atom-generated custom assessment rubrics and scores are proprietary metadata in SupportFinity. We export raw scores and signal labels as custom numeric and text fields on Crelate Contact. The rubric definition structure (question weights, evaluation criteria) is domain-specific and does not map directly to Crelate's form builder; we document the rubric as a written specification for the customer to rebuild as a Crelate Activity Form post-migration.

SupportFinity Interview records (scheduled time, interviewer assignment, notes) map to Crelate Activity records linked to the Contact and the related Opportunity. Interviewer assignments resolve by email against Crelate User records. Interview stage (Phone Screen, Technical, Panel, Final) migrates as a custom picklist field on the Activity record.

Sia interview recordings are binary attachments in SupportFinity and do not export via standard API. We perform a separate file extraction pass using authenticated session access to download each recording by filename and interview record ID. Recordings are stored in a customer-provided cloud storage location and linked back to the corresponding Crelate Activity record via a custom URL field. The customer manually links recordings in Crelate or uses a file-storage integration. This pass runs after primary structured-data migration completes.

SupportFinity's configurable pipeline stages (Screening, Interview, Offer, Hired, Rejected, etc.) are tenant-specific. We map SupportFinity stage IDs and labels to Crelate Opportunity Stage values, creating a Crelate Pipeline Record Type that scopes the relevant stages to the migrated Jobs. Stage sequence order and probability percentages are preserved in the stage configuration.

SupportFinity User accounts (Recruiter, Hiring Manager, Admin roles) map to Crelate User records. We resolve by email match. SupportFinity Growth's 3-seat cap means migration scoping must identify all active and inactive users to ensure the Crelate Business plan's 5-seat minimum covers the full team post-migration. Any SupportFinity user without a Crelate account goes to a reconciliation queue for provisioning before record import.

Free-text notes attached to Candidates or Applications in SupportFinity migrate as Crelate Activity Notes linked to the corresponding Contact and Opportunity. Timestamps and author attribution (via email-to-User resolution) are preserved. Long-form notes with formatting map to Crelate's rich-text note format where supported.

Candidate email and SMS conversations via SupportFinity's unlimited mailboxes map to Crelate Activity records (email or call type) on the Contact. Thread structure is preserved as a chronological series of Activity records. Attachment handling requires a separate pass for binary files linked to conversation threads.

SupportFinity job-specific screening questions and candidate answers are custom fields at the application level. We map question text and answer values to Crelate Application Form fields scoped to the Job. Skip logic and conditional branching in SupportFinity's screening flows do not migrate as automation; we document the conditional logic as a written specification for the customer to rebuild as a Crelate Activity Form with conditional visibility.

AI-generated talent signals and ranking scores are proprietary SupportFinity metadata. We export raw scores and signal labels as custom numeric and text fields on the Crelate Contact record. These serve as informational fields in Crelate; the signal generation algorithm does not transfer.

SupportFinity Offer records (salary, start date, status) map to Crelate Opportunity records with custom fields for offer amount, start date, offer status (Pending, Accepted, Declined, Countered), and any offer notes. Status mapping aligns to Crelate Opportunity stage transitions.

The SupportFinity credits ledger (purchased, consumed, balance) is specific to the credits billing model and has no Crelate equivalent. We export consumption records as a CSV reference file for the customer's financial records but do not load into Crelate as operational data. Customers should review their SupportFinity credits balance before initiating bulk export to avoid mid-migration bill shock if AI features are still active on the source account.