Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2021 Release Wave 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
We have 2015 on premise crm application where dev environment is unmanaged and other ( test ,stage and prod) are managed .
we have upgrade plan
And also for every 6 months we want to reimage the dev environment with prod ( just a replica) to have right data. but we have to manually delete the prod org and restore the backed up dev db to unmanaged back for development
so due to this overhead, we want to make the prod also unmanaged from managed.
we have the below links to covert managed to unmanaged. but could you please update us is it supported and it will give some issues during upgrade to dynamic 365?
Can you please provide how to get the prod data into Dev other than above re image methos?
I believe you are using development environment only for development activity so you may need to take care additional activity to maintain your ongoing development activity or customization at development environment if you follow restored organisation or Database taking from production.
I saw the link you have shared to convert managed to unmanaged, I am totally disagree with this approach and although seems this not Microsoft recommended and you may face lot of issues with this.
Considering above its always best practice to do data migration. You may use kingswaysoft , scribe tool or ssis to migrate your data from production to development environment.
As the post from Magnetism states, as well as the unsupported database changes from the second post, this can cripple your solution. I would highly recommend against it and for you to find a different solution.
As Goutam suggested, try going the route of SSIS/Kingswaysoft or Scribe and do a data migration.
If you are planning to do this every 6 months, invest in a data migration solution instead of an unsupported one that can destroy your production environment.
Hope this helps.
Business Applications communities