GP and AX User Role to New ERP Permission Mapping Worksheet
Security is rebuilt, not copied, in a move from Dynamics GP or AX. This worksheet lists legacy roles beside target permission sets so auditors can see how access was carried over and where duty conflicts were found.
| Legacy role | Key tasks covered | Users | Target permission set | SoD risk | Reviewed by | Review priority | Action | |
|---|---|---|---|---|---|---|---|---|
3 | ||||||||
6 | ||||||||
5 | ||||||||
2 |
Role and permission set names shown are examples; verify names in your own GP, AX and Business Central environment. A single GP user often holds several roles, so count users per role, not unique people.
Access conflict review
Optional: we can discuss analysing your role assignments for conflicts.
Optional. The tool and every export work without this. No spam.
How to fill it in
Export roles and assigned users from your legacy system. In GP, security uses roles made of tasks; in AX 2012, roles contain duties and privileges. List the roles, describe the key tasks in plain words and map each to a permission set in the new system. Use the action column to mark roles that need splitting.
- One row per legacy role
- Plain-language task description
- Record who reviewed each row
- Flag any role that combines entry and approval
Segregation of duties
Migration is a chance to remove old overlaps, such as one person who can create vendors and release payments. Mark high-risk rows and decide whether to split the role, add a compensating review, or remove access. Keep the decision on record for audit.
After go-live
Run an access review after the first month close. Roles drift quickly when staff ask for temporary access during cutover, and those exceptions rarely get revoked unless someone checks.
Frequently Asked Questions
Does GP security map one to one to Business Central?
No. GP uses roles and tasks, while Business Central uses permission sets assigned through user groups or directly. Expect to redesign, not copy.
How do I get GP roles and users?
Use GP's security reports, or query the SY10500 and SY10600 style security tables with a DBA. Confirm table names for your version before relying on them.
Who should sign off?
Process owners confirm tasks, the controller confirms financial access, and IT or internal audit confirms the final assignments.
Is the review priority column meaningful?
It is simply the user count, so larger roles surface first. Sort on it and review high-impact roles before small ones.
If you want legacy role assignments analysed for conflicts before mapping, we can discuss tooling that reads them from your system.
Related Tools
GP Third-Party Add-On Inventory Worksheet
List every ISV product and custom dictionary in your GP install with maintenance cost and a disposition, then see the total migration effort.
Microsoft DynamicsDynamics AX 2012 Retirement Project Charter Template
A one-to-two page charter for getting executive approval to retire or replace Dynamics AX 2012, with scope, drivers, risks and sign-offs.
Microsoft DynamicsGP to Business Central Cutover Runbook Template
A fill-in cutover runbook for moving a Dynamics GP company to Business Central: freeze window, final extracts, opening balances, go/no-go and rollback.
Microsoft DynamicsAX 2012 to D365 Data Entity Mapping Worksheet
Plan each AX 2012 data object, its D365 data entity, load sequence, record count and owner in one editable migration sheet.
More Microsoft Dynamics tools
See all- Dynamics GP End of Support Migration Assessment
- Dynamics GP SQL Table Reference (IV00101, SOP10100, POP10100)
- Dynamics GP Chart of Accounts Mapping Worksheet
- GP Cutover Open Balances Reconciliation Worksheet
- GP to Business Central Partner RFP Letter Template
- GP Open Transactions SQL Query Generator
- Dynamics GP Unsupported Risk Exposure Calculator
- Dynamics GP Work, Open and History Table Map
- Dynamics GP SQL AR Aging Query Generator