Set, change or remove a customer’s parent
Review a parent relationship before saving, with revision checks and protection against circular company structures.
Where to goSales CRM → Relationships → Account hierarchy → Customer → Change parent
Before you start
Use your own authorised staff account in the intended Pixie CRM workspace. The Sales CRM module must be available and your role must include the permissions stated above. Existing leads, customers, communications and customer portal pages retain their normal access rules.
Follow these steps
- Open the intended customer and choose Change parent.
- Use Find a parent customer and Find parents to search existing accessible companies.
- Choose the intended Parent customer. To detach the customer, explicitly choose No parent customer.
- Enter a reason describing how the relationship or removal was verified.
- Choose Review parent change and compare Current parent with Parent after saving.
- Confirm the review checkbox, then choose Save reviewed parent.
- Reopen or refresh the hierarchy and check the parent, retained subsidiaries and relationship history.
Behavior and limits
- The separate Manage customer account hierarchy capability does not grant native customer access. Existing staff permissions are not automatically expanded.
- A customer cannot be its own parent, and a branch cannot move beneath one of its descendants. Circular relationships are rejected.
- Every resulting branch must stay within 25 levels, including the selected customer’s descendants. The workspace supports at most 10,000 current parent links.
- Changing a parent moves that customer’s branch. Its direct subsidiaries remain linked to it; their own records and parent links are not rewritten.
- The reason is required and supports up to 1,000 characters. Changing the selected parent or reason clears the prior review.
- Saving rechecks current access, customer labels, the relationship version and the current graph. Another hierarchy change after review requires a fresh review, even if it affected a different branch.
- Concurrent branch moves are serialized within the workspace to prevent two individually valid changes from creating a cycle together.
- Saving an unchanged parent returns the current state without advancing its version or adding another history event. A retry of the latest completed save does not duplicate it.
- A missing or inaccessible old parent can be replaced or removed by an authorised editor of the selected customer. The new parent must be accessible.
- Removing a parent is reversible by selecting and reviewing the intended parent again. It does not delete the customer or its subsidiaries.
Check it worked
- Check both company names and the reason in the review panel.
- After moving a branch, verify its direct subsidiaries are still present.
- After removal, confirm No parent customer recorded and the saved history entry.
Troubleshooting
- For a circular hierarchy error, choose a parent outside the selected customer’s descendant branch. Your edit fields remain available.
- For a depth error, reduce the resulting branch depth before saving.
- For a version or hierarchy conflict, reopen the latest customer structure and review your intended change again.
- If a new parent becomes unavailable, choose an accessible company or No parent customer.
- If the final save response is interrupted, refresh to check the current relationship before submitting another change.