Customer experience | Sales, Customer Insights,...

Best Practices for Regularly Refreshing Sandbox Environment from Production

(0) Share

Report

Posted on by Nikki03

I'm trying to find the best way to implement a regular refresh of our sandbox environment with production data to better test features. We use Dynamics 365 Sales Enterprise. Our current sandbox environment is outdated so finding a solution to update the environment with accurate data would be ideal for more accurate testing. I'm aware we have the ability to do a full copy of our production environment to a sandbox environment. However a concern is that by doing so, we go over storage capacity due to how large the production database is. In addition, to do this regularly would result in going over the allotted capacity each time.

I'd love to get some input from other developer teams that have implemented a regular refresh process. How are others refreshing their sandbox environments? Are there external tools that help achieve this?

Thank you.

I have the same question (0)

All responses (4)

Answers (0)

Suggested answer

Eiken Microsoft Employee on at

Like (1)

Report
Copy link

Link copied!

Hi,

You can copy your production environment to sandbox environment.

Please refer to the steps in the following link.

Quick Tip: Copy Production to Sandbox Environment with Power Platform | Stoneridge Software

Was this reply helpful? Yes No
Suggested answer

PerezAguiar Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hey Nikki.

There are a few other considerations.

a) If your production environment has a high consumption on Auditing, you can trigger a copy without the auditing part.

b) there's also another possibility: A minimal Copy. This will copy only solutions, Customizations & Schemas. No relevant data (but will keep system tables).

c) There is also a Microsoft Package that contains sample data.

I think the best approach when Production is too big is a combination of previous points, specially B and C. You can even go further and create a "sample data" (set of excels with dummy data) that you will import for example on custom tables, so right after a minimal copy, you trigger this and then you have a "reduced" test environment.

Regards,

Was this reply helpful? Yes No
Suggested answer

Niki Patel 89 on at

Like (0)

Report
Copy link

Link copied!
Hi,

Great question, full copy for regular refreshes is rarely practical at scale. Here's what works well for D365 Sales Enterprise teams:

Ditch full copy for regular refreshes. Use this instead:

1. Minimal Copy as your baseline
Copies customizations/schema with no data. Then selectively push only what you need for testing.

2. Selective data sync for what actually matters

Power Automate - scheduled flows to replicate Accounts, Contacts, active Opportunities, Price Lists from prod to sandbox

KingswaySoft SSIS Toolkit - the community gold standard for scheduled, filtered D365-to-D365 data sync. Supports incremental loads, field mapping, and error handling out of the box

Azure Data Factory - if you want a more enterprise-grade pipeline with logging

3. Handle storage before any copy

Purge audit logs (biggest storage killer)

Run bulk delete on closed/inactive records older than 2+ years

Offload email attachments to Azure Blob if not already done

Check PPAC -> Resources -> Capacity to see exactly what's eating your storage.

4. Automate post-refresh steps
Always script these to avoid production incidents:

Disable production Power Automate flows

Swap connection references to sandbox endpoints

Set email to "Do Not Send" mode

Disable webhooks/integrations pointing to prod

5. Consider data anonymization
If GDPR/privacy is a concern, run a masking pass on PII fields (names, emails, phones) after sync rather than pulling raw production data.

Bottom line: Minimal Copy + KingswaySoft (or Power Automate for lighter needs) + automated post-refresh script is the most maintainable pattern for regular sandbox refreshes in D365 Sales.

If this was helpful, please mark it as a Verified Answer - it helps others in the community facing the same challenge!

Was this reply helpful? Yes No
Suggested answer

Zhilan 132 on at

Like (0)

Report
Copy link

Link copied!

Hey Nikki,

You can still copy your enviroment without having any issues or having capacity concern by copying only the schema
+ schedule a retenation policy to remove all the unwanted data from your sandbox enviroment.

for now we don't have out-of-the box features to copy/sync automatically between sandbox and production enviroments. you can manually copy it when it's needed.

Regards,

✅If this answer helped you, please consider marking it as Verified, it really helps others in community

Was this reply helpful? Yes No