The most easiet way would be to restore database backup taken from production site. Another option is to use export/import.

By choosing first one -> probably you will need to adjust some url mapping.

Valdis, what kind of url mapping should he do?

Unless there are some more advance implementations on the web site, a backstage from production environment to development usually is:

• Take a backup of your production environment database.
• Take a backup of your production environment VPP folder.

• Restore development environment database with the .bak file, either to a new database or replace your current database.
  - If you create a new one, change your connectionstrings.config.
  - If you replace your current, be sure that you overwrite all data with the option "Overwrite the existing database (WITH REPLACE)"
• No matter if you chose to create a new or replace, make sure that your SQL user has the proper User Mappings, Roles and Permissions to be able to work with your database.

• Copy the VPP backup into your development environment VPP folder.

• Compare episerver.config on your production environment with your development environment, make sure that the site(s) pageStartId and pageRootId are the same in your development environment as on your production environment.

Browse to your development environment web site and voila! You should have the same EPiServer Content as you had on your production environment.

Note:

• Take a backup of your current development environment database and VPP, just in case something ends up wrong.
• This description is to backstage the EPiServer content from the database and VPP from your production environment to your development environment.
• If your solution contains environment specific settings in the EPiServer database, they will be overwritten since you backstage the entire EPiServer database.
• If your solution contains settings outside the database (for example in configsections or appsettings in your .config files) that refers to a Page Id, these should be backstaged from your product environment as well since these pages might have other Id:s in your production environment compared to your development environment.
• If you have integrations to third party products or solutions, you should give it a thought if you need to do some more changes in configuration or database settings.

For the url mapping I referred to some out-of-the-box cases (that's usually the case) when some baseUri, baseAddress, etc is pointing to production domain. Your list of steps looks really complete. Thanks!