HubSpot to Capsule custom field limit: counter added

When you move HubSpot data into Capsule, Shuttio's field review now shows a counter in the form "N of 150 Capsule custom fields". The counter updates as you tick and untick fields. If the ticks would put the account over 150, the review says how many fields to untick, and Shuttio refuses to start the sample until you do.

HubSpot-defined properties that are calculated or read-only now start unticked when Capsule is the destination. You can tick any of them.

What changed

Shuttio treats 150 as the limit of custom fields per Capsule account, counted across parties, opportunities and projects. The total covers the fields the account already holds, not only the ones a single move adds. HubSpot defines properties of its own, and each ticked one with no match in Capsule creates a custom field.

Three things are different now:

• A counter in the field review. N is the number of custom field definitions the Capsule account already holds, plus the fields your current ticks would create. Shuttio reads the account's definitions live from parties, opportunities and projects. A field that matches an existing definition adds nothing to the count.
• A refusal at the start. If the total is over 150, starting the sample returns a message instead of running. The message gives the number the account holds, the number the move would add, and how many fields to untick.
• HubSpot system fields off by default. A property that HubSpot defines, and that is calculated or read-only, starts unticked for Capsule. Its row carries the note "HubSpot system field — off by default to save Capsule's 150 custom fields".

Some fields stay ticked even if they look like system fields. These are built-in matches, the record id, the match key, links, companion columns and required columns. Other destinations are unchanged: the system-field default applies to Capsule only.

How to use it

1. Pick HubSpot as the source and Capsule as the destination, connect both, and choose your objects.
2. Open the field review. Read the counter, for example "132 of 150 Capsule custom fields".
3. Look for rows with the note "HubSpot system field — off by default to save Capsule's 150 custom fields". They start unticked. Tick one only if you need that value in Capsule.
4. Tick and untick fields. The counter changes with each tick.
5. If the counter passes 150, the review shows a sentence of this form: "This would pass Capsule's limit of 150 custom fields. Untick 3 fields to continue." Untick that many fields. People and companies share the same definitions in Capsule, so a field with the same name on both counts once.
6. Start the free sample. If the total is still over 150, you get the refusal message. It also suggests deleting fields you do not use in Capsule, which lowers the number the account holds.

The counter is advice while you review. The refusal at the start is the actual gate, and the server runs it again against the account's live definitions.

What it does not cover

• An account Shuttio cannot read. If Shuttio cannot read the Capsule account's field definitions, there is no counter and no block. The move can start.
• Other plans. Shuttio saw the 150 limit on one Capsule plan, Growth, on 9 November 2026. It has not checked other Capsule plans, so the limit on them may differ.
• Other destinations. Attio, Clarify and Odoo do not get this counter or this default.
• Other sources. The system-field default relies on a flag that only the HubSpot connection sets.

FAQ

Why are some HubSpot fields unticked when I open the review? They are HubSpot-defined properties that are calculated or read-only. Every custom field counts against the 150, so these start off. Tick the ones you need.

The counter is already high before I tick anything. Why? The number includes the custom field definitions the Capsule account already holds, read live from parties, opportunities and projects. Fields that exist in Capsule before the move count toward the 150.

Can I start the sample if the counter shows more than 150? No. Starting the sample is refused until the total fits. Untick the number of fields the message names, or delete unused fields in Capsule, then start again.

To try it, start a migration at shuttio.com. The sample copies 50 records per object, so you see real data before the full run.