CRM migration

Migrate from Sellsy to Zoho CRM

Field-level mapping, validation, and rollback between Sellsy and Zoho CRM. We move data and schema; workflows are rebuilt natively in Zoho CRM.

Sellsy logo

Sellsy

Source

Zoho CRM

Destination

Zoho CRM logo

Compatibility

71%

10 of 14

objects map 1:1 between Sellsy and Zoho CRM.

Complexity

BStandard

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from Sellsy to Zoho CRM is a structural migration that requires separating Sellsy's conflated Contact model, remapping financial documents from Sellsy's integrated invoicing layer to Zoho CRM's Quote-SalesOrder-Invoice flow, and resolving owner references across a different user-management paradigm. Sellsy bundles Individuals and Corporations in a single Contact object with a type discriminator; Zoho maintains separate Contacts and Accounts modules, so we split by type at migration time and wire the resulting Contact to the corresponding Account before any Deals attach. SmartTags on Invoices, Orders, and Credit Notes become Zoho Tags, and Sellsy Staff records map to Zoho Users with a reconciliation queue for any unresolved owners. We do not migrate Sellsy's workflows, document templates, or access-control rules; we deliver a written inventory of these for your admin to rebuild in Zoho's Blueprint and Workflow Rule builders.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Sellsy logo

Sellsy

What's pushing teams away

  • Steep learning curve that requires roughly one week to become productive: reviewers consistently report Sellsy is not intuitive and the information architecture demands significant onboarding investment before teams can work efficiently.
  • Pricing opacity across public sources creates buying friction: Sellsy has been transitioning from modular to bundled pricing for years, leaving outdated numbers scattered across Capterra, G2, and its own site — confusing prospects and delaying sign-off.
  • Interface and UX lag behind newer CRM alternatives: reviewers note the design feels dated compared to platforms like Pipedrive, with imperfect ergonomics that create friction even for basic workflows after the initial learning period.
  • Document template and workflow setup takes 2–3 hours to configure properly: initial setup of custom fields, pipelines, and document templates is non-trivial, and basic configuration at go-live still requires deliberate configuration effort.

Choosing

Zoho CRM logo

Zoho CRM

What's pulling them in

  • Free tier is genuinely usable for up to 3 users with leads, pipeline management, and email tracking — no credit card required, making it easy to evaluate before committing.
  • Pricing undercuts Salesforce by 80–90% at equivalent feature tiers, with Enterprise plans offering capabilities that cost 3–4× more on competing platforms.
  • Deep ecosystem of 45+ integrated apps (Books, Desk, Creator, Campaigns) means companies already in the Zoho suite get native integrations without third-party connectors.
  • Highly customizable: custom modules, custom fields, Canvas drag-and-drop layouts, and Blueprint workflow automation without requiring developer resources.
  • Small-business reviewers highlight real-time team visibility, daily time savings of 60–90 minutes, and the ability to mold the CRM to any industry vertical.

Object mapping

How Sellsy objects map to Zoho CRM

Each row shows how a Sellsy object lands in Zoho 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 (type=individual)

maps to

Zoho CRM

Contact

1:1
Fully supported

Sellsy exports all Contacts in a single bundle with a type discriminator field that identifies Individual versus Corporation. We split by type during pre-flight: Individual records map to Zoho CRM Contact with the name split into First Name and Last Name fields, email mapped to Email, phone mapped to Phone, and the original Sellsy Contact ID preserved in a custom field sellsy_contact_id__c for cross-system reference. Address fields map to Zoho's Mailing Street, Mailing City, Mailing State, and Mailing Country composite or split fields per the customer's address format preference.

Sellsy

Corporation

maps to

Zoho CRM

Account

1:1
Fully supported

Sellsy Corporation records map to Zoho CRM Account. Corporation name becomes Account Name, SIRENE registry number (if present) maps to a custom field sellsy_siren__c, website maps to Website, and phone maps to Phone. The Sellsy Corporation ID is preserved in sellsy_corporation_id__c. Account is created before any Contact import so that the Contact-Account lookup (Account Name lookup or Account ID) is satisfied at the moment of Contact insert.

