Can you go live on HubSpot before Christmas?

Yes, if you kick off by the first week of November and keep the scope to the core sales setup: your pipeline and deals, email connected for every rep, the properties your team actually uses, and a handful of reports. From Tuesday 20 October to Friday 18 December there are 44 working days, about nine weeks, and neither Queensland nor New South Wales has a public holiday in that stretch.

Our four-phase CRM setup timeline puts a standard setup at 4 to 6 weeks from kickoff to go live. Start in the week of 26 October or 2 November and you can be live by early December, with a week to fix things and a freeze before the office empties.

What does not fit is anything heavy: an ERP integration, a migration with years of history from several systems, marketing automation and Service Hub. Plan those as a January phase two. Going live small before Christmas and adding the rest in the new year is far safer than trying to cut everything over in December.

How many working weeks are actually left before Christmas?

We counted them. These are weekdays from 20 October, with the 2026 to 2027 dates taken from the Queensland and NSW government holiday pages.

The holiday dates to plan around:

• Christmas Eve, Thursday 24 December. A part-day public holiday in Queensland from 6pm to midnight. NSW does not list it as a public holiday.
• Christmas Day, Friday 25 December. Both states.
• Boxing Day, Saturday 26 December. Both states add a weekday holiday on Monday 28 December because it falls on a weekend.
• New Year's Day, Friday 1 January 2027. Both states.
• Australia Day, Tuesday 26 January 2027. Worth knowing for your January plan, because plenty of people take the Monday off too.

Other states set their own dates, so check your state government page if your team is spread across the country. In practice, the useful window is shorter than the count. Christmas parties, leave and end of year trading eat into the last fortnight, so treat Friday 11 December as your real go live deadline and the week after as a buffer.

What can realistically go live by mid December?

A buyer on one of our discovery calls put it simply: I need to get this project done before Christmas. Across about nine calls from August to October we heard the same deadline, and the same worry. Another buyer said I just don't want to like shake the ship and rock the boat way too hard.

Both are fair. The answer is to split the work by how much it can hurt you if it goes wrong over the break.

That first group is what most teams actually need on 4 January: one pipeline everyone works from, and emails logged against the right deals.

Is it a change to how people work, or a data migration?

These are two different jobs, and buyers often bundle them into one word: "the move".

• The change is your team working a new way: a new pipeline, new required fields, logging calls in HubSpot instead of a spreadsheet. Its risk is people. It needs training, a few weeks of use, and someone answering questions.
• The data migration is moving records: contacts, companies, deals, notes and emails from wherever they live now. Its risk is volume and quality. It needs a field map, a dedupe and a test import on a sample before the full run.

You can do the change before Christmas with a very small migration, just the open deals and the contacts on them. The years of history can follow in January, once the property structure has been in use for a month and you know it fits. Our data migration checklist covers the January half.

Is it riskier to cut over in your busiest weeks or your quietest?

Both carry a risk, and they are different.

• Busy weeks. If December is your peak, nobody has time to learn a new screen. Reps fall back to the old spreadsheet, and that habit comes back with them in January.
• Quiet weeks. Go live on 21 December and the team uses it for three days, then forgets it over the break. Nobody is around to notice a broken form or a workflow firing on the wrong contacts.

The safest spot is go live with at least one or two weeks of normal trading before your freeze. That gives the team enough use for the new habits to start, and gives your partner enough time to fix what testing missed.

The week-by-week plan from 20 October

This follows the four phases and their durations, with week 1 starting on 26 October.

The four-phase post puts the post-launch review in weeks 8 to 10. With a shutdown in the way, hold it in the second half of January, which still falls 30 to 60 days after a go live in early December.

The freeze window. From Monday 14 December, nothing new goes into the portal. The only changes are fixes to what is already live, made by the person who built it. If you cannot get to go live by Friday 11 December, move go live to January and use December for discovery and the build.

Who needs to be available:

• The person who signs off the architecture, inside the two days after it arrives.
• Your sales lead, who will own the pipeline and the reports.
• Someone with admin access to Google Workspace or Microsoft 365 and the website.
• Every rep, for their training session.
• Your partner's builder through to the freeze, and someone on both sides in the first week back.

What not to do before Christmas

• Do not switch on nurture emails or sequences that keep sending over the break with nobody checking replies.
• Do not turn off the old system. Keep it read only until the January review.
• Do not run a full history import in December. If it goes wrong on 18 December, you live with it until mid January.
• Do not let HubSpot write into your ERP or accounting system for the first time in the last fortnight.
• Do not change your website forms the week before a shutdown, unless someone is watching submissions.
• Do not change the architecture after sign-off to squeeze one more thing in.

Your January phase two list

• Post-launch review, in the second half of January: what the team uses, what they skip, which reports get opened.
• Historical data migration, mapped against the properties the team has now used for a month.
• ERP or accounting integration, scoped field by field. Our ERP integration guide sets out what to sync first.
• Marketing automation: lifecycle stages, lead routing and nurture, built on contacts that are now clean.
• Service Hub, if support is in scope, with its own training.
• A plan for the first 90 days of adoption. Our 90 day adoption plan covers it.

Frequently asked questions

Can you go live on HubSpot before Christmas 2026? Yes, for a core sales setup, if you kick off by early November. A standard setup takes 4 to 6 weeks from kickoff to go live, and there are about nine working weeks between 20 October and 18 December.

How many working days are left before Christmas 2026? 44 weekdays from Tuesday 20 October to Friday 18 December, and 48 to Thursday 24 December. Queensland and NSW have no public holidays in that window.

Is Boxing Day 2026 a public holiday on Monday 28 December? Yes in Queensland and NSW. Boxing Day falls on Saturday 26 December, so both states add a weekday holiday on Monday 28 December.

What should wait until January? ERP integrations, full history migrations from several systems, marketing automation and Service Hub. These take longer and are the riskiest to leave running over a shutdown.

When should a HubSpot change freeze start before Christmas? We suggest Monday 14 December. Go live by Friday 11 December, then make only fixes to what is already live until the office closes.

Sources

• Public holidays, Queensland Government, for 2026 to 2027 Queensland dates including the Christmas Eve part day.
• Public holidays, NSW Government, for 2026 to 2027 NSW dates and the Boxing Day additional day.
• Connect an individual work email, HubSpot Knowledge Base, for supported inboxes and email logging.
• The Four-Phase CRM Setup Timeline for a Growing Australian Business, Neighbourhood, for phase durations and what extends them.

---

Want the pre-Christmas scope and the January list written down for your business? See our RevOps and HubSpot work, or talk to us.