If you did this in SDK, then you can export the solution from one tenant and import it into another tenant. This will "transport" any custom web services you have exposed (creating C4C SOAP APIs) as well as any web services/WSDLs you have consumed (consuming 3rd party SOAP/REST APIs).
Once you do this you will still need to create a new C4C communication arrangement/communication system in the new tenant since this is tenant specific.
So to answer your specific questions
-> Now, we have to move the web service to production system. So, how the WSDL file will take the production system URL?
It will happen automaticaly or need to change any settings?
RK- Since you will transport the custom C4C web service from one tenant to another one, the WSDL structure will be the same but the FQDN (fully qualified domain name) of the WSDL address will be different since every tenant has a unique FQDN. So in your 3rd party system that is consuming the C4C WSDL/webservice you will need to update the FQDN to the new address of the new tenant.
-> We are also consuming the web service of ERP system, To consume the web service, we have created external integeration in development system. Now, after this object transportation to production, how WSDL will take ERP production URL. shall we ask ERP team to share production copy of WSDL file and create external integeration object for the same?
RK- Again the ERP Basis team will need to need to provide the FQDN of the ERP WSDL/webservice for production ERP since it will be different than the dev/test ERP. If the ERP Basis team transported the WSDL from dev/test to production the WSDL structure will be the same so in C4C all you will need to do is update the communication system/arrangement so that the FQDN of the WSDL/webservice reflects the production address and not the development one.