Migrate from Edara to Microsoft Dynamics 365 Business Central

Edara's chart of accounts maps directly to Dynamics 365 Business Central or Finance G/L Account table. Account Code, Name, Type (Posting, Heading, Total), and Income/Balance account category migrate 1:1. Active versus inactive status is preserved; inactive accounts are created as blocked in Dynamics 365. Exchange gain/loss accounts and rounding accounts require field-level mapping to match the destination's currency handling setup.

Edara Customer records (billing/shipping address, contact info, payment terms, currency assignment) map to Dynamics 365 Customer. The Customer Posting Group from Edara maps to the destination Customer Posting Group, and Customer Pricing Group maps to the equivalent price group. Multi-currency assignments preserve the Edara customer currency as the Dynamics 365 Default Currency Code. Any custom customer properties beyond Edara's standard fields are mapped to custom fields on the Customer table.

Edara Vendor master records including addresses, tax ID numbers, and default payment terms migrate to Dynamics 365 Vendor. Vendor Posting Group maps to the destination equivalent, and we reconcile the open PO balance against the Edara vendor ledger before committing. Duplicate vendor names (common when Arabic and English name variants exist for the same entity) are detected and flagged during reconciliation for manual consolidation before insertion.

Item master records from Edara — SKU, description, unit of measure, cost, price, inventory valuation method, and warehouse assignment — map to Dynamics 365 Item or Product depending on the configured destination (Inventory SKU vs. Product type). Unit-of-measure conversions and the inventory posting group migrate to preserve valuation in the destination cost layer. Any item variants in Edara map to Dynamics 365 Item Variants.

Open receivables are exported from Edara's AR aging report as individual open documents (invoice or credit memo reference, outstanding amount, due date, currency). We map each document to a Dynamics 365 Customer Ledger Entry with the same document type, number, and remaining amount. Reminder level and payment term references are preserved. Open AR documents without a matching customer in the destination are held in a reconciliation queue.

Open payables are exported from Edara's AP aging report as individual vendor open documents. Each maps to a Dynamics 365 Vendor Ledger Entry with document type, number, outstanding amount, due date, and currency preserved. We reconcile the vendor ledger totals against Edara's trial balance before committing open AP to the destination. Currency revaluation setup must be configured in Dynamics 365 before open multi-currency AP documents are inserted.

Open and closed sales orders from Edara migrate to Microsoft Dynamics 365 Sales Order or Sales Invoice depending on fulfillment status at migration time. Line items (item number, quantity, unit price, discount percent) map directly. On the Pro plan the 30,000 monthly transaction cap applies; we detect total order count during discovery and either batch extraction aligned with the billing cycle or recommend an Ultimate-plan export window. The mapping preserves salesperson attribution from Edara as a custom field on the Microsoft Dynamics 365 Sales Header.

Edara purchase orders with vendor assignments and line items migrate to Dynamics 365 Purchase Order or Purchase Invoice. PO approval status is mapped to the Dynamics 365 Released and Pending Approval document states. Receipt records linked to Edara POs are mapped to posted Item Receipt entries in Dynamics 365. Any PO with a linked vendor not yet migrated is held until the vendor record is committed.

Edara warehouse records, stock levels, and bin locations are exported per warehouse and mapped to Dynamics 365 Location records. Multi-warehouse Edara setups map to multiple Dynamics 365 Locations, and stock-on-hand per item per warehouse becomes a Quantity record on the Item tracking page. Negative stock entries are flagged for the customer's inventory manager to resolve before final stock snapshot insertion, as Dynamics 365 defaults to blocking negative inventory postings.

Fixed asset records — acquisition cost, accumulated depreciation, depreciation method, and useful life — migrate to Dynamics 365 Fixed Asset only when Edara's Ultimate-plan asset register is accessible. Pro and Basic customers receive a written discrepancy report between the asset register and the general ledger trial balance, which the customer's accountant resolves before we commit the fixed asset ledger to Dynamics 365. Depreciation method (straight-line, declining balance, sum-of-years digits) maps to the corresponding Dynamics 365 depreciation book setup.

Edara POS register configurations and salesperson assignments do not have a direct Dynamics 365 ERP equivalent because Business Central and Finance do not include a native POS register model. We export register definitions and salesperson attribution from Edara and migrate them as custom fields on the Employee or Salesperson table in Dynamics 365. Dynamics 365 Commerce is the Microsoft-native POS product; if the customer deploys Commerce, the register configuration is rebuilt there as part of a separate implementation rather than a data migration.

Edara's multi-currency exchange rate history is exported alongside transactional data on Pro and above. We import exchange rates into Dynamics 365 Currencies as historical rates matching the Edara transaction dates, enabling closed order and open document amounts to reconvert correctly in the destination reporting currency. Open AR and AP documents carry both the original currency amount and the reporting currency amount to match the Edara ledger.