Migrate from Foundry Bean to Microsoft Dynamics 365 Business Central

Foundry Bean accounts organized into Balance Sheet and Income Statement categories map directly to Business Central G/L Account records. Each account code and type (Asset, Liability, Equity, Revenue, Expense) maps to the destination chart, preserving Foundry Bean's automatic categorization. We map account codes explicitly and flag any custom account types that require Business Central account type configuration before import.

Foundry Bean customer records include addresses, contacts, payment terms, and are linked to invoices and receivables. Standard fields migrate cleanly. Custom fields require explicit value mapping between Foundry Bean's property names and Business Central's field structure. Customer posting groups must be configured in Business Central before import to enable correct receivables posting.

Foundry Bean vendor master records contain addresses, banking information, purchase orders, terms, and contracts. We preserve the full vendor lifecycle linkage to purchase orders and payable records during migration. Vendor posting groups in Business Central are configured before migration to enable correct payables posting. Banking information maps to Business Central vendor bank accounts.

Foundry Bean employee records include compensation history, benefits, and organizational assignments. Effective-dated changes require careful sequencing; we import current state first, then apply historical compensation records as journal entries or supplemental pay records. Employee dimensions and cost center assignments map to Business Central dimensions for allocation reporting.

Foundry Bean items support inventory tracking across multiple warehouses and locations. We map item numbers, costing methods, and warehouse assignments. Custom pricing tiers that do not map directly to Business Central price groups are flagged for manual review and rebuild in Business Central's pricing module. Inventory valuation methods map to Business Central costing versions.

Sales invoices, recurring invoices, and subscription-generated invoices in Foundry Bean map to Business Central sales invoices or purchase invoices depending on direction. We preserve invoice-to-payment linkages and aging data, mapping invoice status to Business Central's lifecycle states. Open invoices migrate with full remaining balance; paid invoices migrate as closed historical records.

Foundry Bean subscriptions with flat-fee pricing map to Business Central sales subscriptions. Usage-based and volume pricing map to Business Central billing schedules with line-by-line billing. Tiered pricing subscriptions require tier flattening: each tier threshold and per-unit rate becomes an individual billing schedule line or a separate price group line. Subscriptions with complex tier stacking are flagged for manual review before migration.

Contract records in Foundry Bean link to subscription billing and revenue recognition schedules. We preserve contract-to-revenue schedule linkages and map the recognition method to Business Central's revenue recognition configuration. Contract terms (start date, end date, renewal type) migrate as contract metadata attached to the subscription or billing schedule.

ASC 606 recognition schedules in Foundry Bean are generated from contract terms and subscription billing rather than stored as independent records. We recalculate schedules in Business Central from the migrated contract data using milestone-based or time-based recognition methods. Each schedule's recognition start date, total amount, and method type are mapped to Business Central revenue recognition lines. If Foundry Bean exposes derived schedule records, we export them for reference but rebuild from source contracts.

Purchase orders link vendors to items and drive invoice processing. We migrate open and closed PO history, preserving the PO-to-invoice relationship for procure-to-pay audit trails. Partially received purchase orders migrate with received quantity and remaining quantity so that Business Central's receiving workflow can resume without duplication.

Bank and credit card accounts with real-time balance tracking and auto-reconciliation in Foundry Bean map to Business Central bank accounts. We map account numbers, bank details, and opening balances to Business Central cash account setup. Bank reconciliation templates migrate as reconciliation worksheets for the customer's admin to apply post-migration.

All journal entries from bank reconciliation, invoice processing, and manual entries stored chronologically in Foundry Bean migrate as Business Central G/L entries. We extract full GL transaction history including adjustment entries, preserving the debit and credit balance. Opening balances for balance sheet accounts are established before transaction history migration using a separate opening balances import.

Foundry Bean expense reports auto-convert to vendor invoices upon approval. We capture the approval state before conversion and export expense reports as employee expense journal lines rather than vendor invoices to avoid duplicate liability records in Business Central. The two-record relationship (expense report + resulting vendor invoice) is collapsed into a single expense journal entry with approval workflow to be configured in Business Central post-migration.

Foundry Bean's undocumented custom object API requires cataloguing during discovery. We map customer-defined objects to Business Central custom tables (using AL extensions) or to Dataverse tables if the destination is Dynamics 365 Finance, Supply Chain, or Project Operations. Custom object relationships, custom fields, and data types are preserved. We do not migrate custom object API logic; the customer rebuilds the application logic in Business Central AL or Power Apps.