Yes. If Workflow Conductor is configured to use the Solution Deployment method (the default for Workflow Conductor 1.6 and earlier), workflow solutions are deployed as features at the farm level, activated at the site collection level, and automatically associated with a particular list. A workflow can be activated on a different site collection or associated with a different list using standard SharePoint settings.
If Workflow Conductor is configured to use the Simple Publishing method (the default for Workflow Conductor 2.0 and higher), workflows published to the site or site collection can be associated with a different list. Workflows published to a specific list can be associated only with that list.
Workflows can also be saved as templates that can be reopened, edited, and deployed or published to a different location. Templates can be exported and imported into other SharePoint farms where Workflow Conductor is installed. If you associate a workflow to a different site and widget properties in your workflow are configured with specific list or site names, your workflow will still work if a list or site with the same name exists in the new location.