Your HubSpot setups, as a collection you can deal out.

Snapshot a portal. Bundle what matters into a recipe. Deploy it into any portal in about a minute, and share it with a file.

1 Snapshot 2 Recipe 3 Deploy

Invite-only for now. Sign in with the address your invite was sent to. About sign-in

How it works

Three steps. One screen each.

Trading Cards reads a portal through its Private App Token, keeps a browsable copy, and writes the parts you choose into another portal. The browser never talks to HubSpot and never holds a key.

1

Snapshot a portal

Add a portal by its ID, save a Private App Token, pick what to capture. A scan counts what is there, then a capture stores the definitions. Browse the result like a file manager, with previews and workflow diagrams.

AutomaticManual pickRecords as sample data
2

Build a recipe

A recipe is the set of assets you want to hand on: objects, properties, pipelines, workflows, forms, lists, records. Add them from any snapshot, give it a cover, export it as a file, import someone else's.

Books in the libraryExport · ImportDuplicate
3

Deploy into any portal

Preflight shows what will be created, what already exists, and what is missing. Dependencies come along or map onto what the target has. Name clashes skip or rename. Watch it run on Activity and get an email when it is done.

Skip or renameDependenciesScope check
Snapshots

What a snapshot captures

Pick asset types, or let the automatic mode take everything the key can read. Records come as a sample, a HubSpot list, a property filter, or picked one by one, with their associations and a chosen number of activities.

  • Scan, then capture. The scan counts items per type so you can choose; the capture stores definitions and small facts for filtering.
  • Scopes are checked first. Types the key cannot read are listed with the scope they need, not silently skipped.
  • Browse and export. Open any item, read a workflow as words and a diagram, follow its dependencies, jump to it in HubSpot.
Data model
Property groupsPropertiesPipelines and stagesCustom objectsAssociation labelsLists and segments
Automation
WorkflowsSequences
Marketing
FormsMarketing emailsCampaignsLead scoresCustom events
Content
HubDB tablesKnowledge base articles
Reporting
Dashboards
CRM records
ContactsCompaniesDealsTicketsCustom object recordsOwners and teamsAssociations between records
Activities
CallsEmailsMeetingsNotesTasks
Commerce
ProductsLine itemsQuotes
Under the hood

Built the careful way

Keys stay on the server

Personal Access Keys and Private App Tokens are checked with HubSpot, then stored AES-256-GCM encrypted. The browser only ever sees a masked version.

Sign in by emailed link

No password. A link lands in your inbox, works once, and expires in ten minutes. A session is an httpOnly cookie; only its hash is stored.

Jobs you can watch

Snapshots and deployments are background jobs with progress, a log, scheduling for later and cancel. An email arrives when one starts, finishes or fails.

Each portal is its own

Connect as many portals as you work with. Keys, installs, snapshots and jobs are kept per portal, and every screen says which one it is about.

Pick a card.

Free while in preview. Works with any HubSpot portal you can create a Private App Token or a Personal Access Key for.