Migrate your Selly Erp data
Italian-founded SMB CRM and business management platform with sales, inventory, accounting, and workflow modules bundled in three flat per-user tiers.
In its favor
Why people choose Selly Erp
The signal that keeps Selly Erp on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Small Italian businesses pick Selly ERP because it consolidates CRM, sales pipeline, and light accounting into a single subscription rather than managing separate tools.
Google Workspace integration is a documented reason for adoption — customers already in the Google ecosystem find the connection to Gmail and Google Drive frictionless.
The three-tier flat per-user pricing model appeals to SMBs that want cost predictability without per-module add-on charges that tiered ERPs impose.
Customers cite outstanding customer support in Italian as a differentiator — multiple Capterra reviews specifically praise the assistance team for helping with customisation workarounds.
The platform covers the full sales cycle from lead capture to quote generation to invoicing, reducing the need for separate billing or proposal tools.
Third-party ERP integrations are limited — existing accounting or inventory systems do not integrate smoothly with open platforms, forcing manual data re-entry.
Technical studios and businesses with specialist workflow needs report that Selly ERP requires significant customisation workarounds to fit their use case, which some find unsustainable.
Customers migrating away report that the platform lacks a well-documented public API, making automated data extraction difficult and dependent on in-app exports.
The analytics and reporting module is described as functional but not deep — power users needing custom dashboards or advanced forecasting outgrow the built-in capabilities.
Reasons to switch
Why people leave Selly Erp
The recurring reasons buyers give for replacing Selly Erp. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Selly Erp fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Selly Erp pricing overview
Selly ERP charges a flat per-user monthly fee across three tiers, ranging from €12 to €35 per user per month. There is no published per-module or per-transaction pricing, making the total cost predictable for teams that know their headcount.
CRM Base
Tier 1 of 3
€12/user/month
What's included
Need help selecting your ERP?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Selly Erp's schedule — see our quote-based pricing →
What gets migrated
Selly Erp object support
Object-by-object support for Selly Erp migrations. Per-pair details surface during scoping.
Leads
Fully supportedSelly ERP's Lead Management module stores prospect records with standard fields for name, contact details, source, and status. We extract these as Contacts in the destination and preserve the lead source as a custom property.
Opportunities
Fully supportedOpportunities map directly to Deals or Pipeline Stages in standard CRMs. We carry over stage assignments, estimated values, and close dates during migration.
Customers
Fully supportedCustomer records in Selly ERP include company details, billing addresses, and linked contacts. We map these to Accounts and Contacts in the destination, preserving the relationship.
Deals
Mapping requiredDeals in Selly ERP track pipeline positions and monetary values. We map the deal name, value, stage, and owner. Stage labels vary between accounts so we confirm the mapping with the customer before import.
Pipeline Stages
Mapping requiredSelly ERP allows custom pipeline stage names. We extract the full stage list during scoping and create corresponding stages in the destination, renaming where necessary to match existing pipeline conventions.
Invoices
Mapping requiredSelly ERP generates invoices linked to customers and deals. We extract invoice records as structured line items and separately archive the rendered PDF for reference, since not all destinations accept invoice objects natively.
Quotes
Mapping requiredQuotes are generated from opportunity data. We carry over quote line items, totals, and validity dates. Custom quote templates do not transfer and must be rebuilt in the destination.
Activities
Mapping requiredActivity history including calls, emails, and notes attached to contacts or deals is migrated as engagement records. We normalise timestamps to the destination timezone during import.
Users and Owners
Mapping requiredSelly ERP user accounts map to Owner fields on records in the destination. We flag any inactive or archived users that should not receive an active seat in the new system.
Workflow Automations
Not in this platformWorkflow rules and automated sequences inside Selly ERP are platform-specific and cannot be exported as structured data. We document the active automations during the discovery call and provide a written spec so the customer can rebuild them manually in the destination.
Custom Fields
Mapping requiredCustom fields on any object are extracted as-is during export. We preserve the field name and data type, creating matching custom fields in the destination before importing the values.
Attachments
Mapping requiredFile attachments linked to records are extracted from the export and stored separately for re-upload after record creation in the destination, since attachments do not consistently survive bulk import processes.
| Object | Support | Notes |
|---|---|---|
| Leads | Fully supported | Selly ERP's Lead Management module stores prospect records with standard fields for name, contact details, source, and status. We extract these as Contacts in the destination and preserve the lead source as a custom property. |
| Opportunities | Fully supported | Opportunities map directly to Deals or Pipeline Stages in standard CRMs. We carry over stage assignments, estimated values, and close dates during migration. |
| Customers | Fully supported | Customer records in Selly ERP include company details, billing addresses, and linked contacts. We map these to Accounts and Contacts in the destination, preserving the relationship. |
| Deals | Mapping required | Deals in Selly ERP track pipeline positions and monetary values. We map the deal name, value, stage, and owner. Stage labels vary between accounts so we confirm the mapping with the customer before import. |
| Pipeline Stages | Mapping required | Selly ERP allows custom pipeline stage names. We extract the full stage list during scoping and create corresponding stages in the destination, renaming where necessary to match existing pipeline conventions. |
| Invoices | Mapping required | Selly ERP generates invoices linked to customers and deals. We extract invoice records as structured line items and separately archive the rendered PDF for reference, since not all destinations accept invoice objects natively. |
| Quotes | Mapping required | Quotes are generated from opportunity data. We carry over quote line items, totals, and validity dates. Custom quote templates do not transfer and must be rebuilt in the destination. |
| Activities | Mapping required | Activity history including calls, emails, and notes attached to contacts or deals is migrated as engagement records. We normalise timestamps to the destination timezone during import. |
| Users and Owners | Mapping required | Selly ERP user accounts map to Owner fields on records in the destination. We flag any inactive or archived users that should not receive an active seat in the new system. |
| Workflow Automations | Not in this platform | Workflow rules and automated sequences inside Selly ERP are platform-specific and cannot be exported as structured data. We document the active automations during the discovery call and provide a written spec so the customer can rebuild them manually in the destination. |
| Custom Fields | Mapping required | Custom fields on any object are extracted as-is during export. We preserve the field name and data type, creating matching custom fields in the destination before importing the values. |
| Attachments | Mapping required | File attachments linked to records are extracted from the export and stored separately for re-upload after record creation in the destination, since attachments do not consistently survive bulk import processes. |
Gotchas
What to watch for in Selly Erp migrations
Issues we've hit on past Selly Erp migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
No public API forces manual data export
Invoice PDFs are not exported as structured records
Workflow automations are undocumented and non-transferable
| Severity | Issue |
|---|---|
| High | No public API forces manual data export |
| Medium | Invoice PDFs are not exported as structured records |
| Medium | Workflow automations are undocumented and non-transferable |
Leaving Selly Erp?
Where Selly Erp customers move next
6 destinations Selly Erp can migrate to.
How a Selly Erp migration works
Four steps, Selly Erp-specific
Connect
API key/token (specific authentication scheme not publicly indexed) into Selly Erp. Scopes limited to read-only on the data we move.
Map
We translate Selly Erp-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Selly Erp quirks before production.
Migrate
Full migration with Selly Erp rate-limit handling. Rollback available throughout.
FAQ
Selly Erp migration FAQ
Answers to the questions buyers ask most during Selly Erp migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Selly Erp migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate Selly Erp.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Selly Erp setup and destination — written quote back within a business day.