Parent organizations and subsidiaries

Companies often belong to bigger ones: Acme UK and Acme Deutschland are part of Acme Group. Give an organization a Parent organization and the app keeps that structure for you. The parent's page lists its Subsidiaries, the Organizations list can show and sort by each organization's parent, and conditions, the list's AI search and the assistant can all find a company's subsidiaries.

What you can do here

  • Set an organization's Parent organization on its page, in the Relationship section.
  • See a parent's Subsidiaries on its page, add one, or take one out.
  • Show a Parent organization column on the Organizations list, and sort by it.
  • Find organizations, or the contacts at them, by their parent: in a filter, a segment or a journey condition, or by asking the list's AI search for "subsidiaries of Acme Group".
  • Ask the assistant which companies are part of a group, or to make one company a subsidiary of another.

The Parent organization field

Parent organization is a built-in organization field in the Relationship section, after Type and before Owner. It names the organization this one belongs to: give Acme UK the parent Acme Group, and Acme UK is one of Acme Group's subsidiaries. An organization has at most one parent. A parent can have any number of subsidiaries, and a subsidiary can have subsidiaries of its own.

Picking a parent

An empty field reads Add parent organization…. Click it, and a search opens in place: start typing a name or a domain. It's the same search as a contact's Organization field:

  1. Matching organizations appear as you type, with their domain and how many contacts they have. Organizations you've archived aren't suggested.
  2. Pick one to make it the parent. If the parent isn't in the app yet, choose Create organization “…”: the organization is created and becomes the parent in one step.
  3. The parent shows as a chip. Click its name to open it, or click × to clear the parent.

The list never offers a choice that would break the tree: not the organization itself, and not one of its subsidiaries, or one of theirs (see One company, one place in the tree). Type the exact name of one of those and the list says why it can't be the parent, instead of offering to create a second organization of that name. If a change is refused all the same — someone changed the hierarchy a moment ago, say — the reason shows under the field.

A parent you later archive stays the parent: the chip shows it with an Archived tag.

Parent organization isn't a merge field, so no email or text prints it. With Dynamics 365 connected, it syncs with each account's Parent Account both ways, while organization sync is on and the mapping's Parent Account row isn't set to Ignore — see An account's parent.

One company, one place in the tree

Organizations form a tree: no organization can end up above itself.

  • An organization can't be its own parent. If you try — through the API, say — the change is refused with "An organization can't be its own parent."
  • An organization can't become a subsidiary of a company that is already part of it. If Acme UK is part of Acme Group, making Acme Group a subsidiary of Acme UK is refused: "Acme UK is already part of Acme Group, so it can't be Acme Group's parent."
  • There is no limit to how many levels a hierarchy has.

This holds however the parent is set — on the page, on the Subsidiaries card, by the assistant, through the API or from Dynamics 365, where a parent that would break the tree isn't applied and Sync health says why — even when two people change parents at the same moment. If the parent you picked has just been merged into another organization, the organization it was merged into becomes the parent. If it has been deleted, the change is refused.

Subsidiaries on the parent's page

The Subsidiaries card is in the right column of every organization page, under Tags. Its heading counts them — "Subsidiaries · 3" — and it lists them by name, ten at a time; Show more lists the next ten. Each row shows the organization's name, which opens its page, and how many contacts it has. Archived subsidiaries are listed too, marked Archived.

  • Add subsidiary opens the same organization search. It never offers this organization, one above it, or one that is already its subsidiary. An organization that belongs to another parent is marked "Part of Beta Holdings", and picking it asks first: "Move Acme France from Beta Holdings to Acme Group?" Move moves it; Cancel changes nothing. Type the exact name of one it leaves out and it says why — "Acme UK is already a subsidiary of Acme Group.", say. You can't create an organization here: a subsidiary is an organization you already have.
  • × on a row — Remove from subsidiaries — clears that organization's parent. Nothing else about it changes.

An organization with none shows "No subsidiaries." If an add or a removal is refused, the card says why. If that organization's parent changed since the page loaded, it says "<Child>'s parent organization changed — refresh and try again." and changes nothing.

The Parent organization column

On the Organizations tab, Display → Columns offers Parent organization. It's off to start with, since most organizations have no parent, and a saved view keeps its own columns. Each cell shows the parent's name — click it to open the parent — with an Archived tag when the parent is archived.

Click the column's heading to sort by the parent's name, A to Z or Z to A. Organizations with no parent come last.

Conditions

Two fields describe an organization's parent in conditions.

Parent organization

"Parent organization is Acme Group" — you pick the organization from the same search, so the condition holds the organization itself, not its name. The segment builders (the Organizations filter, Save as segment and contacts segments) and the journey If/Else builder offer =, ≠, is empty (no parent) and is set. A journey trigger's conditions offer is, is not, is any of, is none of, is empty and is not empty. Because it holds the organization, it keeps working when Acme Group is renamed, and when Acme Group is merged into another organization: its subsidiaries move to the organization kept, and the condition follows them. A condition whose organization was archived later shows it with an Archived tag.

Parent organization name

"Parent organization name contains Acme" — the parent's name, as text, with the usual text conditions. It's empty for an organization with no parent. It checks the parent's current name, so a condition on an old name stops matching after the parent is renamed, like a condition on Name.

Where they work

Both fields work:

  • in an organization segment, and in the Organizations tab's Filter and Save as segment;
  • in a contacts segment, as "Organization · Parent organization" and "Organization · Parent organization name": "Organization · Parent organization is Acme Group" reaches the people at Acme Group's subsidiaries;
  • in a journey's If / Else conditions and its trigger's conditions, under Organization.

