Skip to content

Merging Diagrams

Merge combines another saved .json file into your current diagram, instead of replacing it — useful when a teammate has been working on a different part of the same infrastructure, or when you’re stitching together diagrams from different sources.

Choose File → Merge another diagram… and pick a file. Merge only operates on Engineer View, and leaves your compliance rules as they are.

When it’s done, a message tells you what happened — how many devices and networks were added, how many were recognized as already present, and how many existing devices gained new details.

How Schema decides what’s “the same” device

Section titled “How Schema decides what’s “the same” device”

To avoid creating duplicates when you merge two diagrams that both describe some of the same infrastructure, Schema tries to match incoming devices to ones already on your canvas:

  1. By IP address first — if the incoming device has an IP address and it matches an existing device’s exactly, they’re the same device.
  2. By name, if no IP match — Schema falls back to comparing names, ignoring case. Two devices that both have IP addresses, and different ones, are never treated as the same however they’re named; and a device with no name never matches on name.
  3. Otherwise, it’s new — the incoming device is added.

The same name-matching applies to zones and network segments — a segment named “DMZ” in the incoming file merges into your diagram’s existing “DMZ” segment rather than creating a second one. A segment nested inside a zone is matched within that zone: an incoming “Web” segment inside “Production” merges into the “Web” inside your “Production” zone, not into a “Web” somewhere else.

If the incoming file shows one machine several times under the same name — once in each zone it serves — each copy is matched only against a device of that name in the same segment, so a copy for a zone you don’t have yet is added, not mistaken for the one you do have.

When an incoming device matches one you already have, your device is kept — but any detail it’s missing that the incoming copy has (an owner, an OS, a serial number) is filled in. Details you’ve already set are never overwritten.

Anything that doesn’t match existing content is placed to the right of everything currently on your canvas, keeping the incoming diagram’s own layout. New devices merging into an existing segment or zone are offset slightly within it. Containers automatically grow to fit whatever ends up nested inside them, and nested segments stay nested.

Incoming connections are remapped to point at whichever device they matched to (existing or newly created), and any connection that would duplicate one you already have is skipped.

The same matching logic is used by Importing Devices, which is why importing an updated asset list adds only what’s new.