Resourcesのすべてのブログ投稿

Re: Salesforce - HubSpot Campaigns | Step 4 | Import Campaign ID data from Salesforce to HubSpot Con

FRaza05 — Fri, 23 Jan 2026 12:03:45 GMT

https://mobile-tyres.co/ provides professional mobile tyre fitting services across the UK.
They offer 24/7 emergency tyre replacement and puncture repair.
Tyres are fitted at your home, workplace, or roadside location.
The service covers cars and vans with a range of branded tyres available.
It is a convenient solution for fast and reliable tyre assistance.

Re: Legacy Standard Sandboxes Sunset: What’s Changing & How to Prepare (FAQ)

LauraRoberts — Thu, 22 Jan 2026 19:38:22 GMT

Our sandbox honestly ends up being a test for integrations and imports/migrations more than anything else, with the tool running, and then we check to make sure it did all the correct things. After each run I'm quite happy to get fresh data and try again with some tweaks. I suppose this means in some ways that it should be relatively low-impact for me to recreate the sandbox each time, but I might be doing 5 tests in a single day so it would be pretty tiresome to need to set up a sandbox each time, including potentially needing to invite test users. I do understand the potential issues with production to sandbox sync when everything is open to changes in both, though I do agree with others that a versioning tool similar to git, particularly the merge conflicts remediation, would suffice here and most of us will be familiar with it. For simple things like mine though, would it be possible to have a different kind of sandbox that would effectively be a copy of production, except the app can be there and not effect the actual production records? In other words, even without version control, if the only things allowed to change the sandbox are the app(s) being tested and syncs from production, have the syncs be manual only and understood to be overwriting everything but the app connection(s). Perhaps this is kind of niche to ask for, but honestly don't devs pretty frequently need to be testing this way? How many of us are just using the app for the API key and all of our code is otherwise external?

I'm also hoping that with the myriad of edit types that don't deploy, that there's some tracker that gives a checklist of things to do in Production, as explicitly and clearly as possible. This would be helpful for instance when a partner is figuring out the setup for a potential new brand, rebranding, or more complex migration/merger of portals. It would also be helpful just for all the people above doing more complex testing/changes while versioning isn't a full feature (and the tracking of these in connection with property history and the like would be a step toward a full versioning solution)

Re: Legacy Standard Sandboxes Sunset: What’s Changing & How to Prepare (FAQ)

hattiefawcett — Wed, 21 Jan 2026 17:32:39 GMT

I've just had to delete and recreate our standard sandbox rather than refresh it, which works, but is pretty painful for ongoing dev and integration work. I'm also guessing the new sandbox will generate new portal and asset IDs (objects, properties, records), meaning code and APIs need updating.

Whilst I love the "push to prod" feature, losing a simple refresh option makes it harder to keep a sandbox aligned with prod over time, and the reduced contact limits make realistic integration load stress testing impossible so we can't even be sure if stuff will break until it's been pushed to prod...

Would also like to see options like ID parity between prod and sandbox (Salesforce does this) or more flexibility around refreshes - both would make standard sandboxes much easier to work with in real-world setups. I get the risks around overwriting from prod to sandbox but with proper process documentation it's not been an issue for us so this new update is actually a lot more extra work.

Re: Legacy Standard Sandboxes Sunset: What’s Changing & How to Prepare (FAQ)

DaleGearhart — Tue, 20 Jan 2026 19:40:28 GMT

Here is another issue I have but this was true with the legacy SB as well. Custom object records. They still have to be exported/imported, and it breaks all associations. An export will have the associated record IDs but they won't match any IDs in the SB. It seems the recommended course of action is to create new properties in all objects, replicate the record id's to these new "production account record id", so on the backend in the SB - you can take your imported data and create a workflow to re-associate.

(1) why are custom object records not included? This is 2026 - cars can parrallel park themselves. But we can't have custom object records included in our sandbox sync?

(2) if they just can't be, then why can't the task of adding the prod portal record id be part of the sandbox creation? It doesn't seem like it would be that hard to create (another) hubspot provided property that is the prod portal record id that is simply the record id value carried over. Its a lot more involved for me to add the property to all the objects and create workflows to update the values.

Re: Legacy Standard Sandboxes Sunset: What’s Changing & How to Prepare (FAQ)

Monjogard — Tue, 20 Jan 2026 15:19:09 GMT

