ERP migration

Migrate from Selly Erp to Acumatica

Field-level mapping, validation, and rollback between Selly Erp and Acumatica. We move data and schema; workflows are rebuilt natively in Acumatica.

Selly Erp logo

Selly Erp

Source

Acumatica

Destination

Acumatica logo

Compatibility

83%

10 of 12

objects map 1:1 between Selly Erp and Acumatica.

Complexity

BStandard

Timeline

2–4 days

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

Selly Erp logo

Selly Erp

What's pushing teams away

  • 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.

Choosing

Acumatica logo

Acumatica

What's pulling them in

  • Unlimited user licensing lets companies add staff without per-seat billing shocks, making Acumatica cost-predictable at scale.
  • Flexibility and scalability earn consistent praise — users value a platform that adapts to vertical workflows without forcing a redesign.
  • Real-time visibility across financials, inventory, and projects gives mid-market businesses a consolidated operational view previously available only in enterprise-tier ERPs.
  • Cloud-native architecture with automatic updates removes infrastructure management burden from in-house IT teams.
  • Modular licensing lets companies start with one or two suites (Financials, Distribution) and expand into Manufacturing or CRM incrementally.

Object mapping

How Selly Erp objects map to Acumatica

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

maps to

Acumatica

Contact (on Customer screen)

1:1
Fully supported

Selly 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

maps to

Acumatica

Customer (or Vendor)

1:1
Fully supported

Selly 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

maps to

Acumatica

Opportunity

1:1
Fully supported

Selly 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

maps to

Acumatica

Sales Order

1:many
Fully supported

Selly 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

maps to

Acumatica

Inventory Item

1:1
Fully supported

Selly 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

maps to

Acumatica

Non-Stock Item

1:many
Fully supported

Selly 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)

maps to

Acumatica

Activity / Note

1:1
Fully supported

Selly 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)

maps to

Acumatica

User-Defined Field on Contact

1:1
Fully supported

Selly 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)

maps to

Acumatica

User-Defined Field on Opportunity

1:1
Fully supported

Selly 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

maps to

Acumatica

Lead (if CRM module active)

1:1
Fully supported

Selly 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

maps to

Acumatica

Files (Attachments on CRM screens)

1:1
Fully supported

Selly 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)

maps to

Acumatica

AR Invoice

1:1
Fully supported

Selly 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.

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.

Selly Erp logo

Selly Erp gotchas

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

Acumatica logo

Acumatica gotchas

High

API user licenses cap concurrent sessions and request throughput

High

Multi-tenant filtering requires CompanyID awareness

Medium

Custom fields require separate discovery before field mapping

Medium

Notes and attachments use a separate linked table structure

Low

Implementation timelines frequently run 3–9 months end-to-end

