How long does a Flectra to Acumatica migration take?

A Flectra-to-Acumatica migration with under 50,000 transactional records typically completes in 72–96 hours of active migration time, with 10–18 days of total project time for schema setup, sample migration, and delta pickup. The longest pre-migration step is configuring Acumatica branches, UOM classes, and tax zones — that alone can take 3–5 days if Flectra's multi-company structure requires many branch mappings. Record volumes above 200,000 or complex project-task hierarchies extend the window to 3–4 weeks.

Will my Flectra workflows and automated actions migrate to Acumatica?

No. Flectra workflows, server actions, automated actions, and scheduled actions do not migrate. They are Python/C# code objects in Flectra's ir.actions and ir.rule tables with no direct equivalent in Acumatica's screen-based automation model. Acumatica handles automation through Screen automation (Automation Steps), Business Events, and Push Notifications. FlitStack AI exports your Flectra workflow definitions as a rebuild reference document that your Acumatica consultant can use to recreate the logic in Acumatica's automation framework.

What happens to Flectra CRM leads and pipeline stages in Acumatica?

Flectra CRM leads with status 'won' become Acumatica Customers; leads still in 'new' or 'qualified' status become Acumatica Leads. Flectra pipeline stages map to Acumatica Lead.Source or Lead.Rating depending on what captures the stage intent. If your Flectra CRM module tracks opportunity probability per stage, we preserve those values as a custom field on the Acumatica Lead so your sales team retains stage-to-probability context. Flectra's crm.lead.calendar_event history does not migrate as events — it is exported as a CSV note on the corresponding Lead record.

Can I migrate Flectra custom objects and custom fields to Acumatica?

Yes. Flectra custom objects (created via Settings > Technical > Models) map to Acumatica custom tables registered via a Customization Project. Custom fields on standard Flectra objects (x_ prefix fields) map to Acumatica extension DAC fields with the Usr prefix. FlitStack creates the SQL table schema, registers the DAC in your Acumatica customization project, and loads the data via Import by Scenario. If a custom Flectra field has no Acumatica equivalent, we store the value in a catch-all UsrFlectraCustomData JSON field and flag it for manual review.

How does Flectra's multi-company setup map to Acumatica's branch architecture?

Flectra's multi-company feature stores a separate company_id on each record with independent charts of accounts. Acumatica's branch model is lighter — branches share a single GL but can have separate legal entity reporting. We map each Flectra company to an Acumatica branch, configure the branch's company name and tax registration, and ensure the Flectra chart of accounts aligns with Acumatica's GL structure. If Flectra companies use different fiscal year dates, we map them to separate Acumatica branches with distinct FinPeriodID configurations.

Does the migration affect my Flectra account during cutover?

No. FlitStack AI uses scoped read-only API access to Flectra — your team continues working in Flectra throughout the migration. The delta-pickup window (24–48 hours after the full migration run) captures any records created or modified in Flectra during the cutover period so that Acumatica reflects Flectra's final state at go-live. No write operations are performed against Flectra, and no users are locked out. Flectra can be decommissioned only after Acumatica reconciliation is confirmed.

What happens to Flectra's project tasks and nested sub-tasks?

Flectra project.task supports an arbitrary nesting depth via parent_id, while Acumatica's PMTask table allows a maximum of two levels (parent task and child task). We flatten Flectra's task tree to two levels before loading — top-level Flectra tasks become PMTask records with no parent, and Flectra child tasks become PMTask records linked via ParentTaskID. Flectra grandchild tasks are remapped to the second level with a note field (UsrOrigTaskID) preserving the original Flectra task ID. This requires a planning step to validate the nesting depth before migration runs.

Flectra to Acumatica Migration — Field-Level Mapping & Rollback

Overview

What this migration involves

