I am migrating a legacy static HTML site over to DNN and am looking for ways to reduce the migration effort.  The site has about 100 pages and I would like to be able to create the empty pages through some automated import process, and then I can delegate the task of copy/pasting the existing content over to the new pages.

Looking at the database, its structure seems pretty straightforward.  I am wondering if it is safe to just write a SQL script that does a bunch of inserts to the dnn_Tabs table, using the data I can see for the few pages I manually created as a template.

While I'm comfortable in SQL and ASP .NET, I am pretty much a newbie with DNN and am nervous there might be more to it.  I've worked enough with complex apps like SAP to know that reverse engineering just by looking at the db schema is dangerous.  Is there stuff done at the file system level or in other tables in DNN when you create a page manually that I will miss or corrupt if I just go creating new rows in dnn_Tabs?

Thanks, Pat

you should definately add pages and module using BCL as there are additional tables that need to be filles as well, as tabpermissions, modulepermissions, modulesettings,...