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 :
Small and medium business | Business Central, N...
Answered

Best Practices on Sandbox and Production

(4) ShareShare
ReportReport
Posted on by 3,549
Hi:
 
Does Best Practices dictate the following, for an implementation:
 
(1) creating a company in production,
(2) configuring that company,
(3) using Configuration Packages to import master records into that company,
(4) copying the Production environment into a Sandbox environment which of course includes that company,
(5) conducting training in that company in the Sandbox,
(6) conducting User Acceptance Testing (UAT) in that company in the Sandbox,
(7) exporting Configuration Packages and their master data from the company in the Sandbox.
(8) importing their Configuration Packages and their master data into the company in Production,
(9) creating Configuration Packages to import net changes and initial balances for the new year into the company in the Sandbox, 
(10) validating the data in #9 in that company in the Sandbox and
(11) exporting Configuration Packages and their data from #10 from this company in the Sandbox, and
(12) importing Configuration Packages and their data from #11 into the company in Production.
 
Thanks!
 
John
I have the same question (0)
  • Verified answer
    Dynamics_Decoded_Gokul Profile Picture
    487 on at

    The approach you’ve outlined generally aligns with Best Practices for data management and system implementation in Microsoft Dynamics 365 Business Central, with some important clarifications and recommendations:

     
    1. Typically, we do not create and configure a Production company first. Instead, the preferred practice is to build and configure the company initially in a Sandbox environment to fully test configurations, data imports, and processes before moving anything into Production.

    2. The recommended approach is usually:

      • Set up and configure the company in the Sandbox environment first.

      • Use Configuration Packages to import master data and initial balances into the Sandbox.

      • Perform Training and User Acceptance Testing (UAT) in the Sandbox environment to validate that processes, data, and integrations work as intended.

      • Once validated, deploy the same Configuration Packages into the Production environment to replicate master data and configurations without starting directly in Production  

    3. Steps involving copying the Production environment into Sandbox typically happen when you want to refresh Sandbox with current Production data. However, during initial implementation, the flow is typically from Sandbox → Production, not the other way.

    4. Regarding ongoing operations like Year-End adjustments:

      • It is good practice to prepare, test, and validate any data updates, such as net changes or initial balances, in Sandbox first before applying them in Production.

      • Exporting/importing Configuration Packages for this purpose ensures consistency and minimizes risk.


    Therefore, the correct best practice flow should look more like: Configure and validate in Sandbox → Import into Production → Refresh Sandbox from Production periodically as needed.
     
    In summary, your overall approach is sound, but I would suggest avoiding creating and configuring the company directly in Production upfront, and instead, focusing the configuration and data imports to happen first in Sandbox, followed by deployment to Production once fully tested.

    Let me know if you want me to help you structure a detailed Best Practice guideline based on this.

     
  • Suggested answer
    RockwithNav Profile Picture
    8,941 Super User 2026 Season 1 on at
    I will do the same but first everything on Sandbox and then I will take that Sandbox into Production.
  • Suggested answer
    Nimsara Jayathilaka. Profile Picture
    4,950 Super User 2026 Season 1 on at
    Hi
     
    Yes, the best practices generally follow that sequence: set up and configure the company in Production first, use Configuration Packages to import master data, then copy Production to Sandbox for training and UAT, export/import data between Sandbox and Production for master data and changes, and use Sandbox to validate updates before importing them back into Production. This approach ensures controlled data migration, testing, and validation before affecting live data.
     
    Thanks
    Nimsara

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 > Small and medium business | Business Central, NAV, RMS

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 1,926 Super User 2026 Season 1

#2
YUN ZHU Profile Picture

YUN ZHU 1,158 Super User 2026 Season 1

#3
Khushbu Rajvi. Profile Picture

Khushbu Rajvi. 533 Super User 2026 Season 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans