Migrate from Betterteam to Crelate

Betterteam Jobs map directly to Crelate Jobs. We transfer title, description, requirements, location, department, status (active/closed/paused), and posting date. Betterteam bills by active-job count, so we flag the count during scoping to confirm the destination Crelate plan accommodates the customer's hiring volume. Archived jobs migrate with their original close date and status so historical reporting is preserved.

Betterteam stores one candidate record per application, meaning the same person appears as separate records if they applied to two jobs. We deduplicate candidates by email address (case-insensitive, normalized for whitespace), merge their application history into a single Crelate Contact profile, and preserve the application count as a custom field bt_application_count__c. Each merged application's original submission date, job reference, and status migrate as child Application records on the unified Contact.

Betterteam Application records map to Crelate Application records linked to the unified Contact. The application date, source job board, status (new, reviewed, liked, declined), and custom notes transfer. Application status values (new, reviewed, liked, declined) map to Crelate's stage pipeline values, and we document the mapping during scoping so the customer's admin can configure stage names to match their original process.

Betterteam's 5-star rating on candidates maps to Crelate's Rating field on Contact. We map the numeric scale consistently. If a candidate was rated across multiple applications, we preserve the most recent rating and note the rating history in a custom field bt_rating_history__c as a text summary.

Betterteam reviewer notes migrate as Crelate Note records linked to the unified Contact. Author attribution and original timestamps are preserved. Notes are imported in chronological order by date so the recruiting team's evaluation history reads correctly in Crelate's timeline view.

Resume and cover letter files attached to Betterteam applications are downloaded, deduplicated by filename, and re-uploaded to the corresponding Crelate Contact record. File naming conventions differ between platforms; we standardize to Name_Resume.pdf and Name_CoverLetter.pdf. Binary attachments exceeding 10 MB are flagged for the customer to handle manually due to Crelate's default file size limits on Business plans.

Betterteam generates hosted careers pages as rendered HTML rather than exposing structured job-listing data. The careers page URL and page title are recorded, but the page content is HTML markup that cannot be remapped to a structured Crelate careers page without manual rebuilding. We flag this as a post-migration task and advise the customer to configure Crelate's Branded Job Portal after migration.

Betterteam's job-board posting integrations (Indeed, ZipRecruiter, LinkedIn, and 100+ others) are third-party server-side connections that are not exposed in exportable data. The job-to-board mapping does not transfer. After migration, the customer must re-establish job distribution in Crelate's integrations or through a third-party job-posting aggregator. We document the list of active board connections from the Betterteam export for reference during rebuild.

Betterteam stores employer/company information linked to jobs. These map to Crelate Company records. We transfer company name, website, industry, size, and location fields. Company records are loaded before Contact records so that the Company-Contact lookup relationship is satisfied at the moment of Contact insert.

Betterteam users referenced on candidate notes and ratings are resolved by email match against Crelate Users. Any Betterteam Owner without a matching Crelate User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Inactive owner records are preserved in a custom field for audit.

Betterteam allows custom fields on applications. We map these to Crelate custom fields on the Application object. Crelate's field-mapping feature (which copies form answers to Contact, Company, or Opportunity columns) is noted for the customer's admin to configure post-migration if they want application-answers to auto-populate related fields.

Betterteam records candidate engagement events (email, note added, status change) in the application history. These migrate as Activity records on the unified Crelate Contact. Note-type engagements map to Crelate Notes; status-change events map to Task records. We preserve the original timestamp and actor for each event so the timeline reflects the full recruiting interaction history.