For an update of a release 3.x to 4.0 version I suggest the following: take this opportunity to re-engineer your website :-) Many things have change in the R4 release, it will be the best to do a fresh start and copy your existing templates, stylesheets etc. bit by bit to the new system.
The R4 has a system for including custom design elements, so that further updates will be much easier. See (?Naming Rules for custom Elements?).
And R4 contains a powerful component system with which you can store common used HTML parts in a central place and re-use them in templates. That will make your templates much easier to read. So, while re-engineering your site with the R4 release, take advantage of that and put as much code in components as possible
Recommended steps:
Follow all the instructions from the (?Installing the system?) topic. Make sure you installed the new openwebcms35.jar.
Create a new database based on the openwebcms.nsf database from the R4 package.
Open the translator.nsf, hit 'inject to target database' and choose your new OpenWebCMS? database. That injects language data into the database.
Copy basic settings from your old to the new database.
Copy Resources (files, javascript) from the old to the new db.
Copy areas and stylesheets from the old to the new database.
Copy templates from the old to the new database. Then check your templates for common used code and move that to components. Be happy that you can re-use central stored code in multple templates.
Copy content types from the old to the new database. Edit and re-save every type.
Copy searchresult templates, edit and re-save them.
When copying content documents they will get a new internet key - thats bad during this migration.. open the agent 'onPaste' and comment out the 'doc.save' call.
Copy some of the most important content documents (homepage and some others), restart http task and see if the site works.
If the site basically works, copy the remaining content documents.
If everything copied fine, re-activate the 'doc.save' in the agent 'onPaste'.
If you made custom modifications to OpenWebCMS? design elements, re-engineer them bit by bit using the new Naming Rules for custom Elements.