Sellsy

Contact (type=corporation)

maps to

Zoho CRM

Contact

1:many
Fully supported

Sellsy Contacts of type=corporation represent people associated with a company who are not the primary account contact. We map these to Zoho CRM Contact records linked to the Account created from the corresponding Corporation. The Contact-Account relationship uses the Account Name lookup or a custom Account ID field. The original Sellsy Corporation reference is preserved in a custom field so that the linkage remains auditable.

Sellsy

Opportunity

maps to

Zoho CRM

Deal

1:1
Fully supported

Sellsy Opportunities map to Zoho CRM Deals. Opportunity name becomes Deal Name, amount maps to Amount, closing date maps to Closing Date, owner_id resolves to Zoho User via email match, and pipeline stages map to Zoho Stage picklist values. We configure Zoho Stages before migration to match the Sellsy pipeline stage names and probabilities so that the stage distribution is preserved. The original Sellsy opportunity ID goes in sellsy_opportunity_id__c.

Sellsy

Pipeline (Opportunity stages)

maps to

Zoho CRM

Deal Stages

lossy
Fully supported

Sellsy deal pipelines and their stage definitions (names, probabilities, order) map to Zoho CRM Deal Stage picklist values. We create the stage sequence in Zoho before Deal import so that all Deals land in the correct stage on first insert. If Sellsy has multiple pipelines, we use Zoho's Stage custom field or a Deal custom field to preserve the pipeline context.

Sellsy

Invoice

maps to

Zoho CRM

Invoice

1:1
Fully supported

Sellsy Invoices map to Zoho CRM Invoice. Line items (product name, quantity, unit price, discount, tax) map to Invoice Items. Invoice status (draft, sent, paid, overdue) maps to Zoho Invoice Status. The linked Contact and Corporation from Sellsy resolve to the Zoho Contact and Account created earlier in the migration. SmartTags on invoices become Zoho Tags. We preserve the original Sellsy invoice number in sellsy_invoice_id__c and the invoice date as the Invoice Date in Zoho.

Sellsy

Order

maps to

Zoho CRM

Sales Order

1:1
Fully supported

Sellsy Orders map to Zoho CRM Sales Order. Product-line items migrate to Sales Order Items with quantity, unit price, and discount preserved. The linked Contact and Corporation resolve to the migrated Zoho Contact and Account. SmartTags become Zoho Tags. Order status maps to Zoho Status picklist values. We preserve the original Sellsy order number in sellsy_order_id__c.

Sellsy

Credit Note

maps to

Zoho CRM

Invoice (Credit Note subtype)

1:1
Fully supported

Sellsy Credit Notes (API v2.86.0+) map to Zoho CRM Invoice records with a Credit Note flag or a custom field sellsy_credit_note__c set to true. The linked invoice reference maps to the Related To (WhatId) field on the Zoho Invoice. Credit note amount, reason, and date migrate to corresponding Zoho Invoice fields. SmartTags become Zoho Tags.

Sellsy

Staff

maps to

Zoho CRM

User

1:1
Mapping required

Sellsy Staff records represent users and carry role information. We map Staff to Zoho CRM User by email match. Any Sellsy Staff without a matching Zoho User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Role and privilege information does not migrate because Zoho's Roles and Profiles system is structurally different from Sellsy's privilege model; we deliver a written map of each Staff member's Sellsy role for the admin to assign equivalent Zoho permissions.

Sellsy

Task

maps to

Zoho CRM

Task

1:1
Fully supported

Sellsy Tasks map to Zoho CRM Task. Subject, description, due date, status, and priority migrate directly. Assignee from Sellsy task.owner_id resolves to Zoho User ID via the Staff-User lookup. The linked Contact or Opportunity from Sellsy resolves to Zoho Contact ID or Deal ID. We preserve the original Sellsy task ID in sellsy_task_id__c.