Flectra and Acumatica share the same high-level ERP module categories — CRM, sales, purchasing, inventory, accounting, projects — but their underlying data models diverge significantly at the field level. Flectra uses snake_case field names (partner_id, sale_order_line_ids, product_uom_qty) derived from its Python object framework, while Acumatica uses PascalCase identifiers (CustomerID, OrderNbr, LineNbr) within a branch-scoped tenant architecture. Flectra models a Contact as a separate res.partner record with a category relationship; Acumatica collapses Customer into a single entity that can represent both a company and an individual, distinguished by the CustomerClassID. Flectra's project.task inherits directly from project.project; Acumatica separates Projects (PM302000) from Tasks (EP304000) into distinct screens with a parent–child link table. FlitStack AI handles all standard record types — Contacts, Companies, Sales Orders, Purchase Orders, Invoices, Products, Projects, Employees — plus Flectra custom objects and custom fields, mapping them to Acumatica custom fields (usr prefix) or extension DAC fields as appropriate. We do not migrate workflows, automated actions, or server-side modules; those must be rebuilt using Acumatica's Screen-based automation or PowerBI reporting layer. The migration runs via a combination of Acumatica's Import by Scenario (for bulk transactional loads) and the Acumatica REST API (for real-time validation and delta pickup), sequenced so that foreign-key dependencies resolve in the correct order: tax categories → inventory items → GL accounts → customers → purchase orders → sales orders → invoices → project tasks.

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.

Object mapping

How Flectra objects map to Acumatica

Each row shows how a Flectra 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.

Flectra

res.partner (company type)

maps to

Acumatica

Customer (AR303010)

1:1

Fully supported

Flectra's company-type res.partner maps to Acumatica Customer. The Acumatica CustomerClassID defaults based on Flectra's partner category (e.g., 'CUSTOMER' vs 'VENDOR'). Primary address from Flectra's partner address record migrates as the Acumatica default address; additional addresses land as Address records linked via AddressID.

Flectra

res.partner (individual type)

maps to

Acumatica

Contact + Customer (AR303010)

many:1

Fully supported

Flectra person-type partners with an email address create an Acumatica Contact record and optionally a Customer record if the individual is billable. The mapping merges Flectra's contact details (phone, email, title) with the partner's address to produce a Contact record linked to the corresponding Customer entity.

Flectra

crm.lead

maps to

Acumatica

Lead / Customer

1:many

Fully supported

Flectra CRM leads with status 'won' map to Acumatica Customers; leads with status 'new' or 'qualified' map to Acumatica Leads. Lost leads are not created in Acumatica but are preserved as a CSV export for reference. Lead source, rating, and expected revenue from Flectra's crm.lead become Lead.Source and Lead.QualifyDate fields.

Flectra

sale.order

maps to

Acumatica

Sales Order (SO301000)

1:1

Fully supported

Flectra sale.order maps to Acumatica Sales Order. OrderNbr uses Flectra's name field as the order reference. The Acumatica branch is determined by Flectra's warehouse_id if set, otherwise defaults from the Acumatica configuration. Order lines map to SOLine with inventory ID lookup, quantity, and UOM from Flectra's sale_order_line.

Flectra

purchase.order

maps to

Acumatica

Purchase Order (PO301000)

1:1

Fully supported

Flectra purchase.order maps to Acumatica Purchase Order. VendorID resolves from Flectra's partner_id (vendor type). PO type (Standard vs Blanket) defaults based on Flectra's po_type field. POLine maps InventoryID or Non-Stock items with the vendor's product SKU preserved as the vendorID cross-reference.

Flectra

account.invoice (customer)

maps to

Acumatica

AR Invoice (AR301000)

1:1

Fully supported

