Workflow deploy into production environment

That depends. Your post left out a few details. When you speak about having production databases and sharpoint sites, do the databases which you developed against in development exist in your production environment? Is the structure of those artifacts the same in development in production?

If these are all new artifacts, you will need to move the sql database objects and sharepoint lists into your production environment first, before attempting to deploy your K2 solution. The high level order of dependencies are: Non-K2 Artifacts (Databases, SharePoint, Etc.) --> K2 Service Instances --> K2 Smart Objects --> K2 Workflow --> K2 Forms.

Until the nonK2 artifacts are deployed, you won't be able to refresh or configure service instances which will block successful deployment of any of the downstream components (smart objects, workflow, forms)

If you have moved the nonK2 artifacts into production OR you developed against replicas of those artifacts that match production in naming conventions and structure then, yes, you should be able to seamlessly deploy into your production environment. It will all hinge on how you have developed your solution and if you have properly managed the nonK2 artifacts.

Hope this helps.

S.