Sellsy

Activity (appointments, calls, logged interactions)

maps to

Zoho CRM

Event

1:1
Fully supported

Sellsy Activities mapped to appointments and meetings migrate to Zoho CRM Event records with Subject, Start DateTime, End DateTime, and Location. Attendee information maps to Event Participants. Call logs migrate to Zoho Tasks with Task Type set to Call and Call Duration in a custom field. The linked Contact and Opportunity from Sellsy resolve to Zoho Contact ID and Deal ID. Activity timestamps are preserved as Event Start DateTime and End DateTime.

Sellsy

Product

maps to

Zoho CRM

Product

1:1
Fully supported

Sellsy Product catalog entries map to Zoho CRM Product. Product name, code (hs_sku equivalent), unit price, and product description migrate. If Sellsy has pricing tiers or matrix pricing, we map these to Zoho Price Books and Price Book Entries. The original Sellsy product ID is preserved in sellsy_product_id__c.

Sellsy

SmartTags (Invoice, Order, Credit Note)

maps to

Zoho CRM

Tags

lossy
Mapping required

SmartTags are Sellsy's transaction-level tagging system and have no direct Zoho CRM equivalent as a relational object. We remap SmartTags as Zoho native Tags on the respective Invoice, Sales Order, and Credit Note records. If Zoho Tags are insufficient for the customer's taxonomy, we create a custom field sellsy_smart_tag__c (single or multi-select picklist) on the relevant modules to preserve the full SmartTag vocabulary.

Sellsy

Custom Fields (Invoices, Contacts, Corporations)

maps to

Zoho CRM

Custom Fields

lossy
Fully supported

Sellsy custom fields on Invoices, Contacts, and Corporations (accessed via GET+PUT /custom-fields endpoints) map to Zoho CRM custom fields of equivalent type. We inspect the custom field schema at scoping, create matching Zoho custom fields (with appropriate field types: text, number, date, picklist, multi-select, checkbox) before migration, and map values during the import phase. Field-level validation rules in Zoho are coordinated with the customer's admin to avoid import blocking.

Gotchas + challenges

What specifically takes care here

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 logo

Sellsy gotchas

High

Owner name uniqueness required in CSV exports

Medium

Pricing numbers scattered across modular and bundled models

Medium

SmartTags are a tagging layer, not a structured object

Medium

Public API rate limits not documented

Zoho CRM logo

Zoho CRM gotchas

High

API access requires Professional tier or above

High

Subform fields do not export cleanly via CSV

Medium

API credit consumption is non-linear

Medium

Export download links expire in 7 days

Medium

Owner (User) assignments require pre-mapped user IDs

