Migrate your Saleshiker data

Leads are first-class objects in Saleshiker with full CRUD via the API. We migrate lead records including status, source, owner assignment, and custom properties. Phone numbers are preserved exactly as stored.

Contacts hold individual records with name, email, phone, lifecycle stage, and owner. We preserve all standard fields and map lifecycle stage values to the destination's equivalent enum.

Organizations represent company accounts linked to multiple Contacts and Deals. We migrate the org record and preserve the contact-to-org association during import into the destination.

Deals carry pipeline stage, value, expected close date, and owner. Pipeline stages in Saleshiker map to the destination pipeline's stage labels via a customer-confirmed mapping table at import time.

Saleshiker's pipeline structure includes named stages with ordering. Where the destination has a different pipeline model, we create a target pipeline and map each Saleshiker stage to the closest equivalent.

Quotes include line items, pricing, and status. We migrate quote headers and line items; if the destination uses a different quote or opportunity object, we split the header into the target record and store line items as a custom field.

Invoice records include payment status, totals, and AR/AP flags. We preserve invoice header data and line items; payment history requires the destination to support AR tracking or we map to a custom object.

Products store name, SKU, price, and description. We migrate the product catalog and map SKUs to the destination's product or item records.

Tasks include title, due date, status, and assignment. We migrate all task fields including assignee and related-to linkage.

Events carry title, start/end datetime, type, and assignee. We preserve the full event record including recurrence patterns if applicable.

Workflow definitions in Saleshiker reference internal triggers and action chains that do not have portable equivalents in other CRMs. We do not migrate workflow definitions; we document which workflows exist so the customer can rebuild them post-migration.

Email campaign records include template, send date, and open/click statistics. We migrate campaign metadata and basic stats; detailed engagement logs require destination-specific handling.

Broadcast records exist in Saleshiker but are governed by Meta's WhatsApp Business API conversation limits and template approval states. We do not migrate broadcast history.

Attachments are stored per-record (Lead, Contact, Organization, Deal). We migrate file references and metadata; the actual files are downloaded from Saleshiker's storage and re-uploaded to the destination.