If you’re worried about anything getting screwed up, fear not, for the customizations that you have to make to ensure the file is completely compatible with Expression are minor.
First off, you cannot add FrontPage Include Pages. Those you have are fine, and you will be able to edit them without difficulties, but you cannot add new ones in Expression via a button. Instead, you’re going to need to add them using HTML. The code for this is:
<!--webbot bot="Include" U-Include="file.htm" TAG="BODY" -->
So, where the “file.htm" spot is, you need to replace that with your Include Page URL. This is pretty straightforward, so, there shouldn’t be any big issues with this portion of customizations.
Moving on, the FrontPage Link Bar will not work in Expression Web. Instead, you need to put the formatted links in a Dynamic Web Template. You can then add this to your website, and configurations to the links will be relatively simple.
For FrontPage Themes, you are going to need to convert them to CSS. Themes are getting pretty old now, and CSS can make global page layout alterations easier. Another small adjustment is FrontPage Shared Borders, which you will have to reconstruct in a Dynamic Web Template.
An important note, the components within FrontPage usually work regardless if you are using Expression Web; however, you are unable to customize or change them to your preferences. So, if you have a FrontPage Shared Border, it will still appear on your website in Expression and on the Internet, but you will not be able to change the border if need be.
The last problem is FrontPage Forms. Again, these will show up and allow the visitor to enter information, but the information will not be sent or received by an email address. To fix this, you need to remove any FrontPage Forms and replace them with ones provided by Expression Web or your host company.