How long does a Merci to Acumatica migration take?

A Merci to Acumatica migration with under 25,000 records typically completes in 5–10 business days: 1–2 days for data extraction and schema setup, 2–3 days for validation and sample migration, and 2–5 days for the full load with delta-pickup and GL posting. Multi-entity Merci configurations, high transaction counts (100,000+ records), or fixed asset history requiring depreciation schedule carry-forward extend timelines to 3–6 weeks. Acumatica's consumption-based subscription means we also coordinate migration with your Acumatica tenant provisioning timeline.

Will my Merci workflows and approval rules migrate to Acumatica?

No. FlitStack AI migrates data only — Merci workflows, approval chains, document routing rules, and conditional automation logic do not transfer to Acumatica. These constructs are destination-side configuration, not data. We export Merci's workflow definitions as a structured rebuild reference so your Acumatica implementation partner can reconstruct the logic in Acumatica's Screens (Rapport), custom code, or third-party workflow tools. Approval rules in particular require Acumatica configuration under Financial Settings (AP101000 / AR101000) before documents can route correctly.

What happens to my Merci customer and vendor balances in Acumatica?

Merci open AR balances migrate to Acumatica as unposted invoices in the AR subledger; open AP balances migrate as unposted bills in the AP subledger. Closed historical invoices become read-only Cash Sales (AR304000) and Vendor Credit Memos preserving original amounts and payment dates. The trial balance reconciliation compares Merci's AR/AP totals against Acumatica's subledger totals — any discrepancy above 0.01% triggers a rollback until the variance is resolved. Customer credit limits and payment terms migrate as fields on the Customer and Vendor records.

Can I migrate Merci inventory items to Acumatica with historical valuation data?

Merci inventory items migrate to Acumatica Stock Items or Non-Stock Items with current on-hand quantities and average or standard cost. Historical valuation layers (FIFO layers, specific identification lots) require Acumatica's Inventory Valuation module to be licensed and configured — if Merci used FIFO, we map layer-by-layer; if Merci used average cost, we carry the weighted average as the opening average cost. Acumatica's real-time valuation posts on each transaction post-migration; Merci's historical cost layer data is preserved as opening balance entries for audit continuity.

How does Acumatica's migration mode affect my cutover?

Acumatica's Migration Mode must be activated before any bulk document import — when enabled, imported AR invoices, AP bills, and PO receipts hold in pending status without posting to the General Ledger. This prevents double-posting when you deactivate migration mode and documents batch-post. We coordinate Migration Mode activation with your GL close timeline to ensure the cutover period aligns with a closed accounting period. Your team continues working in Merci throughout Migration Mode; a delta-catchup batch captures any new records created during the transition window.

What happens to Merci fixed assets in Acumatica?

Merci fixed assets migrate to Acumatica Fixed Asset records with acquisition date, cost, salvage value, and depreciation method. The key carry-forward is accumulated depreciation — we map Merci's accumulated depreciation to the Acumatica Fixed Asset's accumulated depreciation balance rather than resetting it to zero. Depreciation method (straight-line, declining balance, units of production) maps to the matching Acumatica method. Mid-quarter acquisitions and partial-year conventions are preserved as the depreciation start date. Your Acumatica admin must create Fixed Asset Classes (FA201000) before assets can import.

Will Merci's document numbering system carry over to Acumatica?

Merci allows the same document number to appear in different modules — Invoice #1001 and PO #1001 coexist. Acumatica enforces globally unique RefNbr values across all screens. To prevent numbering collisions during migration, we prefix Merci document numbers with their source module code (AR-1001, PO-1001, SO-1001). This preserves traceability back to the original Merci document number. After migration, your Acumatica admin can renumber documents through the Numbering Sequences screen (CS201000) if a cleaner numbering scheme is preferred.

Does the migration affect my Merci account during cutover?

No. FlitStack AI connects to Merci via scoped read-only API access during the migration — your team retains full access to Merci for ongoing operations. A delta-catchup window runs concurrently with the cutover, capturing any records created or modified in Merci during the migration window. When you are ready to switch to Acumatica as your live system, the delta batch lands in Acumatica before Migration Mode deactivates and documents post to the GL.

MERCI to Acumatica Migration — Field-Level Mapping & Rollback

Overview

What this migration involves

Merci Cloud ERP positions itself as an affordable, AWS-hosted all-in-one for SMBs covering CRM, financials, and operations. Acumatica uses a consumption-based licensing model tied to transaction volume rather than user count, making it attractive for growing companies with seasonal or expanding workforces. The fundamental migration challenge is reconciling Merci's flat, integrated object model against Acumatica's modular architecture where Financial Management, Distribution, and Project Accounting are separate application tiers with independent configuration. We extract Merci data via its REST API, map customer records to Acumatica Customers (AR303000), vendor records to Acumatica Vendors (AP303000), inventory items to Stock Items (IN202000), and open invoices to the appropriate subledger entry points. Closed historical transactions migrate as read-only audit records. Workflows, approval chains, and custom formulas embedded in Merci cannot migrate — we export those definitions as rebuild documentation for your Acumatica implementation partner. A delta-pickup window runs concurrent with cutover to capture in-flight transactions, and one-click rollback reverts the Acumatica environment to its pre-migration state if reconciliation fails.

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 MERCI objects map to Acumatica

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

MERCI

Customer

maps to

Acumatica

Customer (AR303000)

1:1

Fully supported

Merci customers map directly to Acumatica Customers. The key translation is Merci's customer class becoming Acumatica's Customer Class (AR2010). Shipping addresses migrate to Acumatica address records; multi-contact customers require individual Contact records linked via the Customer ID. Tax registration IDs and credit limits transfer as Customer attributes. All customer mappings are validated against Acumatica's required field constraints before import.

MERCI

Vendor

maps to

Acumatica

Vendor (AP303000)

1:1

Fully supported

Merci vendors map to Acumatica Vendors. Merci's vendor class maps to Acumatica's Vendor Class. 1099 vendor type flags translate to the Tax ID tab in Acumatica. Remit-to addresses become alternate address records in Acumatica's address section. Payment terms and 1099 reporting settings transfer as vendor attributes and are validated during import.

MERCI

Item / Product

maps to

Acumatica

Non-Stock Item / Stock Item (IN202000)

1:1

Fully supported

Merci items require classification: inventory-tracked items become Acumatica Stock Items with warehouse/bin assignments; non-inventory items become Non-Stock Items.Merci's item class hierarchy maps to Acumatica's Item Class (CL) and Inventory ID segment. Pack/Unit of Measure conversions require explicit UOM setup in Acumatica.

MERCI

Sales Order

maps to

Acumatica

Sales Order (SO301000)

1:1

Fully supported

Open Merci sales orders migrate to Acumatica Sales Orders with order type mapping. Merci's order status workflow (Draft, Confirmed, Shipped) maps to Acumatica's Status field. Historical closed orders migrate as SO Invoice History records — they appear in reporting but cannot be modified in Acumatica.

MERCI

Purchase Order

maps to

Acumatica

Purchase Order (PO301000)

1:1

Fully supported

Open Merci purchase orders migrate to Acumatica Purchase Orders. Merci's PO approval workflow does not transfer — Acumatica's approval setup must be configured separately. Received-not-invoiced lines require specific attention: Merci's receipt quantity must map to Acumatica's Receipts, and accrued liability accounts must be mapped to the correct AP account.

MERCI

Invoice (AR)

maps to

Acumatica

Invoice (AR301000) / Cash Sale (AR304000)

1:many

Fully supported

Merci AR invoices split into two Acumatica paths: open invoices become AR Invoices with correct due dates and terms; paid invoices become Cash Sales preserving payment history. Merci's invoice aging buckets map to Acumatica's Terms. Multi-currency invoices require currency code and exchange rate preservation in the Acumatica record.

MERCI

Invoice (AP)

maps to

Acumatica

Bill (AP301000)

1:1

Fully supported

Merci AP bills migrate to Acumatica Bills. Open bills carry balance due; paid bills migrate as historical records. Merci's 3-way matching flags (PO-Receipt-Invoice) require manual verification in Acumatica since Acumatica handles matching through its own workflow. Vendor credits become Acumatica Vendor Refunds/Credit Memos.

MERCI

Project

maps to

Acumatica

Project (PM301000)

1:1

Fully supported

Merci projects with time/billing tracking map to Acumatica Projects. Project status (Active, Completed, On Hold) translates directly. Merci's project phases map to Acumatica Task codes. If Merci tracks project profitability, those amounts become initial Project Budget records in Acumatica. Project-specific billing settings and rate tables transfer as project attributes.

MERCI

Fixed Asset

maps to

Acumatica

Fixed Asset (FA202000)

1:1

Fully supported

Merci fixed assets migrate to Acumatica Fixed Asset records. Asset class, acquisition date, cost, and depreciation method must map explicitly — Acumatica's Fixed Asset module supports mid-quarter acquisitions and partial-year depreciation that Merci may not. GL account assignments for each asset component require manual verification against the destination chart of accounts.

MERCI

Employee

maps to

Acumatica

Employee (EP301000)

1:1

Fully supported

Merci employee records with active status migrate to Acumatica Employees for use in Project Time tracking and payroll integration (if applicable). Inactive/terminated employees migrate with status preserved for historical project reference. Salary information migrates only if the destination uses Acumatica Payroll — otherwise the field is left blank.

MERCI

Custom Field

maps to

Acumatica

User-Defined Field (UDF) / Custom Field

1:1

Fully supported

