Migrate your Spotler Mail+ data

Contacts are the primary object accessible via the REST API using GET/POST/PUT/DELETE on element URIs. Standard fields map cleanly. Custom fields require field-type mapping (text, numeric, list, date, permission) as defined in Spotler's database field documentation.

Mailings are API-accessible objects and can be created and sent via the API. Subject lines, sender names, content, and send dates are preserved. Automated campaign logic does not transfer as executable rules and must be reconstructed at the destination.

Segmentations are built from selections, exclusions, refinements, behavioral data, tags, and scores. The segmentation rules themselves are not exported; only the resulting contact sets can be extracted. We recommend exporting static snapshots of segmented lists alongside live segmentation definitions for manual rebuild.

Tags are contact-level attributes accessible via the API. They map 1:1 to standard CRM label/tag fields in most destination platforms.

Lead scoring values are stored as contact properties. Numeric scores map directly to number fields in the destination CRM.

Spotler Mail+ supports text, numeric, currency, list, date of birth, date, and permission field types. Import column names must link to database field names exactly. List fields and permission fields require explicit value mapping during migration.

Form submissions are recorded as request objects linked to contacts. Survey results can be exported to Excel per the help center documentation. We extract form submissions as related records rather than standalone objects in most destinations.

Email templates are stored assets. The drag-and-drop editor layout does not export as a portable format. We extract template content, images, and styles as HTML/CSS assets for manual reassembly in the destination platform.

Landing pages built in Spotler Mail+ are platform-native assets. We export the content and structure where accessible, but interactive elements, forms embedded on pages, and styling require reassembly at the destination.

Media assets (images, PDFs, Word, Excel, PowerPoint, ICS files) can be archived and managed in the platform. We export binary assets from the media library. Folder structure is preserved where the API exposes it.

Opens, clicks, delivery stats, heatmaps, and conversion attribution are available via the analytics dashboard and can be exported as CSV. Mailing interaction history is anonymized after 24 months per Spotler's data retention policy, so historical reports older than 24 months will be incomplete.

User accounts with predefined roles and access levels are accessible. We extract user names, emails, and role assignments. Role definitions map to standard user permission schemas in destination platforms.

Automated campaign logic (triggers, drip sequences, behavioral actions) is platform-native and cannot be exported as executable rules. We document the automation structure to support manual rebuild at the destination.