Finance | Project Operations, Human Resources, ...

Import the UAT database to the Production environment in the Dynamics 365 Finance and Operations

(1) Share

Report

Posted on by Syed Amir Ali

185

Hi,

I have a query regarding the database movement from the Sandbox (UAT) environment to the Production environment in D365 Finance & Operations.

Background:
Previously, two businesses were operating on a single Production instance. One of the businesses is now separating and requires a complete database backup, including all types of data. Both businesses are currently under the same tenant but have separate LCS projects.

As part of this activity, I have already taken the database from the existing Production environment and imported it into the UAT environment of the other business.

Requirement / Question:
For the Production environment, I am planning to engage Microsoft to copy the UAT database (.bacpac) file and import it into the new Production environment.

Could you please confirm whether this is the correct approach and whether Microsoft supports this process for moving a UAT database into Production?

Thank you for your guidance.

Best regards,
Syed Amir Ali

Categories:

Dynamics 365 Finance

Dynamics 365 Project Operations

Microsoft Dynamics AX

I have the same question (0)

All responses (6)

Answers (0)

Suggested answer

BillurSamdancioglu 19,854 Most Valuable Professional on at

Like (0)

Report

As far as I know , Microsoft supports this operation but of course this information needs to be validated.

Was this reply helpful? Yes No
Suggested answer

vishalsahijwani 168 on at

Like (0)

Report

Hi @Syed Amir Ali ,

There is no need for you to engage Microsoft support team as you have an option to directly import UAT database through refresh database option in Environment details page of production environment.

Just follow the below mentioned steps : -

Step 1 - Go to Prod environment page in LCS.

Step 2 - Select Move Database option.

Step 3 - In the screen Select the change type screen select Refresh Production Database option.

Step 4 - In Production database refresh screen select your UAT environment from drop down menu named as Source environment.

Step 5 - Make sure target environment should show the name of your Production Environment.

Step 6 - If you want to copy the document attachments from UAT environment to your prod environment then enable the flag Copy document attachments.

Step 7 - Select the By clicking submit checbox.

Step 8 - Click Submit button.

Note - Make sure while this process going on there should be a down time for both Prod and UAT environment otherwise inconsistent data will flow to Prod environment.

Please check if this helps and mark this as a verified answer.

Was this reply helpful? Yes No
Suggested answer

Martin Dráb 237,965 Most Valuable Professional on at

Like (0)

Report

You indeed need to involve Microsoft; no one else can do it (in case of the production environment). You need to create a service request called Sandbox to Production. Please refer to Golden configuration promotion (in F&O documentation) for more details.

Was this reply helpful? Yes No
Syed Amir Ali 185 on at

Like (0)

Report

@BillurSamdancioglu and @Martin Dráb, Thank you for your comment.

I reviewed this documentation yesterday (Golden configuration promotion) and raised a support ticket with Microsoft. However, the Microsoft support engineer informed me that database movement from the UAT environment to the Production environment is blocked in LCS. However, my understanding is that Microsoft can still perform this activity. Therefore, I requested another session with them to discuss the matter further in detail.

Was this reply helpful? Yes No
Suggested answer

Sagar121 872 on at

Like (1)

Report

If you want to restore the database to Production, you can follow the steps suggested by Vishal. Based on your comment, it seems you will have diff LCS Project Id and PROD environment (assuming PROD environment slot is available).

You will need to make sure all below parameter there would be many more like

Enabling users
Setting up email parameters
Configuring blob storage or certificates
Business event setup/ Integration

Batch Job status setup and Batch group.

And possibly many more this will keep increasing once you will do one round to mock cutover.

As you will have new PROD environment for sure MSFT would be to be involved for sure. Make sure to check AOS and batch server Qty in new PROD.

The ideal approach as per my understanding do a pre mock cutover first.

Restore the database to the new Production environment.
Perform all necessary configurations totally depend upon the project.
Allow business users to do a regression test once everything is set up and documented then go for refresh again.

1 people found this reply helpful.

Was this reply helpful? Yes No
Syed Amir Ali 185 on at

Like (0)

Report

Hey @Sagar121 and @vishalsahijwani,

I am aware that this option is available and have already reviewed the relevant documentation. However, I could not find clear details regarding its pros and cons or guidance on when it should be used safely. In line with Microsoft standards, I raised a support ticket to better understand the use of this option and its prerequisites. Nevertheless, thank you for your input.

Was this reply helpful? Yes No