Inventory the SYSPRO customisation estate — Application Builder apps, screen tailoring, C# scripts, business object automations, workflow and mobile customisations — and triage each surface into Power Platform, X++ extension, ISV or retirement.
The adapter's list of canonical pain points names this domain second, and phrases it without hedging: Application Builder and C# scripting create meaningful re-platforming work with no direct D365 equivalent.
D365 finance and operations applications use an extension-only model. Standard code cannot be modified. Customisation attaches through defined mechanisms:
The customisation register enumerates ten surfaces, each with a triage disposition already assigned. This is the checklist to run the inventory against.
These three account for most of the unknown volume, because they are the surfaces business users and analysts can reach.
Connected Systems Manager, e.net business objects and the OData connector are covered in depth by the Integration, Data & Analytics module. Two points belong here.
Workflow and Document Flow Manager is rated Power Platform, and the practical answer is usually a mix. Approval processes with a clear structure map to native D365 workflow, which has the advantage of running inside the transaction and enforcing state. Document routing, generation and distribution frequently fit Power Automate better.
Espresso mobile customisations and Missions and Tasks custom workflows are rated an X++ extension disposition, and they split along the same line as the warehouse posture decision in the Inventory module.
The Supply Chain Portal, the tax connector and the document services are grouped as an ISV or partner-solution triage, and the related gap rates the target architecture for them undecided with low confidence.
Given that the inventory is the domain's governing unknown, the method deserves stating.
This domain converts an unknown into a plan, and the unknown is genuinely unknown until someone counts.