Flectra customer invoices map to Acumatica AR Invoice. The invoice number (Flectra's move_name) becomes the DocNumber; the Flectra journal entry date maps to Acumatica's DocDate and FinPeriodID. Tax amounts from Flectra's invoice_line tax_ids create ARTran entries with the corresponding Acumatica tax zone applied.

Flectra

account.invoice (vendor)

maps to

Acumatica

AP Bill (AP301000)

1:1

Fully supported

Flectra vendor bills map to Acumatica AP Bill. The vendor's Flectra partner_id resolves to an Acumatica Vendor record (AP202000). Bill lines map to APLine with either an InventoryID (for stocked items) or an ExpenseAccrualAccount for services. Prepayments in Flectra become AP Payment applications on the Acumatica side.

Flectra

product.product

maps to

Acumatica

Inventory Item (IN202500)

1:1

Fully supported

Flectra product.product maps to Acumatica Inventory Item. The ItemID uses Flectra's default_code as the primary key. Item Class from Flectra's categ_id maps to Acumatica's ItemClassID. Costing method (standard, average, FIFO) is set per Acumatica inventory item based on Flectra's valuation field; UOM conversions are preserved via the Acumatica UOM class.

Flectra

project.project

maps to

Acumatica

Project (PM302000)

1:1

Fully supported

Flectra project.project maps to Acumatica Project. The ProjectCD is derived from Flectra's project code or name. Project template flags from Flectra (use_tasks, billing_type) translate to Acumatica's Allow Billable flag and Project Type. Non-billable projects set Non-Project = TRUE in Acumatica.

Flectra

project.task

maps to

Acumatica

Project Task (PM304000)

1:1

Fully supported

Flectra project.task is a sub-record of project.project; Acumatica stores tasks separately. Each Flectra task becomes an Acumatica PMTask record linked to the corresponding ProjectID. Task IDs from Flectra are preserved in PMTask.Note with a cross-reference to Flectra's task ID for traceability. Parent-child task hierarchies in Flectra map to PMTask.TaskCD parent links in Acumatica.

Flectra

stock.picking

maps to

Acumatica

Shipment / Receipt (SO302000 / PO302000)

1:1

Fully supported

Flectra outgoing stock.picking maps to Acumatica Shipments (SO302000); incoming picking maps to Receipts (PO302000). The picking state (done, draft, cancel) maps to Acumatica status (Balanced, On Hold, Cancelled). Lot/serial numbers from Flectra's stock_move_line transfer as Acumatica LotSerialNbr on the corresponding shipment line.

Flectra

account.move (journal entries)

maps to

Acumatica

Journal Transaction (GL301000)

1:1

Fully supported

Flectra account.move maps to Acumatica GL Journal. The Flectra move name becomes the BatchNbr. Each Flectra move_line maps to an Acumatica GLTran entry with the AccountCD, Sub, DebitAmt, and CuryDebitAmt fields populated. Branch is determined by Flectra's company_id or the journal's default branch.

Flectra

hr.employee

maps to

Acumatica

Employee (EP301000)

1:1

Fully supported

Flectra hr.employee maps to Acumatica Employee. EmployeeID is derived from Flectra's work_email or employee number. Department from Flectra's department_id maps to Acumatica's Department. Employment status (active, terminated) translates to the Employee.Status field. Compensation data is preserved as custom fields if the source data exists.

Flectra

stock.location

maps to

Acumatica

Warehouse / Location (IN204000)

1:1

Fully supported

Flectra stock.location maps to Acumatica Warehouse (or Location within a Warehouse). The Flectra location_type (internal, partner, inventory) determines whether this becomes an Acumatica Warehouse or a Location under an existing Warehouse. Multi-company Flectra locations with separate companies require Acumatica branch mapping.

Flectra

Flectra Custom Object (x_ model)

maps to

Acumatica

Acumatica Custom Table / DAC Extension

1:1

Fully supported

Flectra custom models (created via Settings > Technical > Models) map to Acumatica custom tables via a Customization Project. FlitStack creates the SQL table, registers it as a DAC in the Acumatica project, and loads the data via Import by Scenario. Relationships to standard entities (Customer, Vendor) use Acumatica's key field reference pattern.

Flectra	Acumatica	Compatibility
res.partner (company type)	Customer (AR303010)1:1	Fully supported
res.partner (individual type)	Contact + Customer (AR303010)many:1	Fully supported
crm.lead	Lead / Customer1:many	Fully supported
sale.order	Sales Order (SO301000)1:1	Fully supported
purchase.order	Purchase Order (PO301000)1:1	Fully supported
account.invoice (customer)	AR Invoice (AR301000)1:1	Fully supported
account.invoice (vendor)	AP Bill (AP301000)1:1	Fully supported
product.product	Inventory Item (IN202500)1:1	Fully supported
project.project	Project (PM302000)1:1	Fully supported
project.task	Project Task (PM304000)1:1	Fully supported
stock.picking	Shipment / Receipt (SO302000 / PO302000)1:1	Fully supported
account.move (journal entries)	Journal Transaction (GL301000)1:1	Fully supported
hr.employee	Employee (EP301000)1:1	Fully supported
stock.location	Warehouse / Location (IN204000)1:1	Fully supported
Flectra Custom Object (x_ model)	Acumatica Custom Table / DAC Extension1:1	Fully supported

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.

Flectra gotchas

High

XML-RPC API format requires non-standard serialization

High

No official migration utility or dedicated export tooling

Medium

Community edition lacks functional support and hosting

Medium

Large imports can trigger timeouts without batching

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

Flectra gotchas		Acumatica gotchas
Severity	Issue	Severity	Issue
High	XML-RPC API format requires non-standard serialization	High	API user licenses cap concurrent sessions and request throughput
High	No official migration utility or dedicated export tooling	High	Multi-tenant filtering requires CompanyID awareness
Medium	Community edition lacks functional support and hosting	Medium	Custom fields require separate discovery before field mapping
Medium	Large imports can trigger timeouts without batching	Medium	Notes and attachments use a separate linked table structure
		Low	Implementation timelines frequently run 3–9 months end-to-end

Pair-specific challenges

Branch scoping requires pre-migration topology planning

Acumatica's branch model is not optional — every transactional record (Orders, Invoices, Journal Entries) must be assigned to a BranchID. Flectra's multi-company setups store company_id on each record, but Acumatica's branch is a lighter entity tied to the GL rather than a full duplicate chart of accounts. Teams that skip branch planning end up with all migrated data landing in a single default branch, which breaks Acumatica's branch-level financial reporting and may conflict with the configured financial year. We deliver a branch-mapping plan before migration that assigns each Flectra company_id to an Acumatica branch and ensures the branch's fiscal year and base currency are compatible with the source data.
Flectra's UOM and product variant model requires pre-mapping to Acumatica's item class

Flectra's product.product stores UOM on the order line without a structured UOM class; different UOMs per product variant are handled via sale.order.line.product_uom. Acumatica requires a UOM class linked to the inventory item — without it, order lines fail validation. If Flectra products use multiple UOMs (eaches, cases, pallets) without a defined UOM class in Acumatica, the migration flags those items and loads them as Non-Stock items until an Acumatica admin defines the UOM class. This is a pre-migration schema step, not a data transformation.
Tax mapping requires Acumatica tax zone configuration before invoice migration

Flectra stores taxes on invoice lines as account.tax records with tax_group_id for tax groups. Acumatica's tax engine applies a TaxZoneID at the document header and resolves tax lines automatically. If the Acumatica Tax Zones (TX102000) have not been configured to match Flectra's tax groups, invoice migrations will create lines with zero tax or throw validation errors. We surface the tax zone gap before migration starts and can pre-configure Acumatica tax zones from Flectra's tax data as an optional add-on.
Flectra's project.task hierarchy needs flattening before Acumatica PMTask load

Flectra project.task is embedded within project.project and supports nested sub-tasks via parent_id. Acumatica's PMTask table is flat — sub-tasks link via PMTask.ParentTaskID. Flectra tasks with more than two levels of nesting (grandchild tasks) exceed Acumatica's two-level PMTask hierarchy. We extract Flectra's task tree, flatten it to a maximum of two levels, and map deeply nested Flectra tasks to PMTask.TaskCD with a cross-reference note. The planning step validates the nesting depth before the migration runs.
Numbering sequences must be pre-created in Acumatica to avoid duplicate DocNumber errors

Flectra uses its own sequence logic (sale.order, account.move) for document numbering, often with custom prefixes. Acumatica's numbering sequences (SM200540) must exist before Import by Scenario loads documents. If a Flectra invoice number (e.g., INV-2024-00142) collides with an existing Acumatica sequence value, the import fails for that record. We set up Acumatica numbering sequences to match Flectra's format before bulk load, or we use the 'User Numbering' override in Import by Scenario to write Flectra's original document numbers directly.

Migration approach

Six steps for a successful Flectra to Acumatica data migration

Inventory Flectra schema and build Acumatica destination plan

FlitStack AI reads Flectra's object model via its XML-RPC API and exports the full schema including custom fields, custom objects, and relationship metadata. We cross-reference each Flectra object against Acumatica's standard DACs and identify gaps. For each gap, we write an Acumatica Customization Project specification: which custom fields (Usr-prefixed) need to be created, which Acumatica branches need to be provisioned, and which numbering sequences need to be defined. This plan is reviewed with your Acumatica admin before any data moves.
Create branches, UOM classes, tax zones, and numbering sequences

With the Acumatica destination plan in hand, your Acumatica admin (or FlitStack on your behalf) creates the required branches in GL102000, UOM classes in IN202000, tax zones in TX102000, and numbering sequences in SM200540. Custom fields are published via a Customization Project. This step runs in parallel with Flectra data extraction so the destination schema is ready before the first import batch runs.
Extract, cleanse, and sequence Flectra data in foreign-key order

FlitStack extracts Flectra data in a strict load order: tax categories → inventory items → GL accounts → UOM classes → customers and vendors → contacts → purchase orders → sales orders → AR/AP invoices → project headers → project tasks → employee records → journal entries. This ordering ensures that when a sales order line references an InventoryID, that inventory item already exists in Acumatica. We apply data cleansing rules: deduplicating partner records by email, normalizing country codes to ISO, and resolving Flectra analytic_account_id references to Acumatica subaccounts.
Run sample migration with field-level diff on a representative record slice

A sample of 200–500 records — spanning customers, sales orders, invoices, and project tasks — is migrated first via Acumatica's Import by Scenario. FlitStack generates a field-level diff comparing source values against the destination values for each record, covering all mapped fields and documenting any fields that could not be mapped (e.g., Flectra custom fields with no Acumatica equivalent). You review the diff and approve the mapping before the full run commits.
Execute full migration with delta-pickup window and rollback readiness

The full migration runs against the configured Acumatica tenant. A delta-pickup window (typically 24–48 hours) begins at cutover and captures any Flectra records modified or created during the final hours of dual operation. All operations are logged in a FlitStack audit record. If reconciliation identifies missing or mismatched records, one-click rollback reverts the Acumatica tenant to its pre-migration state so the migration can be re-run with corrected mappings.

Platform deep dives

Context on both ends of the pair

Flectra

Source

Strengths

Community edition is free with no per-user licensing cost, removing financial barrier to adoption.
On-premise hosting option provides full data sovereignty for regulated-industry customers.
Modular architecture means customers deploy only the modules they need, reducing system complexity.
XML-RPC External API allows programmatic data access across all business objects via standard ORM methods.
Open-source codebase can be audited and extended by the customer's own developers without vendor dependency.

Weaknesses

Community edition receives no security patches or version upgrades from the vendor, creating long-term maintenance risk.
XML-RPC API is less widely documented and supported by third-party integration tools compared to REST alternatives.
Smaller community and partner ecosystem than Odoo means fewer pre-built modules and fewer implementation consultants.
Performance on large datasets (100k+ records) is not optimised without significant infrastructure tuning.
Version upgrade path for on-premise installations requires manual testing of all custom modules for compatibility.

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.

	Flectra Source	Acumatica Destination
Strengths	Community edition is free with no per-user licensing cost, removing financial barrier to adoption. On-premise hosting option provides full data sovereignty for regulated-industry customers. Modular architecture means customers deploy only the modules they need, reducing system complexity. XML-RPC External API allows programmatic data access across all business objects via standard ORM methods. Open-source codebase can be audited and extended by the customer's own developers without vendor dependency.	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	Community edition receives no security patches or version upgrades from the vendor, creating long-term maintenance risk. XML-RPC API is less widely documented and supported by third-party integration tools compared to REST alternatives. Smaller community and partner ecosystem than Odoo means fewer pre-built modules and fewer implementation consultants. Performance on large datasets (100k+ records) is not optimised without significant infrastructure tuning. Version upgrade path for on-premise installations requires manual testing of all custom modules for compatibility.	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.

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

Migrate from Flectra to Acumatica

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

Flectra

Acumatica

How Flectra objects map to Acumatica

What specifically takes care here

Six steps for a successful Flectra to Acumatica data migration

Context on both ends of the pair

How hard is this migration?

Estimate your Flectra to Acumatica migration cost

What are you migrating?

Frequently asked questions about Flectra to Acumatica data migrations

Can't find your answer?

Related migrations to explore

Move from Flectra.
Land in Acumatica, intact.

Migrate from Flectra to Acumatica

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

Flectra

Acumatica

How Flectra objects map to Acumatica

What specifically takes care here

Six steps for a successful Flectra to Acumatica data migration

Context on both ends of the pair

How hard is this migration?

Estimate your Flectra to Acumatica migration cost

Frequently asked questions about Flectra to Acumatica data migrations

Can't find your answer?

How long does a Flectra to Acumatica migration take?

Will my Flectra workflows and automated actions migrate to Acumatica?

What happens to Flectra CRM leads and pipeline stages in Acumatica?

Can I migrate Flectra custom objects and custom fields to Acumatica?

How does Flectra's multi-company setup map to Acumatica's branch architecture?

Does the migration affect my Flectra account during cutover?

What happens to Flectra's project tasks and nested sub-tasks?

Related migrations to explore

Move from Flectra. Land in Acumatica, intact.

Move from Flectra.
Land in Acumatica, intact.