The Folder, the Automatic Journal and the redesign imperative
Understand the three constructs that define Sage X3 — the Folder topology, Automatic Journals resolved through Accounting Codes, and the L4G/Adonix customisation heritage — and why translating each into D365 F&O demands a redesign rather than a conversion.
What you will be able to do
Explain why a Sage X3 migration is a redesign rather than a data conversion
Describe the Folder/company/site/legislation topology as X3's defining platform primitive
Describe Automatic Journals and Accounting Codes as X3's accounting primitive and their D365 counterparts
Identify the L4G/Adonix and Syracuse customisation estate and its migration dispositions
Name the event → intent → voucher → ledger pipeline both systems share and where translation effort concentrates
List the decisions a programme must settle before configuration begins
Introduction
Every ERP migration carries a hidden prerequisite: understanding what the source system actually is, structurally, before any mapping spreadsheet is opened. Sage X3 is not a simpler SAP, nor a French-language NetSuite, nor a mid-market Oracle.
The Sage X3 Platform Topology
Keep the source vocabulary precise. A Folder is the broadest application and data container in Sage X3. It can hold multiple companies and carries shared parameterisation — accounting models, dimension types, Automatic Journal templates, Accounting Codes, customisation layers, and workflow rules.
The Accounting Primitive: Automatic Journals and Accounting Codes
Sage X3 derives ledger postings through a matrix of Automatic Journals — rule-driven posting templates configured per operational event family — resolved through Accounting Codes that determine the specific general-ledger accounts to debit and credit.
The L4G/Adonix Customisation Heritage
Sage X3 customisation runs on a proprietary fourth-generation language called L4G (also referred to as Adonix 4GL), inherited from the original Adonix technology stack that predates Sage's acquisition.
The Shared Pipeline: Event, Intent, Voucher, Ledger
Despite their structural differences, Sage X3 and D365 F&O run the same fundamental accounting pipeline:
Decisions That Block Everything Else
Before any D365 configuration, data-migration sprint, or integration design can begin, the programme must resolve five structural decisions. Each is a precondition for every downstream workstream, and deferring any of them forces rework:
Knowledge check
Summary
Sage X3 and D365 F&O both produce audit-defensible, period-closed accounting records. They arrive at that outcome through different architectural choices, and a migration is the work of re-projecting one set of choices onto the other.