# HubSpot themes and modules built to fit your business > We build your portal's theme, templates, and modules so your marketing team can publish pages and landing pages without opening code, and without any way to break the design. - Modules your marketing team can edit - No marketplace templates - Migration with every redirect mapped ## Everything your portal needs to run on its own Six pieces, from theme design to handover, built so that once we're done nobody has to call us for a text change. ### Custom themes We design and code the whole theme: typography, color palette, spacing, and global styles defined in one place. Changing your brand color means changing one value, not going through forty pages. ### Configurable modules Every block your team drags into the editor comes with its own fields: text, image, repeaters, style options. Your team sets it up from the panel, inside the limits we define, so an edit can't break the layout. ### Templates for each page type Home, service page, article, landing page, and thank-you page, each with its own structure and fields. Publishing a new landing page stops being a project and becomes a form. ### Landing and campaign pages We build the pages your campaigns run on, with HubSpot forms connected to the CRM and conversion events defined so attribution reaches the report complete. ### Migration from your current CMS We bring your site over from WordPress, Webflow, Wix, or whatever CMS you use, with the content migrated and the full map of 301 redirects. It's the step that gets skipped most often and the one that costs the most organic traffic. ### Training and documented handover At handover your team gets a session on its own modules and the documentation of what each field does. A theme nobody knows how to use ends up being a theme that gets edited by asking for help. ## The difference is in who can edit what You can tell a well-built HubSpot portal by one sign: marketing doesn't need a developer in order to publish. These three decisions are what get you there. ### Modules with fields, not blocks of code A badly built module forces someone to edit HTML inside the HubSpot editor, and from there it's a matter of time before somebody deletes a tag and the page breaks. We expose every editable part as a field with its own type: text, image, link, repeater, or list of options. What shouldn't change doesn't show up as a field. - The repeater lets your team add cards, logos, or testimonials without touching the structure. - Style options are a closed list, so the site never ends up with fifteen different blues. - Every field has help text, so whoever edits knows what they're changing before they save it. ### Your own theme instead of a marketplace template Marketplace templates make the start easy and charge for it later: they bring dozens of modules you don't use, styles you have to override, and a structure that isn't your business. Your own theme contains only what your site uses, and it looks like your brand from the first day. - Global styles live in the theme, so a brand change isn't made page by page. - We build only the modules your operation needs, and we document each one. - The code is yours: it stays in your portal and doesn't depend on a vendor renewing a license. ### Migrating without losing the rankings you already have When you change CMS, every URL changes, and without a redirect map the new site starts without the authority the old one took years to build. Before publishing we take the full inventory of URLs, cross it against the ones that actually bring traffic, and leave each one redirected to its equivalent. - The inventory comes from your sitemap, from Search Console, and from a crawl of the current site, not from a list written by hand. - We test the redirects before launch, not the day after, once the drop has already shown up. - Metadata, canonical tags, and structured data move with the content. We don't rebuild them from scratch. ## Portals edited by the teams that own them They're built inside the HubSpot CMS and they're live. You can open any of them and see for yourself. - **SeguriData** (Invoicing and tax compliance): seguridata.com - **JB Soluciones** (Invoicing and tax compliance): jbsoluciones.com ## Pick the scope that fits your situation Three ways to start, depending on what you already have in the portal. We close the proposal after we've seen your HubSpot from the inside. ### Modules *For teams that have a theme and are missing pieces* We build the modules your team needs and doesn't have: a case study section, a comparison table, a pricing block, or the form that doesn't fit the standard ones. They plug into the theme you already use and follow its styles, so nothing has to be redone. It's the shortest of the three and the one you notice fastest, because it unlocks pages you can't put together today. ### Full theme *For rebuilding the site inside HubSpot* The entire theme, made to measure: global styles, templates for each page type, and the full set of modules your team uses to assemble any new page. It includes setting up forms and CTAs connected to the CRM, and the training session run in your own portal. It's the scope for teams that want to stop asking for help to publish. ### Migration and theme *For bringing your site over from another CMS* Everything in the full theme plus the move: URL inventory, migration of the content and its metadata, a 301 redirect map tested before publishing, and verification in Search Console afterward. There are more moving parts here than in the other two, and more to lose if something goes wrong, so we plan the launch with a date and a way back. ## From design to portal, with reviews along the way Four stages. Each one ends in something you can open and review before we build the next one. ### Inventory and design · 1–2 weeks We go through your portal and your current site: which templates are needed, which modules repeat, and which pages have traffic worth keeping. We design the templates and define, module by module, which field is going to be editable. ### Theme build · 3–6 weeks We code the theme and the modules in a sandbox of your portal, with real content and not filler. You see the templates as they come out, so a change of structure gets asked for while it's still cheap. ### Content and migration · 2–4 weeks We load the pages, migrate the content if it comes from another CMS, and build the redirect map. This is where we connect the forms to the CRM and define what counts as a conversion. ### Launch and training · 1 week We publish with the redirects live, check crawling in Search Console, and train your team on its own modules. We hand over the documentation of what each field does. ## Frequently asked questions about HubSpot development ### How is this different from your Websites service? It comes down to where the site lives. The Websites service builds with our own code, outside HubSpot, for companies that want full control of the stack and the most room for performance. This service builds inside the HubSpot CMS, for companies that already have the portal and want their marketing team to publish and edit without depending on anyone. If you're not sure which one suits you, we settle it on the first call: the answer almost always depends on who is going to maintain the site. ### Do I need a Content Hub license? To publish the pages of the site on your own domain, yes: you need Content Hub, which is the current name of what used to be called CMS Hub. You can create landing pages from Marketing Hub, with less control over templates and modules, but the exact scope depends on the plan and HubSpot has moved it more than once. As a HubSpot partner, we review your portal and tell you what your case needs before you buy more than you have to. ### Can I edit the pages myself afterward? That's exactly the point. Every module ships with its fields editable from the HubSpot editor and with help text that explains what each one changes. What shouldn't be modified—the structure, the layout, the type scale—never appears as a field, so you can edit without fear of breaking the page. ### Why not use a marketplace template? Because it makes the start easy and charges for it later. A generic template brings dozens of modules you won't use, styles you have to override, and a structure designed for another business, so every adjustment fights decisions somebody else made. On top of that, performance carries everything the template loads, even what you never use. ### What happens to URLs and rankings when we migrate? Before publishing we take the full inventory of URLs from your sitemap, Search Console, and a crawl of the current site, and leave each one redirected with a 301 to its equivalent. We test the redirects before launch and verify them afterward in Search Console. Skipping this step is the most common reason a new site loses organic traffic for months. ### How long does the project take? A set of standalone modules usually takes 2 to 4 weeks. A full theme, between 6 and 10 weeks depending on how many templates are needed. A migration from another CMS adds another 2 to 4 weeks, depending on the volume of content and how orderly it is. What stretches the timeline most is almost always content delivery and internal approvals. ## Show us your portal and we'll tell you what it's missing In a 30-minute call we go through your HubSpot and come out with the list of what to build first so your team publishes without help. --- Source: https://c2suite.com/en/services/hubspot-development You can cite and summarize this content if you credit C2Suite and link to the source URL.