create pages programmatically and also populate their content?

Yes, it is possible. AEM provides various APIs and tools that allow you to automate the process of creating and migrating pages with their content, but, It's essential to thoroughly understand the structure of your existing project, the content types, and the relationships between different pieces of content. Plan out your migration strategy, including how you'll map content from the old system to AEM's structure, templates, and components.

Consider the following available resources:

1. Use AEM APIs: AEM provides RESTful APIs and Java APIs that allow you to interact with the AEM repository programmatically. You can use these APIs to create pages, update content, and manage assets. The AEM Java API, in particular, provides a high level of control over content creation and manipulation.

2. Content Import Tools: AEM offers tools like the Content Package Maven Plugin that allow you to define your content structure and migrate it using versioned content packages. You can create a content package that includes the page templates, components, assets, and content required for your project and then deploy it to AEM instances.

3. Scripting: You can use server-side scripting languages like Groovy or JAVA to automate content creation and population. This could involve writing scripts that iterate through your existing content and programmatically create AEM pages and populate them with content.

4. Custom Workflow: You can design custom workflows using AEM's Workflow Model Editor to automate the migration process. Workflows can be triggered when content is imported or based on specific events, and they can perform tasks such as creating pages, setting properties, and populating content.

5. Template-Based Pages: Define page templates and components in AEM that closely match the structure and design of your existing project. Then, you can programmatically create new pages based on these templates and populate them with content.

6. Metadata and Tags: Leverage AEM's metadata and tagging capabilities to help categorize and organize your content during migration. This can make it easier to automate content population based on metadata.

With that said, I suggest examining the structure you intend to replicate. Subsequently, develop a script that constructs the structure outlined in your analysis, and finally, execute the script.

I hope this helps