Migrate from Sellsy to Mailchimp

Sellsy conflates Individuals and Companies into a single Contact model with a 'type' discriminator. We split by the type attribute during pre-flight: Individuals migrate as Mailchimp Members within the target Audience. Email address is the dedupe key. First name, last name, phone, address, and custom field values transfer to Mailchimp merge fields, subject to the 255-character merge field limit — text exceeding this threshold is truncated and flagged in the pre-migration report.

Sellsy Corporations (companies) are not a native Mailchimp object type. We map Corporation records as Members in the target Audience and populate Mailchimp merge fields with company data (company name, SIRENE number, industry classification) rather than creating separate records. If the customer requires a company-level view, Mailchimp's Groups or Tags serve as the organizational layer.

Sellsy Opportunities have no direct Mailchimp equivalent. Mailchimp is an email marketing platform, not a CRM or pipeline management tool. We extract Opportunities as a structured CSV export (Opportunity name, stage, amount, owner, expected close date, linked contact email) for the customer's admin to review or archive outside Mailchimp. If the customer requires pipeline visibility in Mailchimp, Tags on Members can serve as a lightweight stage proxy, but this is not a native mapping.

If the customer uses Sellsy's product catalog for e-commerce, we map Products to Mailchimp Product records within the Mailchimp e-commerce integration (available on Standard and Premium plans). Product name, SKU, price, and description transfer directly. Note that Mailchimp's e-commerce model is primarily for connected storefronts (Shopify, WooCommerce, BigCommerce); standalone product catalog sync requires a specific configuration.

SmartTags in Sellsy function as labels applied to Invoices, Orders, and Credit Notes rather than a relational data object. Since financial documents do not migrate to Mailchimp, SmartTags that were applied only to transactional documents are documented but not transferred. Any contact-level tags applied in Sellsy map to Mailchimp Tags on the corresponding Member record.

Sellsy Staff records represent internal users and carry role and privilege information. Mailchimp uses a simple user model (Admin, Manager, Author, Viewer) that does not replicate Sellsy's privilege hierarchy. We document Staff names and roles as a CSV for the customer's admin to provision Mailchimp user accounts manually post-migration. Active Mailchimp users are the billable seats.

Sellsy custom fields on Contacts and Corporations map to Mailchimp merge fields. We inspect the custom field schema via Sellsy's /custom-fields endpoints, map field types to Mailchimp's supported merge field types (text, number, date, address, phone, email, dropdown), and flag any text fields exceeding 255 characters for truncation before import.

Sellsy Invoices, Orders, and Credit Notes are financial documents with no Mailchimp equivalent. We export these as structured CSV files ordered by document number and date, preserving line items, discounts, taxes, SmartTags, and linked contact email for reconciliation. The customer's admin retains these records in Sellsy (read-only archive) or transfers them to a dedicated accounting platform. This is a documentation and export deliverable, not a Mailchimp import.