CRM migration
Field-level mapping, validation, and rollback between Sellsy and monday CRM. We move data and schema; workflows are rebuilt natively in monday CRM.
Sellsy
Source
monday CRM
Destination
Compatibility
7 of 11
objects map 1:1 between Sellsy and monday CRM.
Complexity
BStandard
Timeline
2-4 weeks
Overview
Sellsy combines CRM, invoicing, and pre-accounting in a single French-market platform with a flat Contact model that bundles Individuals and Corporations without a clean separation key. Monday.com CRM uses a board-based architecture with native Accounts, Contacts, Deals, and Services entities. The structural difference that most affects migration is that Monday.com CRM has no native invoicing, order management, or credit note module, so these financial records require either manual re-entry, a third-party integration, or acceptance that they will not carry over. We sequence the Contact-Corporation split as the first pre-flight step, remap Sellsy SmartTags to Monday.com Tags, preserve Staff as Owner assignments, and use Monday.com's API with batch chunking and adaptive throttling to handle the platform's undocumented rate limits. Workflows, automations, and sequence cadences from Sellsy do not migrate; we deliver a written automation inventory for the customer's admin to rebuild in Monday.com's board-based workflow builder.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Sellsy object lands in monday CRM, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Sellsy
Contact (Individual type)
monday CRM
Contact
1:1Sellsy Contact records of Individual type export bundled with Corporation records and must be split by the type discriminator before import. We detect the type field during pre-flight and route Individual records to the Monday.com Contact object. Name, email, phone, mobile, position, and address fields map to Monday.com Contact column equivalents. Owner assignment resolves via email match against the Monday.com User table.
Sellsy
Corporation
monday CRM
Account
1:1Sellsy Corporation records map to Monday.com Account. The Corporation name, SIRENE registry reference (if present), address, and website fields migrate. Account is created before any Contact import so that the Account-Contact relationship is satisfied at the moment of Contact insert. Monday.com Accounts have no native financial credit rating or company size fields; these migrate to custom fields if the customer requires them.
Sellsy
Opportunity
monday CRM
Deal
1:1Sellsy Opportunities map to Monday.com Deals. Pipeline stage, deal amount, probability, expected close date, and owner migrate directly. Monday.com Deal status (Won, Lost, Open) maps from Sellsy opportunity state. Closed-Lost reason from Sellsy custom properties becomes a Monday.com custom field on Deal.
Sellsy
Invoice
monday CRM
No direct equivalent
lossySellsy Invoices have no native Monday.com CRM equivalent. Monday.com CRM does not include an invoicing module. We export Invoice records as a structured CSV with line items, amounts, status (draft, sent, paid), and SmartTags. The customer receives this as a deliverable for re-entry into their chosen invoicing tool (Stripe, Quaderno, Pennylane, or a Monday.com-integrated billing app). SmartTags from invoices map to Tags on the exported CSV record.
Sellsy
Order
monday CRM
No direct equivalent
lossySellsy Orders (commercial transaction records distinct from invoices) have no Monday.com CRM equivalent. We export Orders with product-line amounts, status, and linked Corporation as a CSV deliverable. The customer receives this for re-entry or integration with an order management system. SmartTags migrate to Tags on the exported CSV.
Sellsy
Credit Note
monday CRM
No direct equivalent
lossySellsy Credit Notes (first-class API objects since v2.86.0) have no Monday.com CRM equivalent. We export Credit Notes with linked Invoice reference, amount, and status as a CSV deliverable. The linked invoice reference in the CSV points to the exported invoice record in the same deliverable package.
Sellsy
Staff
monday CRM
User (Owner)
1:1Sellsy Staff records map to Monday.com User records for Owner assignment. We resolve by email match. Sellsy's privilege and role model has no direct Monday.com equivalent; access control in Monday.com CRM uses workspace membership levels (member, viewer). We document the role mapping and any Staff records that cannot be matched go to a reconciliation queue for the customer's admin to provision before record import.
Sellsy
Task
monday CRM
Task
1:1Sellsy Tasks map to Monday.com Tasks. Due date, assignee (via Staff-User resolution), task status, and description migrate. Task links to Contact or Opportunity preserved as the Monday.com Task's related item reference.
Sellsy
Activity (calls, meetings, emails)
monday CRM
Activity
1:1Sellsy Activity records (appointments, calls, logged interactions) attach to Contacts and Opportunities. We map these to Monday.com Activity records linked to the corresponding Contact or Deal. Activity timestamp, type (call, meeting, email), duration, and notes migrate. Monday.com CRM Activity columns include Date, Type, Description, and related Contact or Deal reference.
Sellsy
Product
monday CRM
Item (Services or Products board)
1:1Sellsy Product catalog entries map to Monday.com Items in a dedicated Products or Services board. Product name, SKU (mapped to a text column), pricing, and description migrate. Monday.com Items in a Products board serve as the lookup source for Deal line items.
Sellsy
SmartTags
monday CRM
Tags
lossySellsy SmartTags apply to Invoices, Orders, and Credit Notes as a tagging layer. Monday.com Tags apply to Items on a board. We remap SmartTags to Monday.com Tags on the exported financial document CSV as a tag field, preserving the taxonomy. For CRM records (Contacts, Accounts, Deals), Monday.com does not have a native tagging layer at record level; Tags are board-scope only. If the customer requires per-record tagging on CRM objects, we create a custom Tag text column to hold SmartTag values.
| Sellsy | monday CRM | Compatibility | |
|---|---|---|---|
| Contact (Individual type) | Contact1:1 | Fully supported | |
| Corporation | Account1:1 | Fully supported | |
| Opportunity | Deal1:1 | Fully supported | |
| Invoice | No direct equivalentlossy | Fully supported | |
| Order | No direct equivalentlossy | Fully supported | |
| Credit Note | No direct equivalentlossy | Fully supported | |
| Staff | User (Owner)1:1 | Mapping required | |
| Task | Task1:1 | Fully supported | |
| Activity (calls, meetings, emails) | Activity1:1 | Fully supported | |
| Product | Item (Services or Products board)1:1 | Fully supported | |
| SmartTags | Tagslossy | Mapping required |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Sellsy gotchas
Owner name uniqueness required in CSV exports
Pricing numbers scattered across modular and bundled models
SmartTags are a tagging layer, not a structured object
Public API rate limits not documented
monday CRM gotchas
Subitems are not included in bulk exports
Daily API call limits vary sharply by plan
Legacy automations (Sentence Builder) are being deprecated
Excel and account exports only include table views
Enterprise admins can disable non-admin exports
Pair-specific challenges
Migration approach
Discovery and scoping
We audit the source Sellsy account across CRM records (Contacts, Corporations, Opportunities), financial documents (Invoices, Orders, Credit Notes), activity history, product catalog, Staff count, and SmartTag taxonomy. We confirm whether the customer has an existing or planned third-party invoicing tool for Monday.com and whether SmartTag categorization on financial documents is business-critical. The discovery output is a written migration scope document with record counts, a flag on every financial document requiring CSV export, and a decision point on per-record tagging for CRM objects.
Contact-Corporation split and pre-flight
Sellsy's Contact export bundles Individuals and Corporations without a clean separation field. We run the type discriminator split as the first pre-flight step before any import planning. We also detect duplicate Staff owner names, identify any missing owner email addresses, and flag SmartTag values that have no Monday.com column type to map into. The pre-flight report is shared with the customer for resolution before the migration begins.
Monday.com board and entity configuration
We configure Monday.com CRM boards for Accounts, Contacts, Deals, and Services (if applicable). Custom fields are created to receive Sellsy custom field values and any SmartTag values the customer wants preserved on CRM records. Owner assignments are configured using the Monday.com User table with Staff email as the matching key. The Product or Services board is configured to receive the Sellsy product catalog entries.
Record migration in dependency order
We run production migration in dependency order: Monday.com Users (validated against Staff records), Accounts (from Sellsy Corporations), Contacts (with AccountId resolved from the Corporation mapping), Deals (with OwnerId resolved and stage mapped), Activities (Tasks and logged interactions linked to Contact or Deal), Products (as Items in the Services board). Financial documents (Invoices, Orders, Credit Notes) export as a structured CSV with SmartTags preserved in a Tag column and are delivered as a separate package for the customer's invoicing tool re-entry. Each phase emits a row-count reconciliation report.
Automation inventory and handoff
We deliver a written inventory of every active Sellsy automation rule with its trigger object, conditions, and actions, paired with a recommended Monday.com automation recipe equivalent using Monday.com's trigger-action builder. We do not migrate automations as code. We support a one-week hypercare window where we resolve any record reconciliation issues raised by the customer's team.
Platform deep dives
Sellsy
Source
Strengths
Weaknesses
monday CRM
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Sellsy and monday CRM.
Object compatibility
2 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Sellsy: Not publicly documented.
Data volume sensitivity
Sellsy exposes a bulk API — large-volume migrations stream efficiently.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Sellsy to monday CRM migration scoping. Not seeing yours? Book a call.
Walk through your Sellsy to monday CRM migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Sellsy
Other ways to arrive at monday CRM
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.