I agree with comments above around not being able to sync from prod to sandbox. So many tiny things are edited and updated in the production environment every other week that the sandbox will never be up to date without an ability to sync assets to the sandbox. If you're concerned about overwriting "stuff ready to be deployed" in th sandbox, then add a feature to the sync where you can select what to keep from the sandbox and what to overwrite with from production.

Like most commenters mentioned above, this means we have to delete and recreate the sandbox every time we prep for a major change. This also then includes updating integrations, connected apps etc. While I've been longing for the the sync to prod feature, removing the sync to sandbox feature will make this change net negative.

Re: 3 Game-Changing Features To Transform Your Lead Scoring

asmith593 — Tue, 20 Jan 2026 13:15:08 GMT

This is a strong breakdown of why the new HubSpot lead scoring is a genuine upgrade rather than a cosmetic change. Features like score limits and “score every time” finally align scoring with buyer intent instead of noisy activity, which makes sales–marketing alignment far more actionable and realistic.

Re: Shape the Future: The 2026 Ecosystem Mentorship Program is Live!

SJMorris — Fri, 16 Jan 2026 23:09:54 GMT

I'm so excited to see how much this program has grown since our 2024 beta! Please don't hesitate to reach out to myself or @Jnix284 to learn more about the program.

And please note this program is not just for developers. If you have any interest in building on the HubSpot platform, we want you to join us. We're especially keen to talk to experienced members of the community who would like to learn collaboratively with newer members of the community and share their expertise.

Re: Legacy Standard Sandboxes Sunset: What’s Changing & How to Prepare (FAQ)

hkampen — Fri, 16 Jan 2026 13:14:22 GMT

Hi,

I understand the possible issues, but I think there are some which can be synched from production to sandbox without concerns.

First of all I miss the views after sandbox creation. Views can be synched without impact if none existing or archived fields in the sandbox are ignored.

To synch fields will be a bit more difficult. If the fields are archived or the options are changed, it can causes conflicts, but I think that can be solved. I do that now with a script.

A subset of elements synched from production to sandbox would really help.

Re: Salesforce - HubSpot Campaigns | Step 4 | Import Campaign ID data from Salesforce to HubSpot Con

Сna — Fri, 16 Jan 2026 13:14:20 GMT

Yeah

Re: Legacy Standard Sandboxes Sunset: What’s Changing & How to Prepare (FAQ)

DKR91 — Fri, 16 Jan 2026 11:58:28 GMT

Thanks for moving forward on this. However I was wondering if it would port over themes/React CMS as well and you could test new deployments like this. Else it's not fully useable since you can't fully test end to end.

168-Hour Executive Framework: Reclaiming Strategic Time in the AI Era

HeatherSmyth — Wed, 14 Jan 2026 18:58:53 GMT

FEBRUARY 10 | Join SVP of Marketing, Kieran Flanagan

With AI enabling 24/7 execution, marketing operations are constantly running. This roundtabale is about strategically deploying all 168 hours available to your organization each week.

Re: Legacy Standard Sandboxes Sunset: What’s Changing & How to Prepare (FAQ)

DWinnyk — Wed, 14 Jan 2026 15:29:24 GMT

I'm excited about this new feature, definitely a big step foward! Thanks for the work!
However, I echo the concerns of other users here.
Key features we need to see in the future:
1. Syncing updates to properties that exist in production.

2. Pull changes from production down to the sandbox

3. Version control (This is probably a HUGE ask, but would be so nice)

Some reasoning:
1. Building good products is an iterative process. Not being able to push changes to existing properties or workflows means we are stuck at single iterations.

2. Easily maintaining alignment between sandbox and production environments is a huge advantage for dev teams and user assurance testing.
3. Being able to push, pull, and roll back changes gives organizations a safety net when pushing big changes. A bad push in the current HubSpot could take hours to undo.

Again, big step forward here with this feature. Super thrilled to roll this out to our organization and thanks for all the hard work on updating the product!

Re: Legacy Standard Sandboxes Sunset: What’s Changing & How to Prepare (FAQ)

CDean — Wed, 14 Jan 2026 14:37:28 GMT

+1 on this being a net negative.

The deployment from sandbox to production is not very useful. It does not push up any edits– only new things. A huge portion of updates are edits rather than new.
The loss of sync from prod to sandbox is huge. Overwriting sandbox junk is a good thing. The entire point of sandbox is trial and error.
Proper version control would solve all of this. A sync screen similar to the de-duplication would prevent accidental loss by choosing which version to keep/overwrite. This would work for both syncing down and deploying up.
The new sandbox creation should have had the option to copy the existing legacy sandbox. This would at least alleviate the problems people have with the extremely short turnaround time on this sunset. If nothing else, please give much more time for updates that cause fires.

