ERP migration
Field-level mapping, validation, and rollback between Selly Erp and Acumatica. We move data and schema; workflows are rebuilt natively in Acumatica.
Selly Erp
Source
Acumatica
Destination
Compatibility
10 of 12
objects map 1:1 between Selly Erp and Acumatica.
Complexity
BStandard
Timeline
2–4 days
Overview
Selly ERP targets small to mid-sized businesses with an integrated CRM and sales management suite covering €12–35/user/month. Its data model organizes around Contacts, Companies, Deals, Products, and Activities with a deal pipeline that tracks stage, amount, and owner. Acumatica consumes this into a full ERP schema: Customers and Vendors as master records, Inventory Items with warehouse branches, Sales Orders and Purchase Orders with line-item detail, and a Chart of Accounts with legal-entity scoping. The migration maps Selly's flat deal structure into Acumatica's Opportunities or Sales Orders depending on your configuration, translates custom field values into Acumatica User-Defined Fields, and preserves product relationships across Inventory IDs. Workflow automations, email templates, and reporting configurations do not migrate and must be rebuilt from exported definitions. The migration runs via Acumatica's REST API and import tools, with a delta-pickup window capturing records modified during cutover. During pre‑migration, FlitStack extracts Selly field metadata, data types, and custom property definitions, then cross‑references them against Acumatica DACs to generate a UDF manifest. This manifest drives UDF creation in Acumatica before data loads, ensuring custom values land in the correct columns. After the initial load, a reconciliation step compares record counts, totals, and a random field sample to detect truncation, encoding mismatches, or orphaned foreign keys, triggering corrective adjustments before the final delta‑pickup window closes.
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 Selly Erp object lands in Acumatica, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Selly Erp
Contact
Acumatica
Contact (on Customer screen)
1:1Selly contact records map to Acumatica Contact sub-records under a Customer master. Primary company resolves to the Customer record using domain lookup. Phone, email, job title, and address fields transfer directly; ContactClassId applies based on Selly contact type if configured.
Selly Erp
Company
Acumatica
Customer (or Vendor)
1:1Selly company becomes an Acumatica Customer master record. Company name maps to CustomerName, domain maps to WebSite. Industry classification from Selly's dropdown maps to the CustomerClassID or a custom UDF in Acumatica. Vendors from Selly map to the Acumatica Vendor screen separately.
Selly Erp
Deal
Acumatica
Opportunity
1:1Selly deal maps to an Acumatica Opportunity linked to the Customer. Deal name becomes OpportunityID and Description. Pipeline stage from Selly becomes the StageID or a custom StageUDF field; probability and amount carry forward. Owner resolves by email match to Acumatica employee.
Selly Erp
Deal
Acumatica
Sales Order
1:manySelly deals with status 'Won' split into Acumatica Sales Orders with status 'Open' or 'Completed'. Line items derive from Deal products if Selly tracks product lines. Deals remaining in open pipeline stay as Opportunities. This split is planned before migration with customer sign-off.
Selly Erp
Product
Acumatica
Inventory Item
1:1Selly products with stock tracking map to Acumatica Inventory Items with ItemCode, Description, and base sales/purchase prices. For non-inventory items (services), Selly products map to StockItem=false with a service flag. UOM maps from Selly unit-of-measure to Acumatica's UOM class. If Selly product includes a weight or dimension attribute, FlitStack maps those to the Inventory Item's Physical Dimensions UDFs for shipping calculations.
Selly Erp
Product
Acumatica
Non-Stock Item
1:manySelly products that represent services or one-time items without inventory cost split into Acumatica Non-Stock Items with ItemType='Non-Stock'. Price sheet values map to Sales Prices on the Non-Stock Item screen. If a service product has recurring billing periods defined in Selly, FlitStack can also map those to Acumatica Subscription Management templates, provided the module is licensed.
Selly Erp
Activity (Email, Call, Meeting, Note)
Acumatica
Activity / Note
1:1Selly activities map to Acumatica Activities with Subject, Details, StartDate, EndDate, and Owner preserved. Call type maps to Type='Phone Call'; meeting to Type='Meeting'; email to Type='Email'. Notes migrate as Acumatica Notes attached to the parent Contact or Customer record. If an activity includes attachments, FlitStack downloads them and re-links them to the corresponding Acumatica Activity using the Files & Attachments mechanism.
Selly Erp
Custom Property (Contact)
Acumatica
User-Defined Field on Contact
1:1Selly contact-level custom properties become Acumatica UDFs on the Contact DAC (UsrPrefix fields). Each UDF must be pre-created in Acumatica with matching data type before migration runs. Multi-value pick-list properties split into separate UDF rows per selection. If a custom property holds a date, FlitStack maps it to a Date UDF; if it holds a numeric value, it maps to a Decimal or Integer UDF based on the precision required.
Selly Erp
Custom Property (Deal)
Acumatica
User-Defined Field on Opportunity
1:1Selly deal custom properties map to Opportunity UDFs in Acumatica. Date-type custom properties become Date fields; numeric properties become Decimal or Integer UDFs depending on precision. The Acumatica admin creates these fields in the Opportunity screen before import. For multi-select deal custom fields, FlitStack splits each selected value into a separate row in the corresponding UDF, preserving the original list in a related note.
Selly Erp
Lead / Subscriber
Acumatica
Lead (if CRM module active)
1:1Selly leads or subscribers from the marketing CRM side have no direct Acumatica equivalent unless the CRM module is licensed. FlitStack preserves these as a CSV export for re-import into your Acumatica CRM leads screen post-setup. The CSV includes all lead fields, custom properties, and original timestamps, allowing you to map them manually to Acumatica UDFs or third‑party marketing tools.
Selly Erp
Attachment / File
Acumatica
Files (Attachments on CRM screens)
1:1Selly file attachments on contacts, companies, or deals download and re-upload to Acumatica's Files & Attachments section on the matching screen. File size limits follow Acumatica's upload constraints (typically 25MB per file). If a file exceeds the limit, FlitStack splits it into chunks and reassembles them after upload, preserving the original file name and metadata.
Selly Erp
Invoice (if module active)
Acumatica
AR Invoice
1:1Selly invoices map to Acumatica AR Invoices with customer, date, description, and amount. Line items derive from Selly invoice line product references. Tax codes map to Acumatica TaxZone settings based on Selly tax configuration. If Selly includes a payment term or discount percentage, FlitStack translates those into Acumatica's Terms and Cash Discount fields on the AR Invoice.
| Selly Erp | Acumatica | Compatibility | |
|---|---|---|---|
| Contact | Contact (on Customer screen)1:1 | Fully supported | |
| Company | Customer (or Vendor)1:1 | Fully supported | |
| Deal | Opportunity1:1 | Fully supported | |
| Deal | Sales Order1:many | Fully supported | |
| Product | Inventory Item1:1 | Fully supported | |
| Product | Non-Stock Item1:many | Fully supported | |
| Activity (Email, Call, Meeting, Note) | Activity / Note1:1 | Fully supported | |
| Custom Property (Contact) | User-Defined Field on Contact1:1 | Fully supported | |
| Custom Property (Deal) | User-Defined Field on Opportunity1:1 | Fully supported | |
| Lead / Subscriber | Lead (if CRM module active)1:1 | Fully supported | |
| Attachment / File | Files (Attachments on CRM screens)1:1 | Fully supported | |
| Invoice (if module active) | AR Invoice1:1 | Fully supported |
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.
Selly Erp gotchas
No public API forces manual data export
Invoice PDFs are not exported as structured records
Workflow automations are undocumented and non-transferable
Acumatica gotchas
API user licenses cap concurrent sessions and request throughput
Multi-tenant filtering requires CompanyID awareness
Custom fields require separate discovery before field mapping
Notes and attachments use a separate linked table structure
Implementation timelines frequently run 3–9 months end-to-end
Pair-specific challenges
Migration approach
Audit Selly ERP data export and inventory all record types
FlitStack connects to your Selly ERP instance via API or exported CSV and inventories every Contact, Company, Deal, Product, Activity, and custom property definition. We count records per type, flag duplicates, and assess the cleanliness of email addresses and owner fields. This inventory feeds the Acumatica schema design and the UDF manifest for custom fields. The audit also identifies missing foreign keys, such as owner email patterns, to flag potential mismatches before mapping begins.
Design Acumatica schema and pre-create User-Defined Fields
Based on the Selly data inventory, FlitStack maps each object and field to its Acumatica equivalent. For custom properties without native equivalents, we deliver a UDF manifest specifying field name, data type, and DAC attachment. Your Acumatica admin (or our team) creates these UDFs before migration data lands. This step also defines the deal-split rule for Won deals and the owner resolution fallback.
Resolve owner and company relationships before import
Before any record loads into Acumatica, FlitStack matches Selly owner emails to Acumatica Employee records and flags unmatched owners. Companies and contacts are sequenced so foreign keys resolve correctly — Customer records exist before Contact records, and Contact records exist before Opportunity records. This sequencing ensures no orphaned lookups appear in Acumatica after import. If a match cannot be found, FlitStack assigns the record to a designated fallback employee and logs the exception for review.
Run sample migration with field-level diff and reconciliation
A representative sample (typically 200–500 records covering all object types and custom fields) migrates into a test Acumatica environment. FlitStack generates a field-level diff report comparing source and destination values per record, so you can verify UDF mapping, owner resolution, stage mapping, and deal-split application before the full run commits. You review the diff, approve any adjustments, and FlitStack incorporates feedback before the production migration proceeds.
Execute full migration with delta-pickup and audit log
After sample sign-off, the full migration runs against your production Acumatica instance. A delta-pickup window (typically 24–48 hours) captures any records modified in Selly ERP during cutover. Every import operation is recorded in an audit log. If reconciliation reveals discrepancies, FlitStack provides one-click rollback to the pre-migration state so you can re-run without data corruption. Post-migration, you can compare totals and spot-check records to confirm data integrity before decommissioning Selly ERP.
Platform deep dives
Selly Erp
Source
Strengths
Weaknesses
Acumatica
Destination
Strengths
Weaknesses
Complexity grading
Standard ERP migration. 1 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 Selly Erp and Acumatica.
Object compatibility
1 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
Selly Erp: Not publicly documented.
Data volume sensitivity
Selly Erp doesn't expose a bulk API — REST + parallelization used for high-volume runs.
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 Selly Erp to Acumatica migration scoping. Not seeing yours? Book a call.
Walk through your Selly Erp to Acumatica migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Selly Erp
Other ways to arrive at Acumatica
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.