Migrate your Foundry Bean data

Accounts are organized into Balance Sheet and Income Statement categories automatically. We map each account code and type to the destination chart, preserving the platform's automatic categorization logic by recreating account-category assignments in the target system.

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 systems.

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.

Employee records include compensation history, benefits, and organizational assignments. Effective-dated changes require careful sequencing; we import current state first, then apply historical compensation and job-title changes chronologically.

Items support inventory tracking across multiple warehouses and locations. We map item numbers, costing methods, and warehouse assignments, flagging any custom pricing tiers that do not map directly to the destination schema.

Sales invoices, recurring invoices, and subscription-generated invoices are standard objects. We preserve invoice-to-payment linkages and aging data, mapping invoice status to the destination's lifecycle states.

Employee-submitted expense reports auto-convert to vendor invoices upon approval in Foundry Bean. We extract the approval workflow state before conversion and recreate the two-record relationship in the target system.

Subscription billing supports flat fee, usage-based, volume, and tiered pricing. Each subscription record links to a billing schedule and generates invoices. We map the active pricing model and any tiered rate definitions; volume and tiered pricing tiers require custom field mapping to match destination pricing logic.

Contract records link to subscription billing and revenue recognition schedules. We preserve contract-to-revenue schedule linkages and map the recognition method to the destination's ASC 606 configuration.

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.

Bank and credit card accounts with real-time balance tracking and auto-reconciliation are stored as distinct objects. We map account numbers, bank details, and opening balances to the destination cash management module.

All journal entries from bank reconciliation, invoice processing, and manual entries are stored chronologically. We extract full GL transaction history including adjustment entries, preserving the debit-credit structure and account assignments.

ASC 606-compliant schedules are generated from contracts and subscription billing. Each schedule has milestone or time-based recognition rules. We map recognition start dates, amounts, and method types; schedules tied to multi-entity contracts require additional entity assignment mapping.

The platform does not expose a documented custom object API in public documentation. Any customer-defined objects must be catalogued during discovery; we map them to custom tables or fields in the destination, noting that the source schema may require manual field enumeration before migration.