The Support Transfer Process
We follow a structured three-phase process that protects your business continuity and sets you up for long-term improvement. Every transfer is scoped to your system; there’s no one-size-fits-all approach here!
Zero
Business
Disruption
Your existing support stays active throughout the process. The switchover happens at a time that suits your business. Your team won't notice a thing.
Full
System
Documentation
Every customisation, extension, and integration is captured in a Functional Requirements Document before we take over. Nothing gets assumed. Nothing gets lost.
A Dedicated Contact From Day One
From your first discovery call, you'll have one person who owns your transfer. They're accountable for delivery and they'll be your support contact long after the handover is complete.
Here's how we break down the core stages of a Dynamics 365 Business Central Support Transfer

Phase 1: Discovery
This is the first phase of your support transfer. We take time to understand your business and how you currently use Dynamics 365 Business Central.
We run a series of workshops with key people in your team. The sessions are open and practical. We talk through how each area of your system will be supported and where improvements can be made. Where your existing partner is willing to be involved, we welcome their input.
During this phase, we also review all current extensions and custom developments. We produce a Functional Requirements Document that captures everything about your solution as it stands today. Any new requirements we identify are scoped and estimated separately, ready for delivery in Phase 3.

Phase 2: Support Handover
Once Phase 1 is complete, we hold an FRD review session with your team. This confirms the findings and makes sure everything is accurate before it passes to our support team.
When you have agreed the FRD content, your business transfers into Tecvia support. We brief our team on your key contacts, processes and priorities so there is no disruption to your day-to-day operations.

Phase 3 (Optional): Post FRD Recommendations
After the handover, and once scope has been agreed, we schedule resource to act on the recommendations in the FRD. This can include additional user training, third-party app delivery or other improvements identified during Discovery.
Scope for each item is confirmed after the FRD review. You can, however, secure resource allocation during the transfer process so delivery is planned from day one.

Change Requests
If a new requirement comes to light at any stage, we log it as a Change Request. Each one is scoped and estimated separately, outside the original proposal.
All Change Requests carry a status of "Post Support Handover." This keeps new requirements properly planned and prevents them from disrupting the work already in progress.
