How a franchise brand can run franchise development marketing in HubSpot, hand qualified candidates to FranConnect Sales, and bring the candidate pipeline, disclosure milestones, unit openings and location data back into HubSpot for local marketing and brand-level reporting.
FranConnect is a franchise management platform. Its Sales module runs the franchise development pipeline, Info Manager is the record of franchisees, owners and locations, and Opener manages each unit from signing to opening.
Documentation and credentials come only through the vendor, under a license, partner agreement or customer login.
Gated API. FranConnect enables API access for the brand's account, and the API reference requires a signed-in FranConnect account.
Based on the vendor's public documentation. Access terms are confirmed with the vendor and the client in discovery.
FranConnect keeps the franchise record and the disclosure process, and HubSpot runs the marketing that fills the pipeline and the reporting that shows what it produced.
Campaign Creators assessment
FranConnect offers REST APIs across Sales and Information Manager, with a technical reference at docs.franconnect.net for signed-in customers. That makes a direct FranConnect-to-HubSpot integration buildable: HubSpot captures and nurtures franchise candidates, qualified candidates become FranConnect leads, and lead status, disclosure milestones, opportunities and location data flow back to HubSpot. Two things set the pace: API access and the reference documentation are arranged through FranConnect for the brand's account, and the disclosure steps fall under the FTC Franchise Rule, so the brand's franchise counsel decides what HubSpot may automate.
Ratings are CC judgments from FranConnect's public help center and product pages. Endpoints, payloads and limits are confirmed in FranConnect's API reference during discovery.
A closed lead moves to Opener as an In Development location, and its contact, disclosure and real estate fields carry into Info Manager. HubSpot can follow one person from first ad click to grand opening.
Marketing works the candidate in HubSpot; the development team works the lead in FranConnect Sales. Each field needs one owner, and the handoff point is agreed before any sync runs.
FranConnect enables API access for the brand's account, and franchise counsel signs off what HubSpot may send and record around disclosure before the build starts.
Seven parts of FranConnect matter to HubSpot. Four carry the integration, one enriches it, one is a scope decision, and one stays inside FranConnect.
The franchise development pipeline: candidate profiles, lead status, owners, tasks, the Lead Heat Index and lead source reporting.
Opportunities for a new location or a transfer, tracked against the candidate.
FranConnect sends the Franchise Disclosure Document and tracks sent date, FDD status, delivery receipt, FDD receipt and download date.
The system of record for franchisees, owners, entities and locations, including In Development, Active, Terminated and Corporate Locations.
Unit sales and royalty reporting that can add performance context to each location in HubSpot.
FranConnect's Campaign Center and Workflows send email and SMS to leads, and HubSpot can too. Decide which system sends each message before any sync runs.
The FDD itself, Item 23 receipts, signatures and franchise agreements stay in FranConnect. HubSpot receives dates and statuses only.
A CC-built integration layer sits between the two systems. It creates FranConnect leads from qualified HubSpot candidates, reads changes back from Sales and Info Manager on a schedule, matches each record to the right HubSpot object, and writes in batches.
Lead status, disclosure, agreements and location records are kept in FranConnect. HubSpot mirrors what marketing and leadership act on.
Forms, ads, content and nurture live in HubSpot. Every FranConnect lead created by the integration carries its HubSpot source, so cost per signed unit is measurable.
The FTC Franchise Rule governs disclosure timing. Franchise counsel approves which milestone fields sync and which automations they may trigger.
Each phase ends on a gate the client signs off before the next begins, so the fixed scope holds even when the API reference differs from what the public help center shows.
Confirm the FranConnect modules the brand licenses, request REST API access and the API reference through FranConnect, and get test credentials in a non-production environment if one is available.
Agree the point where a HubSpot candidate becomes a FranConnect lead, which system owns each field, which system sends each message, and how lead source maps across.
Walk franchise counsel through the disclosure fields and every automation that could touch a candidate after the FDD is sent. Record what HubSpot may store and trigger.
Create the Location custom object, franchise development pipeline, candidate and owner properties, association labels and property groups in a HubSpot sandbox.
Build the lead handoff, the scheduled change reader for Sales and Info Manager, identity matching, the disclosure guard, idempotent writes and an error replay queue.
Load current leads, opportunities and all locations, plus an agreed history window, then compute rollups once so reports start complete.
Build nurture, opening and owner-communication workflows with sends paused, run two weeks in parallel, then switch on.
FranConnect field names below follow the labels in its help center. Exact API field names come from FranConnect's API reference and are confirmed in discovery.
| FranConnect field | HubSpot property | Object | Direction | Notes |
|---|---|---|---|---|
| Sales · franchise candidates | ||||
| Lead ID | fc_lead_id | Contact | FC → HS | Primary key once the lead exists. Unique. Confirm field name in discovery. |
| First Name, Last Name | firstname, lastname | Contact | ↔ Both | HubSpot fills the new lead; FranConnect edits flow back. |
| Contact | ↔ Both | Match key before a FranConnect lead ID exists. | ||
| Mobile, Work Phone | mobilephone, phone | Contact | ↔ Both | Normalize to E.164. |
| Lead source | fc_lead_source | Contact | HS → FC | Set from HubSpot original source and campaign. |
| Lead status | fc_lead_status | Contact | FC → HS | Drives HubSpot lists and lifecycle stage. |
| Lead owner | hubspot_owner_id | Contact | FC → HS | Matched on development rep email. |
| Preferred market or territory | fc_preferred_market | Contact | ↔ Both | Plain field; confirm name in discovery. |
| Lead Heat Index | fc_heat_index | Contact | FC → HS | FranConnect engagement score, if exposed by the API. |
| Sales · opportunities & disclosure | ||||
| Franchise opportunity | Deal (development pipeline) | Deal | FC → HS | One deal per opportunity; new location or transfer. |
| Opportunity stage | dealstage | Deal | FC → HS | Stage mapping agreed in discovery. |
| FDD Sent Date | fc_fdd_sent_date | Contact | FC → HS | Date only. Counsel approves use in workflows. |
| FDD Status | fc_fdd_status | Contact | FC → HS | Status as FranConnect reports it. |
| Date FDD Received by Franchisee | fc_fdd_receipt_date | Contact | FC → HS | From the FDD receipt. No document stored. |
| Franchise Committee Approval | fc_committee_approval | Deal | FC → HS | Approval date or flag. |
| Info Manager & Opener · locations | ||||
| Location / center | Location | Custom object | FC → HS | One record per unit. FranConnect location ID is the key. |
| Location status | fc_location_status | Location | FC → HS | In Development, Active, Terminated, Corporate. |
| Site Street1, Site City, State / Province | address fields | Location | FC → HS | From the Real Estate tab. |
| Projected Opening Date | fc_projected_opening | Location | FC → HS | Drives pre-opening marketing. |
| Grand Opening Date | fc_grand_opening | Location | FC → HS | Triggers grand-opening workflows. |
| Region / territory | fc_region | Location | FC → HS | From Info Manager Regional. |
| Owner (Owner First Name, Owner Last Name) | Contact | Contact | FC → HS | Associated to the Location with an Owner label. |
| Entity | Company | Company | FC → HS | Franchisee entity; multi-unit owners roll up here. |
| Brand-level reporting · optional | ||||
| Unit sales (reported) | fc_unit_sales_ttm | Location | FC → HS | Rollup only. Off by default. |
| Royalty status | fc_royalty_status | Location | FC → HS | Current or past due. Confirm API coverage. |
| Transfer / previous ownership | fc_ownership_changes | Location | FC → HS | Ownership history count and latest date. |
FranConnect provides API access to the brand's account on request. Values FranConnect does not publish are marked for confirmation.
| Topic | FranConnect | HubSpot |
|---|---|---|
| Access model | Enabled for the brand's FranConnect account through FranConnect. The API reference at docs.franconnect.net requires a signed-in account. | Self-serve in the client portal. Custom objects need an Enterprise hub. |
| Interfaces | REST APIs across Sales and Information Manager, including lead, location, ownership and document endpoints. Confirm the full endpoint list in the reference. | REST APIs: CRM objects, associations, pipelines, custom objects. |
| Authentication | Token-based credentials issued by FranConnect for the account. Confirm the method and token lifetime in discovery. | Private app access token or OAuth 2.0 public app, scoped per object. |
| Change detection | Webhooks are offered for selected features by request. The core sync reads changed records on a schedule. Confirm available filters in discovery. | Writes are immediate; batch endpoints handle volume. |
| Rate limits | Not published. Confirm with FranConnect. | Per-10-second burst and daily limits by subscription tier. |
| Bulk load | Import and export wizards handle 5,000 lines per operation; support can raise the limit. Useful for backfill alongside the API. | CRM imports and batch APIs for large loads. |
| Sensitive data | Candidate financial qualification, disclosure records and agreements. Only approved fields leave FranConnect. | Sensitive data properties on Enterprise; field-level permissions by team. |
Severity reflects impact on the SOW, not technical difficulty alone.
The FTC Franchise Rule sets when the FDD must be delivered before a candidate signs or pays. Franchise counsel decides which disclosure fields sync and which HubSpot automations may run after disclosure.
FranConnect's Campaign Center and Workflows and HubSpot can both send. Without a sender-of-record decision, candidates get duplicate or mistimed messages.
The API reference is available to signed-in customers, not publicly. Budget a short discovery spike to confirm endpoints, payloads and change filters.
Webhooks cover selected features only. The core sync reads changes on a schedule, so lead status reaches HubSpot within an agreed interval, not instantly.
A candidate can arrive from a portal, a broker and a HubSpot form. Match on email first, then FranConnect lead ID, and let the development team merge in FranConnect.
Unit sales and royalty status are sensitive between franchisor and franchisee. Keep them off by default and restrict viewing with HubSpot field-level permissions.
HubSpot campaign and ad data meet FranConnect status and opportunity outcomes, so the brand sees which channels produce signed franchisees, not just leads.
HubSpot nurture pauses or changes as soon as a lead's FranConnect status moves, so candidates hear the right thing at each step.
Projected and grand opening dates trigger local campaigns, landing pages and owner checklists in HubSpot for every new unit.
Every unit is a HubSpot record with its region, status and owner, so local campaigns, lists and reports run per location.
Owners are HubSpot contacts associated to their locations, so brand updates and launches reach the right people by region and status.
Development pipeline, unit openings and optional performance rollups sit in one HubSpot dashboard for leadership.
The integration follows one person through franchise development and one unit through opening. Each system does the part it is built for, and the handoff points are agreed up front.
All custom properties use the fc_ prefix in a FranConnect property group. FranConnect values are written as FranConnect reports them; HubSpot does not recalculate them.
| Internal name | Label | Object | Type | Source / logic |
|---|---|---|---|---|
| fc_lead_id | FranConnect Lead ID | Contact | Single-line text | Sales lead key; unique |
| fc_lead_status | FranConnect Lead Status | Contact | Dropdown | Lead status in Sales |
| fc_lead_source | FranConnect Lead Source | Contact | Dropdown | Set from HubSpot original source |
| fc_preferred_market | Preferred Market | Contact | Single-line text | Candidate's target market or territory |
| fc_heat_index | Lead Heat Index | Contact | Number | FranConnect engagement score, if available |
| fc_fdd_sent_date | FDD Sent Date | Contact | Date | FDD Sent Date; counsel-approved |
| fc_fdd_receipt_date | FDD Receipt Date | Contact | Date | Date FDD Received by Franchisee |
| fc_location_id | FranConnect Location ID | Location | Single-line text | Info Manager location key; unique |
| fc_location_status | Location Status | Location | Dropdown | In Development, Active, Terminated, Corporate |
| fc_projected_opening | Projected Opening Date | Location | Date | Real Estate tab |
| fc_grand_opening | Grand Opening Date | Location | Date | Lease Renewal Details |
| fc_region | Region | Location | Dropdown | Info Manager Regional |
Choose the FranConnect modules and fields for this engagement and the direction each one syncs. Required fields are the keys the integration cannot run without. Copy the summary into the SOW or a reply to the client.
Based on public documentation. FranConnect's API reference is available to signed-in customers, so endpoints, payloads and limits are confirmed with FranConnect during discovery.
Yes, but access is gated: FranConnect enables REST API access for the brand's account and its API reference requires a signed-in FranConnect login. Campaign Creators builds a custom integration layer on FranConnect's Sales and Information Manager APIs once that access is granted.
Franchise candidates, lead status, development opportunities and disclosure milestone dates sync from FranConnect Sales into HubSpot contacts and a development-pipeline deal. Franchisees, owners, locations and unit-opening dates from Info Manager and Opener sync into HubSpot as a Location custom object. Qualified HubSpot candidates flow back to FranConnect as new leads; FDD documents, receipts and signatures never sync.
FranConnect owns the franchise record: lead status, disclosure milestones, agreements and location records are kept and worked there, with franchise counsel approving which disclosure fields may sync and which HubSpot automations may run after an FDD is sent. HubSpot owns demand, holding the forms, ads, content and nurture that fill the pipeline, with every FranConnect lead tagged by its HubSpot source.
Seven phases, each closed by a client sign-off: confirming the brand's licensed FranConnect modules and requesting API access, agreeing the handoff point and field-ownership rules between the two systems, a franchise-counsel review of every disclosure field and automation, the HubSpot data model with a Location custom object, a sandboxed build of the lead handoff and change reader, a backfill of current leads and locations, and a two-week parallel run before nurture and grand-opening workflows go live.
Timeline and cost depend on how many FranConnect modules are licensed, how many locations are in scope, and how long franchise counsel's disclosure review takes. Campaign Creators confirms these in discovery and provides a fixed scope before the build starts.