This document discusses the differences between Adxstudio v7 and Dynamics 365 Portals. It outlines new features in Dynamics 365 Portals like improved multilingual support, portal comments, feedback, and knowledge management. It also describes changes to access control rules, web templates, and deactivated pages. Finally, it provides an overview of prerequisites and two approaches for migrating from Adxstudio to Dynamics 365 Portals.

2. Functionality differences between
Adxstudio v7 and Dynamics 365 Portals
 SharePoint Document Management
 Shopping cart and payment
If you are using the following functionalities of
Adxstudio portals, they need to be reimplemented
either using out-of-box customization patterns or a
third-party solution

3. Things that are new in dynamics 365 portal
 Data model change for multi-lingual-Dynamics 365
Portals support multiple languages in a single portal
website record in a simplified manner. Previously,
Adxstudio Portals managed language by implementing
a child website record for each language.
 Portal Comment-Dynamics 365 Portals comes a new
entity: Portal Comment (adx_portalcomment). It
doesn’t replace the former portal functionality that
used the Note; however, it enables a more user-
friendly interaction.

4. Things that are new in dynamics 365 portal
 Feedback-Feedback is a new entity introduced with
Portal Capabilities for Microsoft Dynamics 365. It
replaces Idea Votes (adx_ideavote), Idea
Comments (adx_ideacomment), and Blog Post
Comments (adx_blogpostcomments).
 Knowledge management-Dynamics 365 Portal used
Knowledge Article(instead of Articles and Knowledge
Base Record )

5. Things that are new in dynamics 365 portal :
 Access control rules now have a scope
 Web templates are associated to a website
 Deactivated pages have associated localized content
page after migration
 Custom CSS changed
 Image files need proper URLs(for example, no spaces)

6. Adxstudio Migration :Prerequisites
 Microsoft Dynamics 365 CRM 2016 Update 1 or later
 Adxstudio Portal v7.0.0025 or later.
 Application code and solution schema must be
unmodified
 Remove all unsupported features that do not exist or
map to v8 portals
 Complete validation in the sandbox environment
before proceeding to production instance upgrade.

7. Adxstudio Migration: Upgrade Approach
Option 1-
Reimplementation-
 Uninstall, reinstall and manually makes changes
 Possible to use 3rd-party migration tools

8. Adxstudio Migration: Upgrade Approach
Option 2-
Migration
 Configure required Site Settings
 Run PowerShell script
-Install new Solution
-Transitions web pages automatically to the new data
model , but won’t include any of data for new features
 Uninstall Adxstudio Solutions