Migrate your Spotler CRM data

Contacts are the primary record in Spotler CRM. Each Contact links to a Company, stores standard fields (name, email, phone, address) and custom properties. We map Contacts 1:1 by email address as the unique key and preserve all standard fields. Custom properties transfer as-is and are recreated as custom fields in the destination.

Companies store account-level data including industry, size, and address. The Company-to-Contact relationship is preserved via the company_id foreign key. We export Company records separately and re-link them to their Contact set post-import using the stored relationship identifier.

Opportunities carry pipeline stage, deal value, expected close date, and an assigned Owner. Pipeline stages vary by CRM configuration, so we collect the source stage names during scoping and map them to the destination pipeline structure. Owner assignment requires a user lookup table to match by email.

Activities include tasks, calls, meetings, and notes linked to Contacts or Companies. We export activity type, date, duration, description, and the related record ID. Note that Spotler stores activity history as individual records—high-volume activity sets require chunked API reads to avoid timeouts.

Spotler CRM allows unlimited custom fields on Contacts, Companies, and Opportunities. Dropdown lists are defined separately in settings and referenced by field. We export the field definitions alongside the data and recreate the field structure in the destination before importing record values. Dropdown values require explicit mapping when destination options differ.

Quotations are available on Professional and Enterprise plans. Each quotation carries line items, pricing, and status. We export quotation records and line items as a separate table, then reconstruct them in the destination using product/item lookups where available.

Case management with SLA assignment is available on Professional and Enterprise tiers. Cases link to Contacts and carry priority, status, and assignment data. We export cases as individual records and map status values explicitly, noting that SLA rules cannot be transferred and must be reconfigured in the destination.

Documents attach to Contacts, Companies, and Opportunities. Storage limits vary by plan (100MB Free, 1GB Starter, 5GB Professional). We export document metadata (filename, size, linked record, upload date) and retrieve the actual file via API. Large document sets require staged downloads to respect rate limits.

Workflows define automation logic—triggers, conditions, and actions. We do not migrate workflow definitions because they reference field IDs and object logic specific to Spotler CRM. Instead, we document the workflow sequence and recommend rebuilding equivalent automations in the destination platform using the recorded logic as a specification.

Users store name, email, role, and group membership. Permission levels (Admin, Standard, Read-only) vary by plan tier. We export the user table and map roles to the closest equivalent in the destination. Active vs. inactive status is preserved to avoid licensing waste post-migration.

Spotler uses both static lists and dynamic segments for segmentation. Tags apply to individual records. We export tag names per contact and list membership records separately, then recreate them as tags or dynamic lists in the destination depending on the target platform's structure.

Reports and dashboard widgets store query logic and visualisation configuration tied to Spotler's internal schema. We do not migrate report definitions. We export the underlying data so reports can be rebuilt from scratch in the destination platform.