How-to
Remove a blueprint installation
Removing a blueprint installation archives every component it created in one step: its collections, stages and pipelines, templates, filters, and automations. Do it soon after a mistaken install; once your own work depends on those components, removing them takes that work down with it.
Removing a blueprint installation archives every component it created in one step: its collections, stages and pipelines, templates, filters, and automations. Do it soon after a mistaken install; once your own work depends on those components, removing them takes that work down with it.
Requirements
A role that can manage blueprints, collections, and automations.
When to remove one
- You installed the wrong blueprint, or with the wrong settings, such as a campaign name you did not mean.
- You installed a second copy by mistake, which was created alongside the first under a suffixed name.
- You tried it, and it does not fit. See Blueprint vs manual setup.
Steps
- List what the installation created. The install summary names every component; see What is inside a blueprint.
- Check what depends on it. Your own automations that use its collections, references from your collections into its collections, entries you have added, views your team relies on.
- Move what you want to keep. Entries in its collections are archived with them.
- Remove the installation. Every component it created is archived together.
Notes and limitations
- Only what the installation created. Components you chose to reuse during the conflict check, instead of creating new ones, belonged to you before the install and are not removed.
- Archived, not erased. Components are archived rather than deleted outright.
- The CRM blueprint is installed with every new business and holds your core sales collections. Removing it removes Companies, Contacts, Leads, and Deals; it is rarely what you want.
- Removing is not the same as adapting. To change parts of a blueprint you are keeping, see Adapt a blueprint to your business.
Related
For installing, see Install a blueprint.
Frequently asked questions
What does removing a blueprint remove?
Everything the installation created is archived together: collections, stages and pipelines, templates, filters, and automations.
Will removing it delete collections I already had?
No. Components you reused during install belonged to you before and are not removed.
Should I remove the CRM blueprint?
Rarely. It holds Companies, Contacts, Leads, and Deals, and removing it archives them.