Pair-specific challenges

  • Sellsy bundles Individuals and Corporations in one Contact export

    Sellsy's Contact export bundles Individuals and Corporations together with a type discriminator field rather than separating them into distinct API endpoints. If this type split is not performed before import, Zoho CRM will receive Corporation records mapped as Contacts (with no First Name, just a company name) and Individual records mixed in. We handle the split during pre-flight by reading the type discriminator and routing Corporation-type records to the Account import first, then linking Individual contacts to those Accounts. Failure to split before import results in orphaned Contacts in Zoho with no Account lookup and duplicate Account creation when Corporation records are imported separately.

  • Sellsy SmartTags have no direct Zoho CRM equivalent

    SmartTags in Sellsy function as a tagging layer applied to Invoices, Orders, and Credit Notes. Zoho CRM has a native Tags system, but it is module-scoped (Tags on Contacts, Tags on Deals) rather than document-specific. We remap SmartTags to Zoho Tags on the respective document records. If the customer's SmartTag taxonomy is complex (hierarchical tags, tag-based reporting, or cross-document tag inheritance), Zoho's Tags may not replicate that behavior, and we create a custom multi-select picklist field on each financial document module to preserve the full vocabulary. The customer chooses the strategy during scoping.

  • Sellsy Owner name uniqueness required in CSV exports

    Sellsy's CSV export for contacts does not deduplicate owner names. If multiple Staff members share the same name, the import process in downstream systems uses the first match only. We detect duplicate owner names in the exported CSV during the pre-flight phase and ask the customer to either disambiguate in Sellsy before export or provide a unique identifier field. Failure to handle this results in owner assignment silently defaulting to one person across all affected records, breaking the accountability chain for Deals, Tasks, and Documents.

  • Financial document linkage to Contacts and Accounts requires sequenced import

    Sellsy Invoices, Orders, and Credit Notes reference Contact and Corporation IDs. In Zoho CRM, Invoices and Sales Orders require a linked Contact (WhoID) and optionally an Account (for B2B contexts). If Contacts and Accounts are not migrated and validated before financial documents are imported, the document linkage will fail and invoices will land as orphaned records. We sequence the import as: Accounts first, then Contacts, then Products, then Invoices, Sales Orders, and Credit Notes. Each phase emits a row-count reconciliation report before the next begins.

  • Zoho field validation rules can block invoice and deal import

    Zoho CRM enforces field-level validation rules (required format for email, conditional required fields, picklist whitelist enforcement) that can reject records during bulk import. We coordinate with the customer's Zoho admin to either temporarily disable validation rules during the load window or extend them with a migration-context check. Skipping this step results in 5-20 percent record rejection on the first import attempt, particularly for Invoices with missing line items or Deals with stage values not in the active picklist.

Migration approach

Six steps for a successful Sellsy to Zoho CRM data migration

  1. Discovery and scoping

    We audit the source Sellsy account across plan tier (Standard, Professional, Scale), object inventory (Contacts, Corporations, Opportunities, Invoices, Orders, Credit Notes, Tasks, Activities, Products), custom field schemas, SmartTag taxonomy, Staff count, and engagement volume. We pair this with a Zoho CRM edition assessment: Standard ($14/user/month) covers most SMB migrations; Professional ($20/user/month) adds workflow rules, Blueprints, and macro support; Enterprise ($35/user/month) is required for advanced validation rules, scoring, and territory management. The discovery output is a written migration scope, object inventory, and Zoho edition recommendation.

  2. Contact-Corporation split and schema design

    We split Sellsy's combined Contact export by the type discriminator into Individual records (mapped to Zoho Contact) and Corporation records (mapped to Zoho Account) before any Zoho import begins. We design the destination Zoho CRM schema: Contacts and Accounts modules with the lookup relationship, Deal stages pre-configured to match Sellsy pipeline names, custom fields created to match Sellsy custom field types, and Tags taxonomy designed for SmartTag remapping. Schema is validated in a Zoho Sandbox org before production migration.

  3. Staff-to-User reconciliation and User provisioning

    We extract every distinct Sellsy Staff member referenced on Contact, Opportunity, Task, and Document records and match by email against the Zoho CRM destination org's User table. Any Sellsy Staff without a matching Zoho User goes to a reconciliation queue. The customer's Zoho admin provisions any missing Users (active or inactive depending on whether the original Sellsy user is still employed). Migration cannot proceed past this step because Owner and assignee references on Deals, Tasks, and Documents require a valid Zoho User ID.

  4. Sandbox migration and reconciliation

    We run a full migration into a Zoho Sandbox (Copy Production configuration) using production-like data volume. The customer's admin reconciles record counts (Accounts in, Contacts in, Deals in, Invoices in, Sales Orders in, Credit Notes in, Tasks in, Events in), spot-checks 25-50 random records against the Sellsy source, and validates SmartTag remapping on sample invoices and orders. The customer signs off on the mapping before production migration begins. Any mapping corrections happen in Sandbox, not production.

  5. Production migration in dependency order

    We run production migration in record-dependency order: Accounts (from Sellsy Corporations first), Contacts (Individuals then Corporation-linked contacts), Products, Deals (with Account lookup and User owner resolved), Tasks and Events, Invoices (with Contact and Account lookup resolved, SmartTags remapped to Tags), Sales Orders, Credit Notes (with linked Invoice reference resolved), and SmartTags fallback custom fields if the customer chose the picklist strategy over native Tags. Each phase emits a row-count reconciliation report before the next phase begins.

  6. Cutover, delta migration, and Workflow rebuild handoff

    We freeze Sellsy writes during cutover, run a final delta migration of any records modified during the migration window, then enable Zoho CRM as the system of record. We deliver a written inventory of Sellsy Workflows, document templates, and privilege/access-control rules with Zoho equivalent recommendations (Workflow Rules, Blueprint, and Roles respectively). We support a one-week hypercare window where we resolve any reconciliation issues raised by the customer's team. We do not rebuild Sellsy Workflows as Zoho Blueprint or Workflow Rules inside the migration scope; that is a separate engagement or an internal admin task.