Merci custom fields on any object require Acumatica User-Defined Field creation before data loads. UDFs in Acumatica are defined per screen (e.g., Customer Details screen) via the Customization -> User-Defined Fields menu. The migration plan documents each custom field's Merci label, data type, and pick-list values so Acumatica-side configuration is pre-built before migration runs.

MERCI

Workflow / Approval Rule

maps to

Acumatica

Not Migrated — Export for Rebuild

1:1

Fully supported

Merci workflows, approval chains, document routing rules, and conditional logic are not migratable. These are destination-side automation constructs. We export Merci's workflow definitions as configuration documentation and recommend your Acumatica partner rebuild them using Acumatica Screens (Rapport) or custom code.

MERCI	Acumatica	Compatibility
Customer	Customer (AR303000)1:1	Fully supported
Vendor	Vendor (AP303000)1:1	Fully supported
Item / Product	Non-Stock Item / Stock Item (IN202000)1:1	Fully supported
Sales Order	Sales Order (SO301000)1:1	Fully supported
Purchase Order	Purchase Order (PO301000)1:1	Fully supported
Invoice (AR)	Invoice (AR301000) / Cash Sale (AR304000)1:many	Fully supported
Invoice (AP)	Bill (AP301000)1:1	Fully supported
Project	Project (PM301000)1:1	Fully supported
Fixed Asset	Fixed Asset (FA202000)1:1	Fully supported
Employee	Employee (EP301000)1:1	Fully supported
Custom Field	User-Defined Field (UDF) / Custom Field1:1	Fully supported
Workflow / Approval Rule	Not Migrated — Export for Rebuild1: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.

MERCI gotchas

High

No public API documentation found

Medium

Single-tenant schema variation across deployments

Medium

Binary attachment export not supported via API

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

MERCI gotchas		Acumatica gotchas
Severity	Issue	Severity	Issue
High	No public API documentation found	High	API user licenses cap concurrent sessions and request throughput
Medium	Single-tenant schema variation across deployments	High	Multi-tenant filtering requires CompanyID awareness
Medium	Binary attachment export not supported via API	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

Migration mode must be activated before bulk imports or GL balances shift

Acumatica's Migration Mode setting (AR101000 / AP101000) prevents imported documents from posting to the General Ledger during the data load phase. Documents added in migration mode hold in pending status — once migration mode is deactivated, they post to GL in a single batch. Skipping this step causes duplicate postings when historical invoices are imported then manually posted. We coordinate migration mode activation with your GL cleanup timeline to avoid an open period mismatch.
Merci's flat customer-vendor model collides with Acumatica's separate AR/AP subledgers

Merci treats Customers and Vendors as distinct records but uses a unified contact model — a company can be both a customer and a vendor without separate classification. Acumatica maintains strict AR and AP subledgers requiring the same entity to exist as both a Customer (AR303000) and a Vendor (AP303000) with matching identifiers. We run a de-duplication pass before migration: entities appearing in both Merci tables generate both Acumatica records with cross-reference notes in the migration audit log.
Merci document IDs cannot be guaranteed unique across all modules — Acumatica numbering is global

