Migrate from Foundry Bean to Acumatica

Foundry Bean customers map directly to Acumatica's Customers screen (AR303000). The customer name, class, status, credit terms, and address fields transfer as-is. Open or inactive customer status is preserved during migration. Multiple currency assignments in Foundry Bean require Acumatica's Currency Management (CM202000) screen to be configured before the migration run; otherwise currency assignments default to the base currency.

Foundry Bean's payables vendor management translates to Acumatica's Vendors screen (AP303000). Vendor name, payment terms, tax ID, and address fields map directly. Vendor contacts in Foundry Bean embedded in payables records need to be extracted and linked to the Acumatica Vendor Contact entity.

Foundry Bean's flat account structure requires decomposition into Acumatica's segment-based chart of accounts. A single Foundry Bean account number like '4100-001' may need to be split into multiple segments (account type + subsidiary + region) matching the configured account mask in Acumatica's GL Setup screen.

Foundry Bean invoices map to Acumatica's AR Invoices and Memos (AR301000). Document number, date, customer reference, description, line items, and amount transfer directly. Open vs. closed status is preserved — closed invoices in Foundry Bean post directly to Acumatica's GL; open invoices land with the appropriate document status.

Foundry Bean bills and AP records map to Acumatica's AP Invoices and Memos (AP301000). Vendor reference, invoice number, date, terms, line items, and amount transfer. Prepayments and adjustments in Foundry Bean map to corresponding AP adjustment document types in Acumatica.

Foundry Bean inventory items map to Acumatica's Stock Items screen (IN202000). Item code, description, unit of measure, item class, and default warehouse transfer directly. Valuation method selection — FIFO, Average, or Standard — maps to Acumatica's ValMethod field on the stock item. Lead times and reorder points become attributes of the item class definition, and any non-stock items in Foundry Bean are flagged for creation as non-stock items in Acumatica's IN202000 screen.

Foundry Bean sales orders map to Acumatica's Sales Orders screen (SO301000). The order number, customer reference, dates, line items with quantities and prices, warehouse assignment, and shipping details transfer directly. Open sales orders in Foundry Bean land in Acumatica with the correct status to continue fulfillment processing. Completed or cancelled orders transfer as historical records in Acumatica's sales order history.

Foundry Bean purchase orders map to Acumatica's Purchase Orders screen (PO301000). The vendor assignment, order number, date, line items with quantities and costs, delivery details, and shipping instructions transfer directly. Multi-vendor purchase orders in Foundry Bean create separate PO records in Acumatica, one per vendor. Open purchase orders retain their status in Acumatica for receipt processing, and closed purchase orders land as completed historical records.

Foundry Bean projects with project fields, status, customer association, dates, and budget data require Acumatica's Project Management module to be enabled and configured. Budget lines map to Acumatica's Project Budget screen. If the Project module is not licensed, project data migrates as custom fields on the customer or inventory records.

Foundry Bean employee records map to Acumatica's Employees screen (EP301000). The employee name, department, manager assignment, employment status, and contact details including email and phone transfer directly. Compensation details such as salary and benefit information require Acumatica's Payroll module to be enabled and configured before migration; otherwise this data is noted for manual entry post-migration.

Foundry Bean custom objects map to Acumatica DAC extensions. Your Acumatica admin must pre-create the Usr-prefix fields using the Customization Manager before migration. Custom object relationships in Foundry Bean that use N:N associations may require junction tables or link fields in Acumatica.

Foundry Bean's subscription billing records (flat fee, usage-based, tiered) translate to a combination of AR invoices and recurring schedule records in Acumatica. The subscription terms, billing frequency, and amount map to Acumatica's Recurring Templates (AR204000) with the appropriate document type.

Foundry Bean employee expense reports map to Acumatica's Expense Claims screen (EP304000). The employee reference, expense date, category, amount, and approval status all transfer directly. Receipt attachments from Foundry Bean are downloaded and re-uploaded to Acumatica's file storage system, linked to the corresponding expense claim records for audit trail continuity.

Foundry Bean workflow definitions, approval chains, and automation rules have no equivalent in Acumatica's schema. FlitStack AI exports the workflow definitions as a reference document for your Acumatica admin or VAR to rebuild using Business Events, Import Scenarios, and email templates.

Foundry Bean's custom financial reports and report templates cannot be transferred to Acumatica's report designer. FlitStack AI exports the report schema and field list so your Acumatica admin can reference them when building Generic Inquiries and reports in Acumatica's Report Designer.