Migrate from Asure to Crelate

Asure Employee records map to Crelate Candidate records. We map first_name, last_name, email, phone, mobile_phone, address fields (street, city, state, zip), department, job_title, employment_status, hire_date, and termination_date. The Asure employee_id becomes the Crelate legacy_id field for dedupe and cross-reference. Active employees migrate with Candidate status set to Active; terminated employees migrate with a termination date and a Candidate status of Inactive or Archived per Crelate's status options.

Asure department assignments map to Crelate Candidate custom fields or tags. Crelate does not have a native Department object; we create a custom picklist or multi-select field on Candidate to hold the Asure department value, preserving the organizational context for reporting and filtering in Crelate.

Asure job_title maps to Crelate Candidate.title. This field appears in the candidate record header and is searchable. We preserve the Asure job title exactly; no normalization is applied because titles vary by organization.

Asure compensation rate (hourly, salary, or contractor rate) maps to a Crelate Candidate custom field, current_salary or desired_salary, depending on how the customer intends to use the field post-migration. Crelate does not have a mandatory pay-rate field; we configure the field type (currency) and label based on customer requirements. Note that Crelate salary fields are used for placement billing context, not payroll processing.

Asure employment_status (Active, On Leave, Terminated, etc.) maps to Crelate Candidate status values. Active maps to an active candidate status; terminated maps to inactive or archived. The mapping table is defined during scoping because status labels differ between Asure tiers.

Asure offer letters and W-4 forms stored in the document repository migrate as Crelate Candidate attachments via the Crelate Resume Toolbox or standard file attachment. We extract the file from Asure's document store, map it to the corresponding Candidate record, and tag it with the document type. Crelate's Resume Toolbox processes attached documents for parsing if the customer enables that feature.

Asure emergency contact information (name, relationship, phone) has no native Crelate Candidate field. We create custom text fields on the Candidate object to capture this data during migration. The customer must decide whether to populate these fields as part of the candidate record or exclude emergency contact data entirely given Crelate's recruiting context.

Pending or recent address changes and direct deposit preferences from the Asure employee self-service portal have no Crelate equivalent. We extract these as a separate data file and deliver it alongside the migration, flagged for manual review. Direct deposit data is sensitive and should be handled per the customer's data security policy before migration.

Historical payroll registers (earnings, deductions, taxes, net pay per pay period) have no schema in Crelate. Crelate is an ATS and recruiting CRM, not a payroll platform. We exclude payroll registers from the migration scope and document this in the scope letter. If the customer requires payroll history visibility in the future, a dedicated payroll reporting integration is the recommended path.

PTO accrual ledgers and leave balances cannot migrate to Crelate because Crelate has no accrual or time-off tracking schema. We extract the balance snapshot as a static report at cutover and deliver it as a CSV alongside the migration. The customer's HR team uses this for continuity if they run both systems in parallel during a transition period.

Health, dental, vision, and voluntary benefit elections tied to plan years do not migrate to Crelate. Crelate has no benefits administration module. We extract a benefits enrollment summary as a static report. Mid-year migration requires special handling: enrollments are isolated to the closed plan year, and any mid-year qualifying event changes are handled separately after cutover.

Federal, state, and local tax withholding setups have no Crelate equivalent. We exclude tax configurations from migration scope and deliver a written inventory of active tax jurisdictions per employee as a reference file. This inventory is useful if the customer later selects a payroll platform to replace Asure.