Merci allows the same document number to exist in separate modules (e.g., Invoice #1001 and PO #1001 coexist). Acumatica enforces globally unique RefNbr across all transaction screens, which prevents any duplicate document identifiers from existing in the system at any time. Our pre-migration numbering analysis prefixes source module codes onto Merci document numbers (AR-1001, PO-1001) to avoid collision while maintaining traceability back to the original Merci identifier. You can override this in the Acumatica Numbering Sequences screen post-migration if you prefer re-numbering your documents to a cleaner scheme.
Merci's fixed asset depreciation history requires a GL carry-forward schedule

If Merci has recorded multiple years of depreciation on existing assets, Acumatica's Fixed Asset module requires a depreciation starting point. importing current net book value as the acquisition cost discards accumulated depreciation history needed for tax and audit reporting. We map Merci's accumulated depreciation to a separate Acumatica asset record for audit trail purposes and configure the depreciation start date to the period following the last Merci depreciation run.
Acumatica's resource tier pricing means migration scope affects your first renewal bill

Acumatica's consumption-based model charges based on transaction volume tier — not user count. If your Merci database contains high transaction counts (10,000+ invoices/year, heavy inventory movement), your Acumatica subscription tier will reflect that activity level at first renewal. We provide a pre-migration transaction count report so you can model the expected Acumatica tier before signing your subscription agreement, avoiding a billing surprise 12 months post-migration. This report includes invoice counts, order volumes, and inventory transactions to help you budget accurately.

Migration approach

Six steps for a successful MERCI to Acumatica data migration

Scope Merci data and configure Acumatica schema

We extract a full data dump from Merci via its REST API: Customers, Vendors, Items, open Orders, open Invoices, Bills, Projects, Fixed Assets, and Employee records. Simultaneously, your Acumatica admin (or our team) creates the matching object structure — Customer Classes, Vendor Classes, Item Classes, Numbering Sequences, Terms codes, and UDF fields for any Merci custom properties. We deliver a schema readiness checklist before any data movement begins.
Clean and validate Merci data against Acumatica constraints

Merci data passes through a validation engine: required fields are checked (CustomerID, VendorID, InventoryID presence), cross-references are verified (Items exist before Orders reference them, Customers exist before Invoices reference them), and Merci's multi-currency amounts are checked against the destination currency code list. Duplicate detection flags entities appearing in both AR and AP ledgers for Acumatica dual-record creation. Validation errors surface in a runbook with fix instructions — you correct in Merci or we apply a mapping override.
Activate Acumatica Migration Mode and run a sample import

We activate Migration Mode in Acumatica (AR101000, AP101000, PO101000 as applicable) to prevent GL postings during the load phase. A representative slice — typically 50–100 records across Customers, Vendors, Items, and 5–10 open documents — imports first. A field-level diff compares source values against the Acumatica database records so you can verify the mapping before committing the full dataset. This validation step catches data type mismatches, missing required fields, and incorrect value mappings before the full migration begins.
Full data migration with delta-pickup

The complete Merci dataset loads into Acumatica. Transactional records (Orders, Invoices, Bills) load in document-date order to preserve aging accuracy. Fixed Assets load after the opening GL balances are set. During the full load window, a delta capture runs continuously against Merci — any records created or modified in Merci during migration land in a catch-up batch before Migration Mode is deactivated.
Deactivate Migration Mode and post to GL

Once delta-pickup is complete, we deactivate Migration Mode. All pending documents post to the General Ledger in a single batch. We run a reconciliation report comparing Merci's trial balance against Acumatica's GL — accounts payable, accounts receivable, inventory, and fixed asset balances must match within tolerance. If reconciliation fails, one-click rollback reverts the Acumatica environment to pre-migration state. On approval, Migration Mode is fully off and Acumatica is ready for live use.

Platform deep dives

Context on both ends of the pair

MERCI

Source

Strengths

All-in-one platform consolidates sales, CRM, financials, and operations into a single database
Cloud-hosted on AWS with automated backups and automatic failover systems
SLA commitment of 99.9% uptime as stated on their public materials
Single-tenant deployment model keeps customer data isolated per installation
Affordable positioning targets SMBs seeking to replace fragmented point solutions

Weaknesses

No publicly documented API — migration relies on CSV exports or direct database access
Single-tenant model means each deployment has a unique schema, requiring per-instance mapping
Limited industry-specific functionality compared to vertical ERPs
Small vendor footprint makes support responsiveness and long-term viability less certain
No published pricing tiers or transparent cost structure in public sources

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.

	MERCI Source	Acumatica Destination
Strengths	All-in-one platform consolidates sales, CRM, financials, and operations into a single database Cloud-hosted on AWS with automated backups and automatic failover systems SLA commitment of 99.9% uptime as stated on their public materials Single-tenant deployment model keeps customer data isolated per installation Affordable positioning targets SMBs seeking to replace fragmented point solutions	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	No publicly documented API — migration relies on CSV exports or direct database access Single-tenant model means each deployment has a unique schema, requiring per-instance mapping Limited industry-specific functionality compared to vertical ERPs Small vendor footprint makes support responsiveness and long-term viability less certain No published pricing tiers or transparent cost structure in public sources	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 MERCI 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

MERCI

Acumatica

How MERCI objects map to Acumatica

What specifically takes care here

Six steps for a successful MERCI to Acumatica data migration

Context on both ends of the pair

How hard is this migration?

Estimate your MERCI to Acumatica migration cost

What are you migrating?

Frequently asked questions about MERCI to Acumatica data migrations

Can't find your answer?

Related migrations to explore

Move from MERCI.
Land in Acumatica, intact.

Migrate from MERCI 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

MERCI

Acumatica

How MERCI objects map to Acumatica

What specifically takes care here

Six steps for a successful MERCI to Acumatica data migration

Context on both ends of the pair

How hard is this migration?

Estimate your MERCI to Acumatica migration cost

Frequently asked questions about MERCI to Acumatica data migrations

Can't find your answer?

How long does a Merci to Acumatica migration take?

Will my Merci workflows and approval rules migrate to Acumatica?

What happens to my Merci customer and vendor balances in Acumatica?

Can I migrate Merci inventory items to Acumatica with historical valuation data?

How does Acumatica's migration mode affect my cutover?

What happens to Merci fixed assets in Acumatica?

Will Merci's document numbering system carry over to Acumatica?

Does the migration affect my Merci account during cutover?

Related migrations to explore

Move from MERCI. Land in Acumatica, intact.

Move from MERCI.
Land in Acumatica, intact.