Migrate from Sellsy to HighLevel

Sellsy conflates Individuals and Companies into a single Contact model with a type discriminator (type: 'individual' or 'corporation'). We split by the type attribute during CSV or API extraction, routing Individuals to the GoHighLevel Contact object and Corporations to the Account object. The Sellsy contact id becomes a custom field sellsy_id__c for dedupe and cross-reference. Primary address, phone, email, and custom fields on Individuals migrate directly.

Sellsy Corporation records extract from the combined Contact export by type discriminator and map to GoHighLevel Account. The Sellsy Corporation's business identifier, SIRENE number (if present), address, and revenue range migrate to equivalent Account fields or custom fields. Account is created before any Individual Contact import so that the Account-Contact lookup relationship is satisfied at the moment of Individual insert.

Sellsy Opportunities map directly to GoHighLevel Opportunities. Pipeline and stage assignments from Sellsy map to GoHighLevel pipeline stages, with the stage probability percentages migrated and rounded to GoHighLevel's supported values. OwnerId resolves by email match against GoHighLevel Users. Closed-won and closed-lost amounts and dates migrate as standard Opportunity fields.

Sellsy Invoices have no direct GoHighLevel equivalent. We create a Custom Object named 'Invoice' with custom fields for invoice number (sellsy_invoice_id__c), issue date, due date, subtotal, tax, total amount, status (draft, sent, paid, overdue), and line items (as a JSON text field or as child Custom Object records depending on reporting needs). SmartTags from Sellsy map to GoHighLevel Tags on the Invoice Custom Object. Line items, discounts, and taxes preserve as separate custom fields or as a serialised JSON body.

Sellsy Orders track commercial transactions distinct from invoices and map to a Custom Object named 'Order' with fields mirroring the Invoice schema. Order status, product-line attachments, and SmartTags migrate. We create Order as a separate Custom Object from Invoice to maintain the Sellsy distinction between sales orders and billing invoices in the destination system.

Credit Notes map to a Custom Object named 'Credit Note' with a lookup to the related Invoice Custom Object (via sellsy_invoice_id__c cross-reference). Amount, reason, and SmartTags migrate. GoHighLevel's 10 Custom Object per location limit applies; if the customer already uses multiple Custom Objects, we prioritise Invoice and Order over Credit Note, collapsing Credit Notes into Invoice notes or a text field.

Sellsy Staff records represent users and carry role and privilege information. We map Staff to GoHighLevel Users by email match. Sellsy's privilege model (admin, manager, user roles) maps to GoHighLevel's team permission structure. Staff records without a matching GoHighLevel User email go to a reconciliation queue for the customer's admin to provision before record import resumes.

Sellsy Tasks map to GoHighLevel Tasks with subject, description, due date, status, priority, and assignee preserved. Task assignment migrates by resolving the Sellsy owner_id to the GoHighLevel User via the Staff-to-User mapping. Completed task timestamps and completion status transfer as standard GoHighLevel Task fields.

Sellsy Activities include appointments, calls, and logged interactions tracked against Contacts and Opportunities. These map to GoHighLevel Activity records linked to the respective Contact and Opportunity. Call duration, disposition, and meeting location preserve as custom fields on the Activity record. Activity timestamps migrate to preserve the chronological timeline.

Sellsy Product catalog entries map to GoHighLevel Products with name, description, unit price, and SKU (sellsy_product_id__c). Pricing rules from Sellsy's product matrix migrate as pricing tiers on the GoHighLevel Product. Product availability and inventory status map to GoHighLevel Product active/inactive flags.

Sellsy SmartTags are labels applied to Invoices, Orders, and Credit Notes, not a relational object. We map SmartTags to GoHighLevel Tags applied to the respective Custom Object record (Invoice, Order, Credit Note). The tag name and colour metadata preserve where supported. Tags are applied after the parent Custom Object record is created, requiring a two-phase import: records first, then tag assignment.

Sellsy supports custom fields on Invoices, Contacts, and Corporations via dedicated GET+PUT /custom-fields endpoints. We inspect the custom field schema per object during scoping, map field types to their GoHighLevel Custom Field equivalents (text, number, date, dropdown, checkbox), and pre-create the destination fields before migration. Fields on Invoice, Order, and Credit Note create within the Custom Object schema. Fields on Contacts and Accounts create within GoHighLevel's Custom Fields settings per object.