Platform deep dives

Context on both ends of the pair

Sellsy logo

Sellsy

Source

Strengths

  • Comprehensive feature stack covering CRM, invoicing, pre-accounting, and marketing in a single subscription.
  • Native GDPR compliance and French market features including SIRENE directory enrichment.
  • Competitive pricing for very small to mid-sized French businesses compared to international alternatives.
  • Integrated electronic document signing reduces the need for third-party document workflow tools.
  • Automation of routine billing and proposal workflows reduces manual administrative overhead.

Weaknesses

  • Steep learning curve with a one-week ramp-up period reported by multiple reviewers.
  • Interface and UX design feel dated compared to modern CRM alternatives like Pipedrive.
  • Pricing structure has been in transition from modular to bundled, creating confusion across public sources.
  • Limited API documentation and undocumented public rate limits complicate programmatic integrations.
  • Owner name uniqueness requirement in CSV exports can block bulk imports with duplicate owners.
Zoho CRM logo

Zoho CRM

Destination

Strengths

  • Generous free tier (3 users) with real CRM functionality — no artificial feature restrictions that prevent valid use cases.
  • Per-seat pricing is transparent and predictable; no contact-based billing surprises that inflate monthly invoices.
  • Blueprint visual workflow builder lets sales ops teams automate stage progressions without developer involvement.
  • Canvas drag-and-drop layout editor lets non-technical users customize module views and forms per role.
  • Active development cadence: API v8 is well-documented, supports bulk endpoints, and COQL queries handle complex filtering.

Weaknesses

  • Poor support quality and inconsistent SLA — Enterprise tier requires 50+ user minimum for Priority Phone support.
  • Daily export limits in the UI vary by plan tier, making large dataset extraction slow and planning-dependent.
  • Zia AI features are gated behind $40+/user Enterprise tier, not available to most SMB customers who chose Zoho for cost savings.
  • User-reported occasional UI inconsistencies and performance slowdowns on large datasets with many custom fields.
  • No EU-hosted option limits appeal for GDPR-sensitive companies; some competitors offer data residency guarantees Zoho does not.

Complexity grading

How hard is this migration?

Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Sellsy and Zoho CRM.

  • Object compatibility

    B

    2 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Sellsy: Not publicly documented.

  • Data volume sensitivity

    A

    Sellsy exposes a bulk API — large-volume migrations stream efficiently.

Estimator

Estimate your Sellsy to Zoho CRM migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Sellsy to Zoho CRM data migrations

Answers to the questions buyers ask most during Sellsy to Zoho CRM migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your Sellsy to Zoho CRM migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most migrations land between three and five weeks for accounts under 15,000 Contacts and 3,000 Deals with no financial document migration. Migrations that include Invoices, Orders, Credit Notes, and SmartTag remapping move to eight to twelve weeks because of the Contact-Corporation split work, document lineage resolution, and the Staff-to-User reconciliation phase. The Zoho Sandbox validation step adds approximately five to seven business days to the timeline but prevents production errors.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Sellsy.
Land in Zoho CRM, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day