GridLane
Menu
ProductBoardsFeaturesDocumentationFor agenciesHow it worksPricingSecurity
See plansStart 30-day trial
GridLane/Documentation/Snapshots and blueprints
Documentation

Snapshots and blueprints

How GridLane blueprints coexist with HighLevel Snapshots, including overlap, source-of-truth, and safe rollout guidance.

HighLevel Snapshots and GridLane blueprints can both copy reusable client-account configuration. They are not the same tool, and you should decide which one owns each part of a setup.

What HighLevel Snapshots cover

Current HighLevel Snapshots can include:

  • Custom objects
  • Custom fields, including Company custom fields
  • Supported associations
  • Pipelines, tags, custom values, smart lists, workflows, calendars, forms, funnels, and other account assets
  • Configuration, not live contacts or conversations

Snapshots are broad: they are designed to build or update a whole sub-account from a proven template. Loading a Snapshot into an existing account can require conflict decisions when assets overlap.

What GridLane blueprints cover

A GridLane blueprint can capture:

  • Selected custom and standard objects
  • Fields, sections, required flags, and options
  • Association definitions
  • GridLane saved views
  • GridLane permission rules

Blueprints are narrow and versioned. They are designed for repeatable governance, drift checks, and the app-specific views and permissions that Snapshots do not manage.

A blueprint does not include workflows, calendars, forms, pipelines, or record data.

Will a blueprint overwrite a Snapshot?

Not normally:

  • Deployment is add-only.
  • Existing objects and fields are not deleted or overwritten.
  • Missing items can be created.
  • Differences are reported as drift or blocked instead of being silently replaced.
  • GridLane-managed views and permissions can be updated.

A later Snapshot load can still change an object or field and create drift. Review the Snapshot conflict screen before choosing to override or skip an asset.

Choosing a source of truth

For most agencies, the cleanest model is:

  • Snapshot: build the full sub-account, including custom objects, fields, associations, workflows, pipelines, calendars, and forms.
  • GridLane blueprint: manage the post-Snapshot layer—selected object configuration, GridLane views, permission rules, drift, and audit.

If the Snapshot owns custom objects and fields, avoid managing the same objects in a GridLane blueprint. You can:

  1. Exclude those objects when capturing a blueprint.
  2. Use the blueprint for GridLane views and permissions only.
  3. Keep the Snapshot as the source of truth and use GridLane for monitoring.

What happens if both manage the same objects?

  • Identical existing configuration is skipped.
  • A missing field can be created by GridLane.
  • A field type mismatch is blocked.
  • A later Snapshot can overwrite the field and produce drift.
  • Loading Snapshots with overlapping assets can require conflict decisions in HighLevel.
  • Both systems are subject to the 10-custom-object limit per location.
  1. Create and test the Snapshot in HighLevel.
  2. Load it into the target account.
  3. Capture a GridLane blueprint for the settings GridLane should own.
  4. Roll it out.
  5. Run a drift check.
  6. Review the exact differences before applying anything.

If you use both tools, document which system owns each object and field. That one decision prevents most confusion.