Migrate your Salesmate data

Core CRM object with a standard REST endpoint (module ID 1). Standard fields include name, email, phone, address, and lifecycle stage. Custom fields are supported and accessible via the API. We migrate all fields including custom ones and preserve duplicate-scoring metadata.

Module ID 5 in the Salesmate API. Companies are standalone records that can be linked to multiple Contacts. Standard fields and custom fields are both accessible via GET/POST/PUT endpoints. We preserve company-contact associations as foreign keys in the migration payload.

Module ID 4. Deals represent pipeline opportunities with stage, value, and owner assignment. Standard Salesmate pipelines map directly to destination CRM pipelines. Custom deal fields are migratable. We preserve deal-contact and deal-company associations.

Module ID 2. Tasks have due dates, owners, statuses, and associations to Contacts or Deals. Accessible via the standard REST API. We migrate tasks with their open/closed status and assignment ownership intact.

Module ID 3. Email history is stored per contact but full email body content may require a separate export path. Thread association metadata is available. We map email associations to the target CRM's activity or engagement objects, flagging any body-length limitations.

Module ID 6. Product records with pricing, description, and inventory fields are accessible via API. We migrate products and map them to the destination's product or item catalog, handling currency and unit-price formatting differences.

Shared inbox conversations are available from the Basic tier (1 inbox) scaling to 10 on Enterprise. The conversation threading model differs from most CRMs, and email message bodies may need field-level mapping to the target's activity or conversation schema.

Salesmate supports custom fields across Contacts, Deals, Tasks, Companies, and Products via the Customize > Create Form interface. Custom fields are accessible in API responses and importable via the API. We capture field type (text, dropdown, date, number) and apply appropriate value mapping at migration time.

Smart Flows use a credit-based model where unique contacts in a campaign consume credits. Automation definitions (triggers, actions, steps) are not fully exposed via the public API, so migration of Smart Flows requires re-creation in the destination using manual configuration. We document the workflow logic and export Smart Flow configurations as reference artifacts.

User records with role-based access control are migratable. Salesmate enforces per-user pricing, so owner assignment in Deals and Tasks is preserved as a foreign key to the user object. We flag any inactive or suspended users before migration.

File attachments associated with Contacts, Deals, and Companies are migratable via the API. Storage limits vary by plan (1 GB Basic, 5 GB Pro, 10 GB Business, 20 GB Enterprise). We flag files approaching or exceeding plan limits and coordinate storage provisioning before migration.

Tags are label-style metadata on Contacts and Companies. They are exported as string arrays via the API and mapped directly to equivalent tag/label fields in the destination CRM.

Email sequences are stored as automation templates tied to the Smart Flow engine. Sequence definitions with step logic and cadence are not a standalone API object. We export sequence membership (which contacts are enrolled in which sequences) and recreate sequence templates in the destination CRM.