Pre-built infor baan data migration for Finance, Distribution, Manufacturing, Warehousing and Project. tdord/tcorda/tfgld database extractors, BaaN BSE attachment routing, dimension-to-COA translation, FBDI/HDL emitters, row-level reconciliation. Audit-ready SOX + HGB + IFRS evidence at every load.
The hard part isn't running SELECT against BaaN tables. It's translating BaaN's 25-year data model into Fusion's modern shape without losing the GL → AP → PO → goods receipt audit chain, the HGB+IFRS dual-GAAP streams, or the ITAR/DFARS export-control markings.
Infor BaaN IV and BaaN V — the predecessors to Infor LN — present a data model built around tightly-prefixed table families (tf for finance, td for distribution, ti for manufacturing, tc for common, tp for project, tw for warehousing, ts for service). 3,500+ tables in a full install. Composite natural keys involving financial company + transaction type + document + line. Packed-decimal numeric encoding. Dimension structures up to 6 deep. The session metadata catalog (ttadv/ttdlu) that documents every BaaN 4GL session and every customization.
Oracle Fusion's data model is fundamentally different. The COA is a 6-segment structure (typically Company, BU, Cost Centre, Account, Product, Future). Numeric fields use IEEE floating-point. Customizations live as PaaS extensions, Visual Builder pages, OIC orchestrations and AMX flows. Every infor baan data migration to Fusion has to bridge those gaps without breaking the audit chain — and without losing the parallel HGB (German statutory) and IFRS ledger streams that European finance teams depend on for statutory filings.
Syntra ETL replaces multi-month bespoke conversion development with pre-built crosswalks refined across BaaN engagements in European manufacturing, Middle East industrial, and global aerospace/defence. The same engine handles three deployment scenarios: full BaaN replacement onto Fusion, phased pillar-by-pillar migration (Finance first, then Distribution + Manufacturing, then Service + Project), and the multi-company consolidation where 5–8 t_fcom companies merge onto one Fusion tenant during a post-M&A integration.
The transformations Syntra ETL ships pre-built. No custom SQL backfill, no multi-month bespoke conversion development per pillar.
BaaN's 6-deep dimension structure (Cost Centre, Project, Reason, Item Code, Origin, plus customer extension) walked, classified, and routed into Fusion's 6-segment COA without analytical-granularity loss. Crosswalk versioned and signed.
t_fcom / t_lcom multi-company structures converted to Fusion BU/ledger architecture. Parallel HGB (German statutory) and IFRS ledger streams preserved with separate reconciliation per legal entity per period.
tcibd item master conflicts across multiple t_fcom resolved with single master designation; cross-references preserved. BaaN bill-of-materials translated to Fusion item structures with full level-by-level routing.
tcmcs exchange-rate history loaded into Fusion daily/period rates. VAT/MwSt/TVA/IVA tax routing per EU country preserved. Reverse-charge handling for cross-border B2B intra-EU trade carried through.
ttadv/ttdlu session catalog mined for every customization. 4GL source exported with trigger context. Customizations classified for retire/rebuild planning across AMX, OIC, Visual Builder, OTBI.
Export-control tagging on items, BOMs, drawings preserved through migration. US-isolated Fusion target tenant supported where contracts demand. DFARS 252.204-7012 NIST 800-171 archive available for off-Fusion records.
A repeatable load order that respects Fusion's data dependencies. Skip a step and your AP invoice load fails on missing suppliers, or your manufacturing load fails on missing BOMs.
Fusion enterprise structures, ledgers (HGB + IFRS in parallel), BUs per legal entity, COA segments, calendars, currencies, daily exchange-rate types configured. Loaded via FSM tasks — not user-facing data, but everything downstream depends on it.
Suppliers (FBDI Supplier Import with VAT-ID/IBAN dedupe), customers (FBDI Customer Import), items (FBDI Item Import with BOM translation), GL accounts, projects, fixed-asset categories with German AfA methods. Loaded in dependency order — never invoices before suppliers.
Open AP invoices and payments, open AR invoices and receipts, open POs (tdpur) and sales orders (tdsls), open production orders (tipcs), in-process warehouse picks. Migrated in transactional state with full reference to closed history.
Closed tfgld GL periods loaded via FBDI Journal Import with both HGB and IFRS ledger streams. Trial balances reconciled to the cent vs BaaN per legal entity per ledger. AP/AR aging reconciled at customer/supplier/BU level. tffam fixed-asset depreciation history loaded.
Closed sales/purchase order history, closed production order history, inventory transaction history loaded. BSE archive attachments routed to Fusion UCM with original references preserved. Project pegging history (tppdm) loaded for active long-cycle projects.
Final delta replay via DB CDC + BaaN Exchange Scheme, parallel-month reconciliation per legal entity, sign-off pack issued (trial balance HGB+IFRS, AP/AR aging, inventory perpetual, production WIP — BaaN vs Fusion to the cent). Production cut to Fusion.
Every BaaN data domain emits to the exact FBDI/HDL/REST format Fusion expects. No custom load programs, no rejected-record triage in production.
tfgld GL history via Journal Import per ledger (HGB and IFRS in parallel); opening trial balance via Trial Balance Import per legal entity; sub-ledger detail preserved for audit drill-down.
tfacp AP Invoice/Payment/Hold Import with VAT routing. tfacr AR Invoice/Receipt/Adjustment Import. Open and closed transaction state preserved with BSE attachments routed to Fusion UCM.
tffam converted to Mass Additions interface. German AfA depreciation methods, IFRS componentization, asset retirement and transfer history loaded.
Supplier Import with VAT-ID/IBAN dedupe. Item Import with BaaN BOM translation. Procurement Contract Import for blanket and pricing agreements.
Production Order Import for in-flight orders, On-Hand Quantity Import for inventory snapshot, BOM Import for item structures. Serial/lot history preserved for FDA / ITAR-driven environments.
Post-cutover delta replay via Fusion REST APIs. BaaN Exchange Scheme partners re-pointed to OIC adapters. Real-time reconciliation continues for the parallel-run window.
Infor baan data migration is the end-to-end movement of structured data from Infor BaaN IV / BaaN V into Oracle Fusion ERP — Financials, Procurement, Supply Chain, Manufacturing and Project — plus archive of history not loaded operationally. Scope spans Finance (tfgld GL, tfacp AP, tfacr AR, tffam Fixed Assets), Distribution (tdsls sales orders, tdpur purchase orders, tcorda customer/supplier orders, tcibd item master), Manufacturing (tisfc shop floor, timfc MRP, tibom BOMs, tirou routings), Warehousing (twhinr, whinp), Project (tppdm) and Service (tssoc). The technical heart is direct database extraction (Oracle/Informix/MS-SQL beneath BaaN), session-catalog mining for customizations, and Oracle-validated FBDI/HDL output. Syntra ETL handles all three with pre-built extractors, governed crosswalks, and reconciliation per company per period.
Migration is the end-to-end project (extract + transform + load + reconcile + cutover); conversion is the transformation layer specifically. Syntra ETL's infor baan data migration engine ships pre-built conversion rules for BaaN dimensions to Fusion COA segments, t_fcom / t_lcom company hierarchies to Fusion BU/ledger structures, BaaN packed-decimal field handling, BaaN's distinctive composite natural keys (Financial Company + Transaction Type + Serial), supplier dedupe by VAT-ID/IBAN, item master with BaaN bill-of-materials translation to Fusion items, multi-currency exchange-rate history (tcmcs), and dual-GAAP HGB+IFRS ledger preservation. On a consultant-led project these conversions eat 4–6 months of bespoke SQL per pillar.
BaaN IV ran on Informix, BaaN IVc4 added Oracle and MS-SQL support, BaaN V standardized on Oracle/MS-SQL. Syntra ETL's infor baan data migration extractor ships read-only stored procedures and table-aware extract scripts for the full 3,500+ table catalog across all three database back-ends. It honours BaaN's natural keys (Financial Company + Transaction Type + Document Number + Line for transactional, Company + Item Code for master), handles BaaN's distinctive packed-decimal numeric encoding, preserves logical-company / financial-company segregation, and streams to Parquet partitioned by t_fcom and fiscal year with hash-signed manifests. Extraction runs throttled against a read replica when available so live BaaN operations remain untouched.
Yes — it is the most common shape. A European manufacturer with 8 legal entities typically runs BaaN with 8 financial companies (t_fcom) consolidated into 1–3 logical companies (t_lcom), with intercompany trade running through paired Sales/Purchase orders. Syntra ETL's multi-source mode extracts from every t_fcom in parallel, runs supplier dedupe by VAT-ID with country-specific tax routing, harmonizes overlapping cost-centre codes to a unified Fusion COA, resolves item master conflicts (same SKU on multiple companies with different prices), and merges intercompany trade into Fusion intercompany invoicing. Dual-GAAP HGB+IFRS ledger streams reconcile separately and land in Fusion as parallel ledgers per legal entity. Output: one clean Fusion tenant carrying the full multi-company history.
Syntra ETL emits Fusion-native load formats for every BaaN data domain: FBDI Journal Import for tfgld GL history with HGB and IFRS ledger streams, FBDI Trial Balance Import for opening balances per legal entity, FBDI AP Invoice/Payment Import for tfacp, FBDI AR Invoice/Receipt Import for tfacr, FBDI Fixed Asset (Mass Additions) for tffam with German AfA depreciation methods, FBDI Supplier Import with VAT-ID and IBAN, FBDI Customer Import, FBDI Item Import with BaaN bill-of-materials translation, FBDI Procurement Contract Import, HDL Worker.dat where BaaN HRM is in scope. Every payload is validated against the current Oracle Fusion 26x release schema before submission — validation errors surface locally, not in a 4-hour Fusion ESS job that fails on row 487,000.
Every record extracted from BaaN is hashed at the source. Every record loaded into Fusion is re-hashed post-load. The reconciliation engine compares counts (journals, invoices, items, BOMs), sum totals (debit/credit per ledger per financial company per period for both HGB and IFRS streams, AP open per BU per currency, AR aging, item perpetual inventory value per warehouse) and hash signatures per t_fcom per period. Any record that fails Fusion validation is captured with the exact field-level reason ready for bulk fix. Output is a signed timestamped reconciliation pack: BaaN trial balance vs Fusion trial balance to the cent per ledger per legal entity, AP/AR aging vs aging, inventory perpetual vs Fusion item quantities. External auditors sign off on the pack directly.
Yes. After the initial bulk load, Syntra ETL captures BaaN deltas through database-level CDC (Oracle LogMiner, MS-SQL CDC, or Informix logging) plus BaaN Exchange Scheme subscriptions for transactional flows, and replays into Fusion through REST APIs and FBDI. This supports the standard parallel-run pattern: BaaN continues taking transactions for 2 month-end cycles while Fusion is validated to the cent per legal entity. Once finance, manufacturing and supply chain sign off, new transactions cut to Fusion and BaaN moves to read-only archive mode. EDI partner cutovers (the BaaN Exchange Scheme partners feeding orders, ASNs and invoices) are coordinated in lockstep so no transactional flow is broken at cutover.
SOX requires 7-year retention with audit trace from GL entry back to original supporting evidence. German HGB §257 demands 10 years for accounting records. IFRS adds harmonization requirements across European entities. ITAR / DFARS retention runs 5–7 years for defence-controlled records. Syntra ETL's infor baan data migration preserves the full chain: Fusion GL line → AP invoice → PO → goods receipt → original vendor document (from BaaN BSE archive), with every hop signed and timestamped. Where Fusion is the cutover target, full transactional history loads into Fusion for the operational window; older history routes to a long-term cloud archive — queryable for the full SOX / HGB / IFRS / ITAR retention period with the same evidence chain intact.
Book a 30-minute discovery call. We'll walk through your BaaN release (IV / IVc4 / V), database back-end (Oracle / Informix / MS-SQL), financial-company structure, dual-GAAP requirements and EDI partner inventory — and give you a concrete data-migration plan before the call ends.