web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Suggested Answer

Best time to do a finance go-live/cutover?

(0) ShareShare
ReportReport
Posted on by 11
Hi all,
 
We're currently going through an ERP implementation where we're moving from Access Dimensions to Dynamics 365 FSCM. The first business release is purely finance related where we're lifting and shifting our transactions/day to day work from Access to D365.
 
Our current plan is to go-live at the end of April for the start of May which is also a bank holiday allowing us more time for cutover activities.
 
We have a query around best practice and approach for how to manage our data migration and cutover activities.
 
Our AP & AR month ends finish at the end of the month so say 30th April, however our GL and management accounts can't be finished and closed until around 15th May (which is also a Friday and falls over a weekend).
 
Our options are the following and hopefully you can point us in the right direction with pro's/con's.
 
  1. Close AP/AR on 30th April, migrate across to D365 over the bank holiday weekend and then draw a line in the sand that we no longer use Access Dimensions and we only move D365 moving forward.
  2. Close AP/AR on 30th April, again migrate across to D365 over the weekend. However from a training perspective and not being able to close the GL prior to migrating. We do the month end for April in Access Dimensions and then migrate the two weeks worth of GL transactions into our production environment to bring it in line with the additional financial data. AP/AR start in D365 from 1st May.
  3. Close GL on 15th May, cut across to D365 across that weekend which will have the month end close of April within the GL and then also any outstanding AP/AR transactions that have not been settled in Access Dimensions to be settled in D365.
Let me know your thoughts.
 
Thanks, David.
Categories:
I have the same question (0)
  • Sukrut Parab Profile Picture
    71,724 Moderator on at
     
    Have your performed analysis on your data to know volume of transaction you will have to deal with if you go live on different dates? 
     
    think about following things 
    - Volume of Data you will be moving to new system and whether you can complete that or not within cutover window.
    - How much manual efforts are involved to settle transactions if you go live on 30th vs on 15th. 
    - Try to close as much as possible in Access dimension.
     
    From the information you have provided, first option looks much cleaner. It really depends on how much data you are going to migrate but based on what you have described if its only financial data you should be able to complete all your activities over the weekend. With this approach you are going to perform all your work in D365 and settle outstanding transactions with standard process which F&O has, assumption is you don't have many transactions to settle in FO. 
     You don't have to worry about migrating and settling lot of transactions later which you would do if you cutover on May 15th.
     
  • Suggested answer
    Syed Haris Shah Profile Picture
    1,416 Super User 2026 Season 1 on at
     
    For the cutover to D365 F&SCM, it is recommended to close Accounts Payable and Accounts Receivable in the legacy system as of 30 April and migrate open subledger transactions along with the General Ledger trial balance into D365. From 1 May onwards, all operational processing should occur exclusively in D365.

    The legacy General Ledger may remain temporarily open only for controlled reference during the final close. However, all adjustment postings should be recorded directly in D365. Only pure GL adjustments (e.g., accruals, prepayments, reclassifications) that do not impact subledgers should be permitted post cutover. Any adjustments requiring customer, vendor, or bank impact must not be processed in legacy and should be handled within D365 using the appropriate subledger processes.

    This approach ensures a clean system cutover, maintains data integrity, avoids subledger/GL mismatches, and supports auditability with a single source of truth from go-live.
     
    Regards,
    Syed Haris Shah

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Giorgio Bonacorsi Profile Picture

Giorgio Bonacorsi 493

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 413 Super User 2026 Season 1

#3
Syed Haris Shah Profile Picture

Syed Haris Shah 242 Super User 2026 Season 1

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans