Key responsibilities
Extract and catalogue design metadata for each application from the DXL and NSF copies: forms, subforms, views, folders, agents, script libraries, shared fields and the field-level structure behind them.
Separate live design from abandoned design. Notes estates accumulate dated backups, duplicated forms and personal views; excluding them from scope is one of the largest cost levers on the programme.
Identify and document every external integration: ODBC and LS:DO database connections, LEI and DECS connectors, COM automation into Excel and other desktop applications, web service and HTTP calls, file system and SFTP access, and outbound mail.
Map cross-database dependencies across the estate: @DbLookup and @DbColumn calls into other NSF files, linked databases, doclinks and replication relationships. These set the migration sequence and are the dependencies most often missed.
Classify every agent by its trigger. Scheduled and event-driven agents are genuine automation and become Power Automate flows; user-invoked agents are usually report generators and belong in Power BI. Reading this wrongly misprices an application.
Read LotusScript and @Formula closely enough to state what the logic does and what the target must do instead — comprehension and specification, not modification.
Document record-level security implemented through Reader and Author fields, and the ACL roles that sit behind it.
Map Notes data constructs to Dataverse: rich text, multi-value fields, names fields, response hierarchies, attachments and embedded objects.
Produce the per-application analysis pack that the Solution Architect, Business Analyst and Data Migration Engineers all work from.
Support the Data Migration Engineers on source structure, field type drift and attachment handling.
Essential experience
5+ years with Lotus Notes and HCL Domino applications in an analysis, assessment or migration capacity.
Able to read LotusScript and @Formula fluently and explain what a given agent, view or form actually does. Writing new Notes code is not required.
Working knowledge of DXL: able to extract, parse and interpret design exports without access to a live Domino server.
Demonstrable experience tracing integrations and cross-database dependencies inside a Notes estate, rather than only cataloguing design elements.
Understands Notes security — ACLs, roles, Reader and Author fields — and how it translates into a modern security model.
Writes analysis that a developer who has never seen Lotus Notes can build from.
Desirable
Scripting in Python or equivalent, to parse DXL at estate scale rather than by hand.
Working knowledge of Power Platform, enough to specify in target terms.
Experience with Notes applications that drive Excel or other desktop applications through COM.