Re: The Power of Segments: Smart Targeting, Better Results

BérangèreL — Wed, 14 Jan 2026 12:18:58 GMT

Hi @LMOHAMED, thank you so much for posting in the HubSpot Community!

I’d love to help out, but could you please clarify what you’re referring to?

The more details and context you can share, such as a description of the issue or even a screenshot (making sure there’s no sensitive information), the better we’ll be able to assist you.

Looking forward to your reply!

Thanks again, and have a wonderful day!
Bérangère

Re: The Power of Segments: Smart Targeting, Better Results

LMOHAMED — Wed, 14 Jan 2026 11:39:25 GMT

The company should create a clear structure of duty allocation to anwser questions like, who answers to whom?, who does what?, at what time? etc.

Re: Legacy Standard Sandboxes Sunset: What’s Changing & How to Prepare (FAQ)

Denise_Thijzen — Tue, 13 Jan 2026 20:41:12 GMT

Hi @thorstenheissel, I've reached out over DMs to gather more context!

Re: Legacy Standard Sandboxes Sunset: What’s Changing & How to Prepare (FAQ)

Denise_Thijzen — Tue, 13 Jan 2026 21:50:38 GMT

Hi @StefanWendt

Can you share an overview of what exactly you're looking to migrate? For example:

which asset types
which configurations
do these assets only exist in the legacy sandbox or have they also been manually recreated in production

I'm happy to set up a call to discuss the nuances and see if there are any recommendations. Let us know if that's something you'd like to do. Thanks!

Re: Legacy Standard Sandboxes Sunset: What’s Changing & How to Prepare (FAQ)

Denise_Thijzen — Tue, 13 Jan 2026 20:25:54 GMT

Hi @hkampen, thank you for sharing your perspective. You’re describing a set of workflows we’ve often seen across sandbox users, especially where sandboxes are either long-lived because they're heavily connected to various integrations, or where different teams are doing various things in one single sandbox.

You're right that sandbox → production is the correct direction of travel. As you noted, given that many teams have come to rely on recurrent production → sandbox resyncs to keep things moving, these two realities came into direct conflict and introduced a myriad of risks for maturing the HubSpot Sandbox.

Why production → sandbox sync had to change

The core reason we removed resync / selective sync in the new sandbox architecture is reliability and safety:

Selective resyncs cause sandboxes to diverge unpredictably from production over time, especially when different users were constantly making micro decisions to resync all or selectively sync assets on any given moment of the day.
That constant divergence made it impossible to reliably detect what actually changed in a sandbox.
Without a trustworthy reference state, any two-way or incremental resync introduces a real risk of overwriting production unintentionally or impacting active development in sandboxes.

In other words: production → sandbox resync might have seemed to facilitate short-term iterations, but it fundamentally blocked us from ever delivering a safe deploy to production feature to support enterprise-grade testing and deployment workflows. The decision to no longer support resync isn’t unique to HubSpot, platforms that support deploy to production at scale do not allow ad-hoc resyncs for these reasons.

On syncing individual elements (like properties)

We understand the idea of at least allowing to syncronize individual fields from production → sandbox. The issue is that even individual elements don’t exist in isolation, for example they’re referenced by workflows, integrations, validation rules, lists, emails and so forth. Partial syncs are exactly what created the inconsistencies and blocked us from delivering a reliable and low risk deploy to production feature. So, on the mid/long term, rather than re-introducing this risk, we're focused on:

Reducing the need for users to manually recreate or copy assets in either direction by continuing to deliver support for newer asset types.
Continue to expand the sandbox → production deployment experience to offer a broader and more reliable one.

On the topic of navigating governance such as multiple sandboxes or various teams, I'd recommend reading Smarter Sandboxes for Safer Deployments blog post which delves into the topic providing a brief framework to get teams started.

We're also open to talking with users about the next slate of supported assets needed to get closer to a full mirror of production. So if you're open to it, please let us know and we can get a call scheduled.

Re: The Power of Segments: Smart Targeting, Better Results

ASahu4 — Tue, 13 Jan 2026 10:19:10 GMT

Nice awesome learning

Shape the Future: The 2026 Ecosystem Mentorship Program is Live!

HSyed — Tue, 20 Jan 2026 17:20:20 GMT

Don't just watch the ecosystem evolve this year, shape it.