Migrate from AFAS to Infor CloudSuite Corporate

AFAS Profit stores the Dutch chart of accounts in its financial ledger tables with statutory account codes and cost-center mappings. We extract the full account structure and map it to Infor CloudSuite's account master, preserving the Dutch statutory codes where Infor supports country-specific chart configurations. Cost-center assignments migrate as cost-center codes in Infor's cost accounting structure. The customer reconciles the account hierarchy with their Infor functional consultant before the import phase begins.

AFAS Customer and Supplier records include contact details, VAT registration numbers (BTW/ondernemingsnummer), payment terms, and addresses. We map these to Infor CloudSuite's party framework, preserving the VAT registration number as the party tax identifier. Payment terms migrate as Infor payment codes. Customer-supplier classification is preserved so that the same legal entity with both roles appears as separate party records in Infor.

AFAS invoices include line items, tax codes, payment references, and BTW treatment per line. We extract open invoices and a scoped history (typically the last 2-3 fiscal years) with line-level tax code assignments preserved exactly. Historical invoices migrate to Infor's open or closed AR/AP registers depending on payment status at cutover. The customer's accounting team reviews the tax code mapping before production load to confirm BTW treatment aligns with Dutch tax authority requirements.

AFAS inventory Items include stock levels, warehouse locations, pricing tiers, BOM structures, and reorder thresholds. We extract full item records with BOM and routing data where applicable, mapping them to Infor CloudSuite's item master. Active/inactive status and reorder points migrate. Item costing methods from AFAS map to Infor's cost type configuration, though the customer validates cost roll-up accuracy post-migration as part of UAT.

AFAS Projects with associated time entries migrate to Infor CloudSuite's project management module. Non-standard rate structures and custom fields on AFAS projects require explicit mapping during the schema reconciliation phase. Time entries from AFAS become labor transactions in Infor, with the original date, hours, and employee reference preserved for project billing and cost tracking.

AFAS employee records include contract details, salary history, and payroll journal entries. We extract employee records with their current contract and a scoped payroll history (last 3-5 years of active employment plus all year-end closing records) to balance compliance requirements against migration volume. Historical records older than the agreed scope are archived per Dutch legal retention requirements and documented separately. The employee effective-date structure in AFAS maps to Infor's employee effective-dated record model.

AFAS bank account configurations, reconciliation data, and current balances migrate to Infor CloudSuite's treasury or cash management module. Account numbers, bank identifiers, and opening balances are preserved. Reconciliation data migrates as historical bank statement records; open reconciling items are flagged for manual resolution by the customer's accounting team post-migration.

AFAS stores Dutch VAT rates, BTW configurations, and fiscal account mappings in its tax configuration tables. We extract the complete set of tax rates and mappings and configure Infor CloudSuite's tax engine with the corresponding BTW codes before any transactional data loads. The customer's Dutch tax advisor or accounting team reviews and approves the tax code mapping before production migration to ensure BTW treatment on invoices aligns with Belastingdienst requirements.

AFAS links documents to records across financial, HR, and logistics modules. We extract attachments associated with transactional records (invoices, employee records, projects) and link them to the corresponding Infor records via Infor Document Management (IDM) or ContentServer. The file format may require conversion depending on whether the source attachment uses an AFAS-specific format. We flag any conversion-required attachments during the schema inventory phase.

AFAS custom fields on standard objects and user-defined tables vary per installation and are present in virtually every established AFAS deployment. We inventory every custom field and user-defined table during discovery, classify them by data type and business necessity, and map them to Infor CloudSuite custom fields, custom objects, or extension tables. Any AFAS custom tables that have no Infor standard equivalent are documented as custom object requirements and built in Infor CloudSuite before data migration begins. This is the most variable and time-intensive portion of any AFAS migration scope.

AFAS workflows define approval chains, conditional routing, and automated actions across HR requests, invoice approvals, and project sign-offs. These are platform-configured business processes, not records. We do not migrate workflows. We extract workflow configurations as process documentation and map them to Infor OS workflow equivalents, but the rebuild occurs in the destination system by the customer's implementation team. The written workflow inventory includes trigger conditions, routing logic, responsible roles, and recommended Infor OS workflow configuration as a handoff artifact.