Migrate your Workstream data

The central worker record in Workstream. We map standard fields (name, contact, hire date, job title, department, location assignment) and preserve the lifecycle status (Active, Onboarding, Offboarded) as a discrete field. Offboarded employee records are included in exports unless explicitly scoped out.

Job openings linked to a specific location. Position records include title, department, pay rate/range, schedule type, and job description. We map these to roles or job titles in the destination system and preserve location linkage.

Reusable job definitions that feed multiple Position instances. We flatten Position Templates into their instantiated Position records during export, preserving the template origin as a tag or custom property in the destination system.

Candidate submissions tied to a specific Position. Application records include applicant contact info, answers to screening questions, communication history, and status in the hiring pipeline. We map status stages and preserve timestamps.

Workstream supports custom fields on team members in text, date, number, and dropdown formats scoped by role, location, or department. We extract all active custom fields and map them to custom properties in the destination, flagging sensitive fields (driver license, certifications) for PII handling.

Workstream's primary organizational unit. Each location can have its own configuration, manager, and address. We preserve location names and addresses as an organizational unit or department in the destination system.

Role definitions scoped to locations. We map which roles exist and how employees are assigned to them, preserving the location-role combination as it determines pay and schedule authority.

Workstream stores document packets (tax forms, signed onboarding documents, IDs) as binary attachments. We do not migrate binary document files. Employee metadata (document submission status, which forms were completed) is preserved as a custom field flag.

Workstream integrates with third-party payroll providers rather than running payroll itself. Pay rates, pay schedules, and payroll sync status are available as employee properties. We map pay rate fields but leave payroll processing to the connected provider at the destination.

Integration connections (ADP, Square, Toast, QuickBooks) are stored as OAuth tokens and configuration metadata. These cannot be transferred between tenants. We document which integrations were active so they can be reconfigured in the destination environment.

Workstream uses configurable pipeline stages for the hiring process (e.g., Applied, Screening, Interview, Offer, Hired). We extract the full pipeline definition and map stage names and order to the destination ATS or CRM stages.