When you split a process into two pipelines, such as qualification and sales or sales and implementation, do you carry the custom fields forward into the new pipeline? I have some fields that are unique to each pipeline, but there are many others that will be used in both pipelines. Is the best practice enable the custom field only in the first pipeline and go back to look it up in the opportunity in the prior pipeline, if you need it. Or is it better to enable the custom field in all pipelines where it’s relevant and carry the value forward when opportunity is closed in the first pipeline and created in the next pipeline? Example: I’m implementing for a residential design/build firm with a qualification pipeline followed by a Design sales pipeline and a construction sales pipeline Some project are design-only or construction only but some go through both. The address of the project (which often isn’t the clients’ current address so doesn’t really belong on person) is a custom field that could be replicated in all three pipelines or I could only put it on the qualification pipeline opportunity. Project Address is unlikely to change but there are other custom fields like the Project Scope or Start Date that will likely be updated as the project progresses through sales. What are your thoughts?
Best answer by Michelle from CopperView original