Migrate from ORCA Financial to Microsoft Dynamics 365 Business Central

ORCA Financial stores a flat or hierarchical COA with account codes, types, and optional custom segments. We map each ORCA account to a D365 General Ledger account, flagging any multi-segment structure (e.g., cost-center or department splits) that requires D365 Financial Dimensions configuration post-migration. Posting groups defined in ORCA map to D365 posting group templates for customers, vendors, and items.

ORCA Customer records include billing address, payment terms, and contact info. We map to D365 Customer (CustTable in D365 FO; Customer page in Business Central), preserving payment terms, credit limits, and the primary contact email. Custom fields in ORCA that have no direct D365 equivalent are held as a flag list for the customer's admin to map post-import.

ORCA Vendor records mirror Customer in structure. We map to D365 Vendor (VendTable in D365 FO; Vendor page in Business Central). Remittance addresses and multi-site vendor records are flagged as requiring post-migration manual review. Post limitations: D365 requires that at least one purchase order or invoice exist against a vendor before that vendor's balance is active in the ledger.

ORCA Item records include SKU, description, unit cost, and warehouse location. We map to D365 Released Product (D365 FO) or Item (Business Central). Inventory valuation method (FIFO, Standard, Moving Average, Weighted Average) is captured at item level and flagged for costing version configuration in D365 before stock transactions are posted. Stock quantities are migrated as open inventory balances rather than full transaction history.

Open AP records (vendor name, invoice number, amount, due date, invoice date) are exported as a reconciliation-ready table. We post them to the D365 Vendor Invoice Journal (or AP Ledger) with invoice date preserved and the original vendor reference maintained. Historical paid invoices are migrated as closed records and do not reopen in D365.

Open AR records (customer name, invoice number, amount, due date, invoice date) are exported separately for the AR team to verify post-migration. We post them to D365 Customer Invoice Journal (or AR Ledger) with invoice date and due date preserved. Unapplied payments and credit memos migrate as linked adjustments against the open invoice records.

ORCA warehouse location records (location code, address, and warehouse-level stock) map to D365 Warehouse records. Bin-level location assignments inside warehouses are flagged as a manual post-migration step because bin structures in D365 require activation and configuration per warehouse site.

ORCA User records include name, email, and role. We export a user roster and map role names to D365 Security Roles (Business Central) or Security Roles and Duties (D365 Finance & Operations). User provisioning in D365 requires an Azure Active Directory account; we coordinate with the customer's admin to map ORCA role assignments to the appropriate D365 license tier (Team Member, Essentials, Premium) before migration.

ORCA Financial bundles a CRM module. Contact records migrate to D365 Contact (Business Central) or the Contact entity in D365 Sales/Finance. If the ORCA contact has an associated open invoice, it maps to a Customer record; if it is only a relationship contact, it maps to Contact with no account link.

If ORCA holds open sales orders or purchase orders at migration time, these migrate to D365 Sales Order or Purchase Order with line items, quantities, and pricing preserved. D365 validates that the customer or vendor on the order exists and that inventory is available or that drop-ship is configured. Completed orders migrate as invoiced records.

If ORCA Financial holds fixed asset records (acquisition date, depreciation method, book value), these migrate to D365 Fixed Asset records. Depreciation methods map to D365 depreciation profiles (Straight-line, Declining Balance, etc.). Accumulated depreciation is posted as a separate journal entry against the asset book.

ORCA Financial stores binary attachments against transactions and master records, but storage formats are undocumented and file-size constraints are unspecified. We export a manifest of attachment references (file name, record association, approximate size) but do not migrate binary content. The manifest is handed to the customer's admin to manually relocate or re-attach files in D365 SharePoint or Dataverse post-migration.