Using custom table data to populate a series of content pages?

Why not to use macro? GlobalObjects.CustomTables["customtable.sampletable"].Items Or To get a particular item you can do .Items.Where("ItemID=1")[0]["fieldname"]

I find way more efficient to have one page to render data from custom table based on item Id or some other unique field, especially for a big custom table. especially because after the first request everything is cached, next request will none or one query to custom table. way more efficient then traditional page structures.

If you want to create a bunch of pages and prefilled them with data - you will have to write a custom import script using API.

I'd second Mike's approach and using the KIT to get the job done. If your content is structured, then I'd recommend AGAINST using editable text webparts on your pages. Structure your page types so you have specific fields for your data and not just a generic catch-all editable text webpart.

Kentico is based on page types and the system is optimized for this specifically. Using custom tables to display your data isn't a fast solution and usually ends up in trouble later.

Mike - Thank you! This sounds like what I need. I'll spend some time with the Import Toolkit to get things set up.

Peter - We currently have data in a custom table like you describe but we're running into some limitations in what we can do with how we display it on the site and in search among other things, so bringing the data into pages more of our current editors can easily manage provides us with advantages.

Brendan - This is our plan for the important data being brought over from the custom table, using specific page fields to keep the precise data into needed formats, but then introducing other elements into the page for editors on top of that.

Thanks to everyone for the help!