Pair-specific challenges

  • Selly deal status 'Won' splits to both Opportunity and Sales Order — planning required before migration

    Selly's deal model covers both open-pipeline deals and closed-won orders in a single object. Acumatica separates pipeline tracking (Opportunity) from confirmed transactions (Sales Order → Invoice). During migration, every 'Won' deal requires a decision: does it become a historical Opportunity for pipeline reporting, a closed Sales Order for financial accuracy, or both? FlitStack surfaces this decision point in the pre-migration plan and applies your chosen rule consistently across the dataset before import begins. Failing to pre-define this split causes duplicate records or missing transaction history in Acumatica's financial module.

  • Selly's N:N contact-to-company associations collapse to one CustomerID per contact

    Selly ERP allows a contact to be associated with multiple companies natively. Acumatica's Contact screen links to one primary CustomerID with the ability to add related customers via Contact Business Account Relationships. FlitStack migrates the most-recently-modified or primary company as the Contact's CustomerID and surfaces remaining company associations as a custom RelatedCustomerUDF for manual post-migration linking. Contacts without any company association in Selly land under a default 'Unassigned Customer' record.

  • Selly custom properties require Acumatica UDF pre-creation before import runs

    Selly stores custom contact, company, and deal properties that have no native equivalent in Acumatica. Acumatica's UDF model requires the admin to define each field in the screen configuration before data can be imported into those columns. FlitStack delivers a UDF manifest listing every custom property, its Acumatica data type (String, Decimal, Date, Boolean, List), and which DAC it attaches to. These fields must be created in your Acumatica instance before the migration step runs — FlitStack cannot inject data into fields that do not yet exist in the schema.

  • Selly's per-user pricing means owner emails may not match Acumatica employee emails

    Selly tracks deals and contacts by owner usernames, but those usernames may not correspond to the email addresses used in Acumatica's employee records. FlitStack resolves owner assignments by matching Selly owner email to Acumatica Employee emails first. Records where no match exists are flagged in a pre-flight report and assigned to a fallback employee you designate. Without this resolution, imported records have no OwnerID and appear 'unassigned' in Acumatica's assignment reports.

  • Selly product pricing tiers require Acumatica price-list configuration before orders migrate

    If Selly tracks tiered pricing or customer-specific prices on products, those map to Acumatica's Sales Prices screen. Acumatica requires price lists to be configured per customer class or individually before Sales Order imports can resolve the correct price. FlitStack exports Selly's price data as a CSV alongside the migration and delivers a price-list setup guide. Orders imported before price lists are configured default to the product's base price, which may not match the customer's contracted rate.

Migration approach

Six steps for a successful Selly Erp to Acumatica data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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

Context on both ends of the pair

Selly Erp logo

Selly Erp

Source

Strengths

  • Flat per-user pricing without per-module add-ons keeps costs predictable for SMB teams
  • Covers the full sales cycle from lead capture through invoicing in one subscription
  • Italian-language customer support receives consistently high marks in user reviews
  • Google Workspace integration with Gmail and Google Drive out of the box
  • Suitable for small to mid-sized businesses that do not need enterprise-level customisation depth

Weaknesses

  • No publicly documented API — automated export is not possible without a manual in-app data dump
  • Limited third-party integrations; existing ERP and accounting tools do not connect smoothly
  • Reporting and analytics are functional but lack the depth power users require
  • Customisation for specialist industries requires workarounds rather than native configuration
  • Platform originated in Italy and documentation is primarily in Italian, limiting accessibility for international teams
Acumatica logo

Acumatica

Destination

Strengths

  • Unlimited named-user licensing eliminates per-seat cost scaling as teams grow.
  • Modular architecture lets companies deploy Financials first and add Distribution, Manufacturing, or CRM incrementally.
  • Cloud-native with automatic updates removes infrastructure patching and version management from IT responsibilities.
  • Flexible customization framework (UDFs, extensions) supports vertical-specific workflows without forking core code.
  • Multi-tenant architecture with CompanyID isolation enables safe data segregation across subsidiaries.

Weaknesses

  • Steep learning curve and complex initial setup create significant onboarding friction.
  • Report Designer is widely cited as unintuitive and difficult to use for non-developers.
  • Feature gaps require customizations or third-party add-ons, adding implementation cost and complexity.
  • Implementation timelines frequently exceed initial estimates, especially for multi-module deployments.
  • API rate limits and concurrent session caps are tied to license tier, creating throughput constraints for bulk data operations.

Complexity grading

How hard is this migration?

Standard ERP migration. 1 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 Selly Erp and Acumatica.

  • Object compatibility

    B

    1 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

    Selly Erp: Not publicly documented.

  • Data volume sensitivity

    B

    Selly Erp doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Selly Erp to Acumatica 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 Selly Erp to Acumatica data migrations

Answers to the questions buyers ask most during Selly Erp to Acumatica migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Selly ERP to Acumatica migrations typically complete in 2–4 days for under 10,000 records across contacts, companies, deals, and products. Projects exceeding 100,000 records or requiring multi-entity Acumatica configuration extend to 10–20 days. The longest step is pre-migration UDF creation and Acumatica schema design — the actual data import runs in hours once the schema is validated. Custom field count and deal-split rule definition add planning time before import begins.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Selly Erp.
Land in Acumatica, 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