# Webinar: Meet the Discourse Customer Projects Team

**URL:** https://meta.discourse.org/t/webinar-meet-the-discourse-customer-projects-team/370693
**Category:** Events
**Tags:** webinar
**Created:** [June 18, 2025, 1:15pm UTC](https://meta.discourse.org/t/webinar-meet-the-discourse-customer-projects-team/370693 "2025-06-18T13:15:41Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![Danielle](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/danielle/32/537380_2.png) [@Danielle](https://meta.discourse.org/u/Danielle)
#### Post date: [June 18, 2025, 1:15pm UTC](https://meta.discourse.org/t/webinar-meet-the-discourse-customer-projects-team/370693/1 "2025-06-18T13:15:41Z")

</div>

On 2025-06-25T04:00:00Z, we hosted an AMA-style session with the incredible team behind custom design, development, and migration at Discourse.

This is the team that makes your Discourse instance look awesome, work brilliantly, and fit your needs.

[![](https://global.discourse-cdn.com/meta/original/4X/2/c/a/2cab1fd825845d30f7a1533f1d21dd32741fb21b.jpeg "Meet the Discourse Customer Projects Team") ](https://www.youtube.com/watch?v=xaEOGYwkWvU)

### Panelists

- **Jamie** – Director of Customer Projects
- **Dave** – Director of Product
- **Coco** – Migrations Team Lead
- **Jeff** – Engineering Manager
- **Mark** – Engineering Manager
- **Gabriel** – Software Engineer
- **Derek** – Customer Projects Designer
- **Danielle (Host)** – Customer Success Manager

### What Does the Customer Projects Team Do?

Our dedicated team supports Enterprise customers with:

- Custom themes and component design
- Plugin and API development
- Complex platform migrations
- Ongoing support and optimization

> It’s not just customizing Discourse—it’s about building the _community you imagined_, integrating with your systems, and making it seamless.  
> @mcwumbly, Director of Product

[Enterprise Services](https://www.discourse.org/enterprise-services)

### Migrate with Confidence

Whether you’re moving from a forum, a chat tool, or even a CSV file, our team handles data migration start to finish.

When we say _any_ platform, we mean it—even Slack, Rocket.Chat, or plain text files.

> We work closely with each customer to guide them through the migration process and make it as easy as possible. We take care of everything.  
> @cocococosti, Migrations Team Lead

One standout? A Slack migration where we used **AI to generate topic titles** from conversations to keep content readable and organized.

Learn more about this complex migration in the replay!

[Explore Migration Options](https://www.discourse.org/migrations)

### Highlights & Takeaways

> Every new request is a chance to evaluate: should this become a core feature, a plugin, or remain custom-built?  
> @featheredtoast, Engineering Team Lead

> Enterprise customizations don’t just serve one customer—they often uncover ways to improve Discourse for everyone. Simulating 1.3 billion pageviews helped us catch edge-case performance issues—benefiting all Discourse users.  
> @jamie.wilson, Director of Customer Projects

Some of our most useful features start as one-off customer requests. The livestream plugin, for example, began as a bespoke project—then evolved through multiple iterations to become a full-featured, open-source tool now available to everyone.

> We got to the point where a plugin, which was initially for one person, has become generally useful.  
> @jamie.wilson

Built by Gabriel, a member of Mark’s team, the discourse-custom-topic-lists plugin was created for a customer who needed a filtered topic list tailored by category and tags. While still in its early stages, it’s a great example of how internal teams collaborate to build scalable, open-source-ready tools.

> It’s still experimental… but it was a really cool example of a customer wanting something, and us thinking—this could be something we open source.  
> @markvanlan

### Let’s Keep the Conversation Going

Got a project in mind? Curious if something is possible? We’d love to hear from you.

📩 Reach out anytime: [team@discourse.org](mailto:team@discourse.org)  
💬 Or talk to your CSM—we’re happy to coordinate!

> Even if it doesn’t lead to a project, we’re always happy to chat. Some of our best ideas started as casual conversations.

@jamie.wilson

### Resources Shared

- [Discourse Discover (Live Examples)](https://discover.discourse.com/)
- [Jobs at Discourse](https://www.discourse.org/jobs) _(Upcoming designer and engineering roles!)_
- [Webinar Replay: Getting Buy-In for Your Community](https://meta.discourse.org/t/webinar-getting-buy-in-for-your-community-office-hours/360736)

---

<div class="post-metadata">

### Author: ![Danielle](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/danielle/32/537380_2.png) [@Danielle](https://meta.discourse.org/u/Danielle)
#### Post date: [June 18, 2025, 1:16pm UTC](https://meta.discourse.org/t/webinar-meet-the-discourse-customer-projects-team/370693/2 "2025-06-18T13:16:19Z")

</div>



---

<div class="post-metadata">

### Author: ![MihirR](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mihirr/32/475158_2.png) [@MihirR](https://meta.discourse.org/u/MihirR)
#### Post date: [June 20, 2025, 6:07pm UTC](https://meta.discourse.org/t/webinar-meet-the-discourse-customer-projects-team/370693/4 "2025-06-20T18:07:18Z")

</div>

Yay, excited and registered :))

---

<div class="post-metadata">

### Author: ![satonotdead](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/satonotdead/32/447830_2.png) [@satonotdead](https://meta.discourse.org/u/satonotdead)
#### Post date: [June 21, 2025, 5:02am UTC](https://meta.discourse.org/t/webinar-meet-the-discourse-customer-projects-team/370693/5 "2025-06-21T05:02:32Z")

</div>

Hello, I would like to understand the rationale behind using Zoom for the meetings.

Additionally, will the sessions be recorded for those who opt not to use this application due to privacy and security concerns?

Thank you for your clarification.

---

<div class="post-metadata">

### Author: ![ondrej](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ondrej/32/198804_2.png) [@ondrej](https://meta.discourse.org/u/ondrej)
#### Post date: [June 21, 2025, 6:34am UTC](https://meta.discourse.org/t/webinar-meet-the-discourse-customer-projects-team/370693/6 "2025-06-21T06:34:03Z")

</div>

Hi satonotdead,

All webinars thus far have been recorded and then posted in the OP a few days later. 😉

---

<div class="post-metadata">

### Author: ![tobiaseigen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tobiaseigen/32/539204_2.png) [@tobiaseigen](https://meta.discourse.org/u/tobiaseigen)
#### Post date: [June 21, 2025, 7:03am UTC](https://meta.discourse.org/t/webinar-meet-the-discourse-customer-projects-team/370693/7 "2025-06-21T07:03:15Z")

</div>

Yup, what @ondrej said. Check out the #webinar tag to see how we’ve done this in the past.

---

<div class="post-metadata">

### Author: ![Danielle](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/danielle/32/537380_2.png) [@Danielle](https://meta.discourse.org/u/Danielle)
#### Post date: [July 7, 2025, 2:00pm UTC](https://meta.discourse.org/t/webinar-meet-the-discourse-customer-projects-team/370693/10 "2025-07-07T14:00:32Z")

</div>

Replay/recap posted above!
