Migrate from Saleshiker to Twenty CRM

Saleshiker Leads map to Twenty Person records. The Lead status, source, owner, and custom properties migrate as Person fields and custom fields. Since Twenty does not have a separate Lead object by default, unqualified prospects land directly in the People table; if the customer needs a separate qualification queue, we configure a custom field (e.g., lead_status__c) or a filtered view rather than a separate object.

Saleshiker Contacts map to Twenty Person records. Phone, email, lifecycle stage, and owner assignment migrate directly. We preserve lifecycle stage values as a custom field (e.g., original_lifecycle_stage__c) since Twenty's standard Person object does not include a lifecycle enum. Contact-to-Organization linkage migrates via the Person's Company field, resolved after Organization records are inserted.

Saleshiker Organizations map to Twenty Company records. We insert Organizations first so that the Company.id is available for Contact.Person lookup resolution. Company name, domain, address, and industry fields map directly. If Saleshiker stores multiple contacts per organization, the relationship is preserved through the Person.Company linkage after Company insertion.

Saleshiker Deals map to Twenty Opportunity. Deal value, expected close date, owner, and stage migrate. Pipeline stages in Saleshiker map to Twenty Opportunity stage labels via a customer-confirmed mapping table at import time. We create the target Opportunity stages in Twenty's settings before migration using the Stage table, mapping each Saleshiker stage name to a matching Twenty stage.

Saleshiker's named pipeline structures (stages with ordering) map to Twenty's Stage records on the Opportunity object. If Saleshiker has multiple named pipelines, we configure multiple stage groups in Twenty and assign opportunities to the correct stage group during import via a pipeline_to_stage_group__c mapping field. The customer confirms stage mapping during the scoping call.

Saleshiker Quotes migrate to Twenty Opportunity records with line item records linked to the Opportunity. Quote headers (reference, date, total, status) map to Opportunity fields or custom fields; line items map to custom line item records if Twenty's OpportunityLineItem equivalent is in use, or are stored as custom Opportunity fields. PDF attachments on quotes migrate as file references requiring re-upload.

Saleshiker Invoices (AR/AP tracking) migrate to a Twenty custom object created at migration time. Invoice header data (number, date, total, payment status) migrates; payment reconciliation history that depends on Saleshiker's internal accounting state may not carry over cleanly if Twenty lacks equivalent AR/AP tracking. We discuss invoice handling scope with the customer during discovery.

Saleshiker Products (name, SKU, price, description) migrate to a Twenty custom object or standard Company field set depending on the customer's product catalog size. We create the target object via Twenty's Metadata API before migration and map SKUs as the dedupe key. Product attachments migrate as file references.

Saleshiker Tasks migrate to Twenty Task records. Title, due date, status, assignee, and related-to linkage preserve. Assignee resolution matches Saleshiker owner email to Twenty User email; unresolved owners go to a reconciliation queue for the customer's admin to provision before record insert proceeds.

Saleshiker Events migrate to Twenty Task records with a custom event_type__c field set to 'Meeting' or 'Event'. Start/end datetime, title, location, and assignee migrate. Recurrence patterns from Saleshiker are preserved as custom text fields if present; if the recurrence logic is complex, we document it for manual rebuild in Twenty. Attachments on events migrate as file references.

Saleshiker file attachments (stored per Lead, Contact, Organization, Deal) require a two-step process: we download files from Saleshiker's storage during the export phase, then re-upload them to Twenty's file storage linked to the target record. File metadata (filename, type, size, upload date) migrates as fields on the target record. Large attachment volumes may extend the migration timeline.

Saleshiker Workflow definitions reference internal triggers and action chains that have no portable equivalents in Twenty or any other CRM. We do not migrate Workflow definitions. We export a structured inventory of every active Workflow and Scheduler (trigger type, conditions, actions, affected records) so the customer's admin can plan rebuilding them in Twenty. This inventory is included in the migration deliverable package.