There are two distinct project types in FlexDeploy.

Utility projects - used for administrative and/or maintenance type of tasks like start server, stop server, provision environment, install software etc. Utility projects do not have any version and hence do not have any life cycle through environments.
Regular projects - used for build and deploy of code/configurations. Jenkins may have many jobs to cater various environments, but in FlexDeploy you will have one project that will be used for build and deploy to all environments for specific piece of code/configurations. For example, Java EAR application or SOA Suite composite are some examples of FlexDeploy projects. Each project has build and deploy workflow appropriate for type of code/configuration being managed.

You need to first figure out type of projects that will be necessary in FlexDeploy.

There are few different types of workflows in FlexDeploy. Workflows are reusable unlike Jenkins are used across many similar types of projects.

Utility workflow - used for administrative and/or maintenance type of tasks. This does not deal with artifacts.
Build workflow - used for performing build mostly based on source controlled files, but at times can pull files from development environment to perform build. This workflow would be generating artifacts.
Deploy workflow - used to deploy artifacts generated by build workflow. Deploy workflow is submitted against specific environment, so there is no need to create workflows per environment, you can have logic to perform environment specific tasks in the workflow.
Test definition workflow - mostly available out of box but you can create custom workflows to run tests.

Prepare workflows

Define topology

Define environment, instances and endpoints to describe physical topology and provide necessary properties like folder paths, credentials, URL etc.

Projects need to be configured with source control location(s) and workflows.
Utility projects will have utility workflow reference and regular projects will have build and deploy workflow reference.
Configure properties necessary at project level.

Now you are ready to perform executions against newly created projects.