Last week we discussed what Microsoft’s “feature complete” announcement means for RSAT.
This week is about what comes next.
Because most teams make the same mistake.
They start evaluating replacement tools before they understand what they already have.
Before they know which scripts actually matter.
Before they know where coverage gaps exist.
Before they know what would break if RSAT disappeared tomorrow.
Before you evaluate a single replacement — answer these five questions about what you already have.
Not with a vendor demo.
Not with a tool comparison.
With an audit.
The Audit That Should Happen Before Anything Else
We have spoken to teams with hundreds of RSAT scripts who could not confidently explain which ones protect their most critical business processes.
That is not a tooling problem.
It is a visibility problem.
Step 1 — Count Your Scripts
How many RSAT scripts does your team currently maintain?
Under 50: Migration is usually manageable.
50–200: You need a structured plan.
Over 200: You need a strategy, ownership model and phased transition approach.
Most teams cannot answer this immediately.
That is already a signal.
Step 2 — Find Out When They Were Last Run
Pull the execution history.
If a script has not been executed in the last 90 days, ask why.
Inactive automation does not reduce risk.
It creates false confidence.
Step 3 — Map Scripts To Business Processes
Not all scripts are equal.
A financial close process carries different risk than a rarely used report.
Map every script to the business process it protects.
Then rank those processes by operational impact.
That ranking becomes your migration priority list.
Step 4 — Identify What RSAT Is Not Covering
RSAT validates what it can record.
It does not automatically cover:
— APIs
— Integrations
— Background batch processes
— Non-UI business logic
Every RSAT library contains gaps.
The question is whether you know where they are.
Step 5 — Evaluate Customisation Coverage
Standard Microsoft flows are one thing.
Customisations are another.
Many production incidents originate inside custom workflows, integrations, approval logic, finance mappings and business rules.
Most organisations discover that their highest risks sit inside the customisation layer.
What This Audit Reveals
After completing these five steps, most teams discover one of three things:
- They have fewer critical assets than expected.
- Their biggest risks sit outside existing coverage.
- Their challenge is not tool selection. It is preserving business knowledge.
That changes the migration conversation completely.
One Final Thought
Every month spent evaluating tools without understanding coverage makes migration harder.
The clock is the amount of undocumented regression knowledge still trapped inside your RSAT library.
Before you evaluate a replacement tool, understand what you are replacing.
If you have completed an audit and want a second perspective, reply directly.
No forms.
No sales process.
Just a conversation.
Crestech Software specialises in D365 F&O QA, regression automation, Wave validation and RSAT transition readiness.
366 days until May 15, 2027.
#Dynamics365 #D365FO #RSAT #ERPTesting #RegressionTesting #D365Com
