Migrate your Kickserv data

Customer records include address, contact info, and a full job history. We map Customer fields 1:1 into the destination's equivalent contact or account object, preserving the customer-center portal link if applicable.

Individual contact records are attached to Customers and used for messaging and estimate approval workflows. We preserve the full contact name, email, phone, and role during migration.

Jobs are the core work-order object in Kickserv. They include status, assigned employee, location, scheduled time, expenses, photos, and notes. We map Job status and stage fields to the destination schema and flag any custom data fields for explicit value mapping.

Estimates contain line items, pricing, and signature-approval status. We preserve estimate content and approval records but note that the customer pipeline view for estimates is Kickserv-specific and may not translate directly to non-FSM destinations.

Invoices include line items, payment status, and online payment records via Stripe. We carry forward invoice amount, status, and payment history; online payment metadata is exported as metadata on the invoice record.

Employee records include name, role, contact info, and API token. We map Employees to Users or Technicians in the destination. Note that API tokens are tied to the employee's password and reset on password change.

Time Entries are clock-in/clock-out records linked to Jobs and Employees. We preserve start time, end time, duration, and any notes attached to the time record.

Charges represent individual line items on a Job or Invoice. We map Charges to the destination's equivalent line-item or invoice-detail object, preserving amount, description, and tax treatment.

Items are the product and service catalog used to populate estimate and invoice line items. We transfer the Items list including pricing and description as a reference dataset.

Notes attach to Customers, Jobs, and other objects. We preserve note content, author, and timestamp and associate each note with its parent object in the destination.

Signature records are created when a customer approves an estimate or confirms job completion. We store the signature image URL and metadata and link it to the associated Estimate or Job record in the destination.

Events represent scheduled appointments or dispatch calendar entries. We map Events to calendar or scheduling objects in the destination, preserving datetime, assigned employee, and job reference.

Custom fields can be added to Jobs, Customers, and the contact form. We identify all custom field definitions during scoping and map their values explicitly, noting that Kickserv's custom field schema is per-account and must be exported before migration.

Tags are used to categorize Customers, Jobs, and Estimates. We preserve tags as label or category fields in the destination system.