Migrate your Crelate data

Contacts is Crelate's primary candidate and client record object. Standard fields include name, email, phone, and address. Custom fields are supported up to a 20-per-entity cap. We migrate Contacts with all custom property values and preserve linked Company and Opportunity associations via Crelate's lookup fields (Id, FirstName, LastName structure).

Companies represent client organizations and are a required dependency for many other objects. We import Companies first to ensure downstream Contacts and Opportunities can reference them correctly. Lookup fields to billing and primary contacts are preserved during migration.

Jobs represent job orders or requisitions. They link to the hiring Company and can have multiple associated Candidates and Placements. We preserve the Job-to-Company linkage and map pipeline stages to the destination's job workflow stages.

Opportunities track revenue-generating business development activity in Crelate's CRM layer. They have a separate custom field allowance from Contacts and Companies. We map Opportunity stages and monetary fields directly to the destination's equivalent CRM object.

Placements record placed candidates and capture salary, pay rate, start date, and fee percentage. They are derived from an existing Job and Candidate relationship. We migrate Placements only after confirming the parent Job and Contact records are present in the destination to avoid orphaned records.

Crelate supports custom fields on Contacts, Companies, and Opportunities with a documented cap of 20 per entity. We audit the customer's existing custom field inventory during scoping and flag any that exceed the cap or have naming conflicts in the destination. Fields are migrated as Short/Long Answer, Picklist, Date, or Numeric based on Crelate's field type metadata.

Activities track recruiter tasks, calls, emails, and notes linked to Contacts and Companies. The Activities object is gated behind specific pricing tiers in Crelate. We verify the source plan includes Activity data before including it and map activity types to the destination's equivalent task or engagement object.

Sequences represent automated outreach workflows with templated tasks, emails, and text steps. Crelate stores Sequence definitions and enrollment state separately from contact records. We do not migrate Sequences as they encode platform-specific automation logic that cannot be reliably reproduced in other CRMs.

Documents attached to Contacts, Companies, Jobs, or Placements are stored in Crelate's document management layer. We export documents via the API or bulk export tool and re-upload them to the destination with linkage to the matching parent record. Document metadata (file type, upload date, attached-by user) is preserved where supported.

Tags in Crelate are label-based categorizations applied to Contacts, Companies, and Opportunities. We extract tags during export and apply them as tags or custom properties in the destination CRM depending on that platform's tagging model.

Crelate Users represent team members who own records. We map User records to Owner or Assignee fields in the destination, either by matching on email address or by creating new user accounts and establishing the mapping table. Inactive or archived users require explicit handling decisions.

Crelate supports customizable pipeline stages for Opportunities and Jobs. Stage names and order are preserved in migration, but stage-specific automation (e.g., triggers that fire when a record moves to a stage) does not migrate and must be rebuilt in the destination.

Crelate stores historical import logs that record when and by whom data was loaded. This metadata is not useful in a new system and is excluded from migration scope.