CiviCRM Community Forums (archive)

i thought i had some luck with node export - but i still had to go through and say eg 3 x contacts and 2 x email fields, but once i did that i found that many of the settings were still there and implemented fine

but guessing it hasn't been like that for you? or did you not try those extra steps

You might also consider the Migrate Webform module. I am not sure if it will work, but just found it while researching this question.
https://www.drupal.org/project/migrate_webform

Looking further into this issue, it seems like part of the difficulty is that Webforms are implemented as nodes(source). This means they have a specific Node ID, which can cause conflicts between deployments.

There is a module, currently with support for Webform 3, that aims to mitigate the Node ID conflict issue while integrating with Features module:
https://www.drupal.org/project/webform_features

I have filed a feature request for webform_features to support Webform 4.x, as it is a dependency for Webform CiviCRM.
https://www.drupal.org/node/2308965

I spent a bit of time working on this a few months back and was able to get webform-civicrm to play nicely with both node_clone and node_export. I haven't tried any others but I can vouch for those two working with the both the 3.x and 4.x versions of webform-civicrm.
See https://www.drupal.org/node/2111713

Thanks Coleman. I just realise that node_export is quite compatible with it.
I tried using node_export to export and import the webforms to some other sites and they all work fine. CiviCRM on that webform is automatically enabled. All the Civi fields are brought back right even custom fields if there are custom fields that match the keys on the sites.

i thought i had some luck with node export - but i still had to go through and say eg 3 x contacts and 2 x email fields, but once i did that i found that many of the settings were still there and implemented fine

but guessing it hasn't been like that for you? or did you not try those extra steps

It is different situation on another site which has exactly same version of modules and CiviCRM. After import, none of Civi fields are there  and CiviCRM is not enabled on that webform.

Then I tried what petednz said and it acually works for this site. I manually enabled CiviCRM on the form and selected the same number of contacts, and then, most of the setups are back automatically even though the contact types and labels need to be set before these happen.

I don't know exactly why the scenario vary on the different sites but guess this is not too bad.

Thanks for helping me out, guys!