Neither field can be watched by the Organization updated trigger: neither can be picked in its Organization fields, and a journey that watches either field can't be published. A change of parent does count as an update to the organization — made on its page, on the Subsidiaries card, by the assistant or through the API, by a merge that moves it, or in Dynamics 365 — so a journey on Organization updated with no fields picked starts for its contacts. A parent Dynamics 365 fills in the first time the app reads an account's parent starts nothing, unless that parent account hadn't synced yet and is brought in afterwards — read by its id, say (see An account's parent). To act on the parent when a journey runs, check it in a condition.

Switch the Organizations tab's search box to AI mode (the ✨ button) and ask in plain words:

  • "subsidiaries of Acme Group" lists the organizations whose parent is Acme Group;
  • "Acme Group and its subsidiaries" lists Acme Group too.

On the Contacts list, "people at Acme Group's subsidiaries" lists the contacts at them.

The AI search knows a parent by its name, so it writes a Parent organization name condition — open Filter to see it. Before you save it as a segment, you can change it to Parent organization and pick the organization, so the segment keeps matching if the parent is renamed. Ask the assistant in a session to save such a segment and it looks the parent up and saves the condition on the organization itself.

When organizations are merged

When you merge organizations (see Merging duplicates):

  • Their subsidiaries move to the organization you keep. Each one that moves counts as an update to it, as a change of parent on its page does.
  • The kept organization keeps its own parent. If it has none, it takes the parent of the first merged organization that has one — but never a parent that is part of the merge or now below the kept organization, which would break the tree.
  • A parent inside the merge is dropped. If the organization you keep was a subsidiary of one you merge into it, and no other parent fits, it ends up with none.

The merge dialog says what will happen before you click Merge organizations: "2 subsidiaries move to Acme UK.", the parent among the empty fields it fills from a merged organization when the kept one takes that organization's parent, and "Acme UK will no longer have a parent organization." when it loses its own. When the assistant merges organizations, its approval card says the same two things.

Archiving and deleting

  • Archiving a parent changes nothing for its subsidiaries. They keep it as their parent, shown with an Archived tag. Archiving a subsidiary changes nothing either: the parent's Subsidiaries card still lists it, marked Archived. An archived organization is never suggested as a new parent, but one that already is a parent stays one.
  • A parent with subsidiaries can't be deleted. Its ⋯ menu has no Delete organization while any organization — archived ones included — names it as its parent, even when no contacts and no CRM record are linked to it. Give its subsidiaries another parent, or remove them with × on the Subsidiaries card, and Delete organization comes back once nothing else is linked to it. If a subsidiary is added at the last moment, the delete is refused and the page says why — for example "Give its 3 subsidiaries another parent first."
  • Deleting a subsidiary needs nothing extra: its parent simply has one subsidiary fewer.

Working with the assistant

In a session the assistant can:

  • tell you an organization's parent and list its subsidiaries — "Which companies are part of Acme Group?" (it's shown up to 20 of them, and how many there are in all);
  • set, change or clear a parent when you ask — "Make Acme UK a subsidiary of Acme Group", or "Acme UK is no longer part of Acme Group". It looks both organizations up first, and when two have the same name it asks you which one you mean. This doesn't need your approval, like changing an organization's type or owner;
  • explain a change it can't make: when the organization you named as the parent is already part of the other one, it tells you so — it never changes another organization's parent to make it fit.

When you @-mention an organization, the assistant also sees its parent's name and how many subsidiaries it has. It sets a parent only when you ask, never from what it found researching an organization on the web. Routines, automations and journeys can read an organization's parent and subsidiaries, but they can't set or clear one.

Through the API

The public API reads and writes the parent as parent_id. An organization's answer carries parent_id and parent (the parent's id and name). POST /organizations, PATCH /organizations/{organization_id} and POST /organizations:bulk take parent_id, and null clears it. In a bulk request, a row's parent_id names an organization that already exists, not one created by an earlier row of the same request. A change that would break the tree is refused with the sentences above, and a parent that doesn't exist with a 422 about parent_id and a sentence saying why. Changing the parent moves updated_at, so updated_since finds the change. See the API reference.

Not available yet

  • Adding up a group's contacts and activity on the parent's page, or a condition that matches anywhere in a group, its subsidiaries' subsidiaries included.
  • Syncing the parent with HubSpot or Pipedrive. With Dynamics 365 it syncs (see An account's parent).
  • The parent and the subsidiaries in an organization's AI summary and its account plans.
  • Watching the parent in an Organization updated trigger's fields.
  • Printing the parent's name in an email or a text.
  • Parent organization columns on the Contacts list.
  • A Parent organization field in the New organization dialog: set it on the organization's page once it's created.
  • A view of a whole group at once: a page shows one level of subsidiaries.

FAQ

Q: Can an organization have more than one parent? A: No. An organization has at most one parent; a parent can have any number of subsidiaries.

Q: Why isn't the organization I want offered as the parent? A: It's archived, it's this organization, or it's already part of this one — one of its subsidiaries, or one of theirs. Unarchive it, or give it another parent first.

Q: Does making a company a subsidiary move its contacts? A: No. Contacts stay linked to their own organization. The parent's Subsidiaries card lists the subsidiaries, not their contacts.

Q: If I rename the parent, do my conditions still match? A: A Parent organization condition does: it holds the organization. A Parent organization name condition checks the name, so update it after a rename.