Get your free guide!

Discover the 10 most common functional issues during (and after) a D365 F&O implementation and learn to spot the symptoms in advance.

“IT|Fandango talked more sense in one hour of discovery call than the Microsoft partner of our client did in the previous twelve months.

Sean O’Hara
CEO at ANPRO

Keep your ERP implementation on track

We guide your ERP implementation through every step, ensuring seamless configuration, reliable data migration, and smooth integrations.

System configuration

System configuration is setting up D365 to work for your business processes. It covers both standard and custom parameters, from financial dimensions to warehouse locations.

The system works against the users, who are quick to distrust it and develop creative workarounds. Lack of documentation makes it difficult to understand what’s been configured and why.

The system feels tailored to your business processes because it is. Users complete their tasks efficiently, and data flows logically through your processes.

We explain clearly how the system works and why a certain setup is (not) suitable for you. Then we document the rationale and the configuration chosen for future reference.

Customisations & integrations

Customisations extend D365 beyond its standard capabilities. Integrations connect it to your other systems to create a cohesive technology landscape.

You pay for complex but weak customisations that break with every update and create a maintenance nightmare. Integrations leave out key use cases, causing time wasted in manual data entry.

Your customisations and integrations are based on a well-defined business case and built from a robust design. They integrate seamlessly with the standard system and documentation is exhaustive.

We challenge customisation or integration requests to see if they’re truly necessary. Then, we design them to be robust, non-intrusive, scalable, extensible, and with future updates in mind.

Data migration

Data migration moves your business information from legacy systems to D365. It’s the foundation to ensure business continuity in the new ERP.

You go live with incomplete and inaccurate data. Fixes are expensive because dirty data multiplies once it’s transacted on. The effect is felt for months, halting batch jobs and disrupting critical business processes.

Clean data means a clean go-live, with smooth operations and accurate reports from day one. Historical transactions are still accessible and and opening balances reconcile properly.

We treat setup, master, and transactional data differently. We recommend multiple migrations with iterative validations to clean data, and a repository to store the final configuration.

Security roles configuration

Security roles define who can do what in your D365 system. They balance access needs with proper controls, and have a direct impact on your licensing costs.

Users either can’t access what they need to do their jobs, or they have excessive access that creates security risks and compliance problems. Your Microsoft licensing bill is astronomical.

Your security roles are tailored to your needs and compliant with segregation of duties. They’re optimised so you pay for the system features you use, not for all of them.

We design security roles based on your actual job responsibilities rather than starting from the out-of-the-box ones. System access changes with time, so we teach your team how to maintain the security configuration while keeping license usage in check.

Testing & UAT

Testing verifies that the system works as designed. User Acceptance Testing (UAT) allows key users to confirm that the proposed solution meets their business needs, before going live.

When tests are not skipped altogether, only the happy path is run, but with template data and admin access. Key users don’t know what they’re doing, they’re only following a script. Acceptance is granted for virtue of project inertia.

Tests cases and outcomes are recorded as part of a comprehensive test plan. Key users are eager to verify each case, because it’s their processes. Time is allowed between UAT runs for bug fixes.

We assist you to create a comprehensive test plan while we make sure your key users are ready to lead the testing efforts. We support them when needed, rather than validating processes on their behalf.

Origin logo

What our clients say

Luke Bayston
IT Director UK and NI at Origin Enterprises

FAQs

After 10+ years fixing and guiding Dynamics 365 projects, we know the real objections. Here’s what you’re probably asking — and how we answer.

Can you help us without replacing our current Microsoft implementation partner?

Yes. Our model is designed to enhance your in-house Dynamics expertise, so we work alongside your system integrator to address any gaps. We make sure you realise the value of your D365 investment without expensive rework later.

How can we tell if our customisations are really necessary?

If your customisations are complexity monsters, you’re not changing any of your processes, and are not relying much on standard system features — that’s usually a telling sign.

Isn’t our system integrator responsible for system configuration and data migration?

Yes, but you’re the only one who can tell if the data is complete and the configuration is suitable. And you need Dynamics expertise on your side to do so.

Our system integrator is doing the testing — why do we need to do it ourselves too?

Because only one team knows if the system truly works for your business, and it’s not them. Your key users need to be trained and ready to lead the UAT phase, not relying on the SI for it.

Why can’t we just configure security roles after go-live?

You can do that — but prepare for way higher license costs and disruption to business operations while you configure and test them.

Got more questions? We’ve got answers

We know every business is different. We’re here to answer all your questions and help you make the right decisions for a successful ERP implementation.