How long does a Selligent by Marigold to HubSpot migration take?

Most Selligent-to-HubSpot migrations complete in 3–7 days of clock time for under 100,000 profiles with standard custom field counts. Larger datasets exceeding 500,000 profiles or datasets with complex behavioral event history extend to 10–21 days. The API export phase from Selligent is typically the longest single step due to batch-rate limits; we sequence exports in advance to avoid surprises.

Will my Selligent campaigns, journeys, and automation rules migrate to HubSpot?

No. Selligent campaigns, Journey Builder flows, and automation rules are marketing automation logic that does not transfer to HubSpot CRM. They must be rebuilt in HubSpot's Workflows tool or within Marketing Hub campaigns. FlitStack AI exports your journey definitions and campaign metadata as a human-readable rebuild reference document that your HubSpot admin can use to reconstruct the logic in HubSpot Workflows.

What happens to Selligent behavioral data like opens, clicks, and engagement scores in HubSpot?

Selligent stores per-contact behavioral events as discrete records. In HubSpot, we aggregate key metrics — total opens, total clicks, last engagement date, and engagement score — as custom contact properties. Full event-level history is preserved as a structured reference file attached to the contact record. Your team decides whether to backfill HubSpot activity records from the reference export using HubSpot's API or workflow tools.

Can I migrate Selligent custom profile fields to HubSpot custom properties?

Yes. Selligent custom profile fields migrate to HubSpot custom contact properties. We create each property in HubSpot matching the source field's data type — text, number, date, or pick-list. HubSpot plan tiers impose a property count limit; if your Selligent instance has more custom fields than your HubSpot plan allows, we identify consolidation options during the scoping phase before migration begins.

How does Selligent's organization and company data map to HubSpot?

Selligent has no dedicated Account or Company object — organizations are stored as contact profile properties or inferred from email domain. We create HubSpot Companies from domain extraction or explicit org_name fields and link them to the corresponding contacts. For Selligent records without an explicit organization, we create a default HubSpot Company or attach the contact without a primary company association per your configuration preference.

Does the migration affect my Selligent account during cutover?

No. FlitStack AI uses scoped read access on Selligent via the REST API — your team continues working in Selligent during the migration. A delta-pickup window of 24–48 hours captures any contacts created or modified during the cutover period, so HubSpot reflects Selligent's final state at go-live. No writes are made to Selligent during this window.

What happens to my Selligent static lists and dynamic segments?

Selligent static lists migrate as HubSpot static lists — list names and contact memberships transfer via email address matching. Dynamic segments with rule-based membership logic have no direct HubSpot equivalent. We export the segment definitions as a rebuild reference. Your HubSpot admin recreates dynamic logic using HubSpot list filters and smart lists. List rebuild is a planning item included in the migration engagement scope.

Selligent by Marigold to HubSpot Migration — Field-Level Mapping & Rollback

Overview

What this migration involves

Selligent by Marigold stores contacts as profiles with standard fields (name, email, phone, address) plus unlimited custom fields, behavioral tracking events, campaign membership, and journey/automation rules. It has no native Company or Account object — organizations are profile properties or inferred from email domain. HubSpot's CRM model is built around Contacts, Companies, Deals, and Activities. FlitStack AI maps every Selligent profile to a HubSpot Contact, every Selligent organization reference to a HubSpot Company (created from domain where no explicit org exists), and every custom profile field to a HubSpot custom contact property. Behavioral metrics (opens, clicks, engagement scores) land as numeric custom properties on the contact. Selligent campaign and journey names migrate as reference tags preserved on the contact record, not as live HubSpot Sequences or workflows. Marketing lists migrate as HubSpot static lists; dynamic segment logic requires manual rebuild as HubSpot list filters. We extract via the Selligent REST API and bulk-import into HubSpot via HubSpot's Contacts API and CRM Imports API, respecting both platforms' rate limits. The result is a clean HubSpot CRM with full contact history intact — ready for sales, service, and marketing ops on day one.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Selligent by Marigold

What's pushing teams away

Enterprise pricing with non-refundable, non-cancelable contract terms creates sticker shock when teams need to downsize or pivot to a lower-cost platform.
Recent acquisition by Zeta Global in 2025 introduces uncertainty about product roadmap, support continuity, and long-term pricing for existing customers.
Platform complexity requires significant onboarding investment; smaller marketing teams report difficulty achieving full utilization without dedicated technical support.
Journey and campaign configuration is deep but not easily transferable, making migrations feel like rewrites rather than data moves and increasing switching costs.
API documentation and partner ecosystem are less extensive than dominant US-based platforms, leading to frustration when custom integrations are needed.

Choosing

HubSpot

What's pulling them in

Lowest barrier to entry of any major CRM — the free tier with unlimited contacts lets teams validate fit before committing to a paid plan, according to G2 and Capterra reviewers.
Native integration between the CRM and sales engagement tools (sequences, email tracking, dialer) means no separate sync configuration, a theme across G2 Sales Hub reviews.
Pipeline visualization, deal tracking, and automated workflows are consistently praised as intuitive and easy to set up without developer involvement.
Strong onboarding for new team members — reviewers on Capterra and G2 highlight how quickly new reps become productive without formal training.
The HubSpot platform ecosystem (Marketing, Sales, Service, CMS hubs) allows growing companies to consolidate tools without building new integrations.

Object mapping

How Selligent by Marigold objects map to HubSpot

Each row shows how a Selligent by Marigold object lands in HubSpot, including any object-level transformations, lookup resolution, or schema-design dependencies.

Typical mapping — final map is confirmed during the sample migration step.

Selligent by Marigold

Contact Profile

maps to

HubSpot

Contact

1:1

Fully supported

Selligent contact profiles map 1:1 to HubSpot Contacts. Every profile property becomes a HubSpot contact property. The Selligent profile ID is stored as Source_System_ID__c for traceability and delta-run de-duplication.

Selligent by Marigold

Organization / Company Data

maps to

HubSpot

Company

1:1

Fully supported

Selligent has no dedicated Company or Account object. Organizations are stored as profile properties or inferred from email domain. We create HubSpot Companies from domain extraction or explicit org_name fields and link them to contacts via the primary company association.

Selligent by Marigold

Standard Profile Fields (firstname, lastname, email, phone)

maps to

HubSpot

Contact Standard Properties

1:1

Fully supported

Selligent's standard profile fields map directly to HubSpot's built-in contact properties: firstname → First Name, lastname → Last Name, email → Email, phone → Phone Number. These require no custom property creation.

Selligent by Marigold

Custom Profile Fields

maps to

HubSpot

Contact Custom Properties

1:1

Fully supported

Every Selligent custom profile field maps to a HubSpot custom contact property. We create the property in HubSpot before migration, matching the source field's data type (text, number, date, picklist). Field labels are preserved for audit continuity.

Selligent by Marigold

Behavioral Event History (opens, clicks, page views)

maps to

HubSpot

Contact Custom Properties

1:1

Fully supported

Selligent stores per-contact behavioral events. We aggregate key metrics (total opens, total clicks, last engagement date) and write them as numeric or date custom properties on the HubSpot Contact. Full event-level history is preserved as a reference note attachment.

Selligent by Marigold

Campaign Membership

maps to

HubSpot

Contact Custom Properties + Tags

1:1

Fully supported

Campaign names from Selligent migrate as contact property values or tags on the HubSpot Contact record. This preserves which campaigns each contact was in but does not recreate campaign configuration.

Selligent by Marigold

Static Lists

maps to

HubSpot

HubSpot Static Lists

1:1

Fully supported

Selligent static lists map directly to HubSpot static lists. We export the list membership, create matching HubSpot lists, and associate contacts by email address match. List names are preserved verbatim.

Selligent by Marigold

Dynamic Segments

maps to

HubSpot

HubSpot Dynamic Lists (rebuild required)

1:1

Mapping required

Selligent dynamic segments with rule-based membership logic have no HubSpot equivalent at the data level. We export the segment definitions as a reference document for your HubSpot admin to recreate using HubSpot list filters and smart lists.

Selligent by Marigold

Journeys and Automation Rules

maps to

HubSpot

Not Migrated

1:1

Fully supported

Selligent journeys and automation rules are marketing automation logic with no HubSpot CRM equivalent. They cannot migrate. FlitStack AI exports the journey definitions as a human-readable rebuild reference, and your team rebuilds them in HubSpot Workflows.

Selligent by Marigold

Selligent User / Owner Data

maps to

HubSpot

Contact Custom Properties

1:1

Fully supported

If your Selligent instance tracks sales owners or campaign managers as profile fields, we migrate those as HubSpot contact properties. HubSpot native Owner assignment requires a matching HubSpot user email.

Selligent by Marigold

Profile Timestamps

maps to

HubSpot

Contact Custom Properties

1:1

Fully supported

Selligent profile create and update timestamps do not map to HubSpot system timestamps. We preserve them as Original_Create_Date__c and Original_Update_Date__c custom date fields for reporting continuity.

Selligent by Marigold	HubSpot	Compatibility
Contact Profile	Contact1:1	Fully supported
Organization / Company Data	Company1:1	Fully supported
Standard Profile Fields (firstname, lastname, email, phone)	Contact Standard Properties1:1	Fully supported
Custom Profile Fields	Contact Custom Properties1:1	Fully supported
Behavioral Event History (opens, clicks, page views)	Contact Custom Properties1:1	Fully supported
Campaign Membership	Contact Custom Properties + Tags1:1	Fully supported
Static Lists	HubSpot Static Lists1:1	Fully supported
Dynamic Segments	HubSpot Dynamic Lists (rebuild required)1:1	Mapping required
Journeys and Automation Rules	Not Migrated1:1	Fully supported
Selligent User / Owner Data	Contact Custom Properties1:1	Fully supported
Profile Timestamps	Contact Custom Properties1:1	Fully supported

Gotchas + challenges

What specifically takes care here

Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.

Selligent by Marigold gotchas

Medium

API rate limits are documented but not fully quantified publicly

High

Enterprise contracts are non-cancelable with no refunds mid-term

High

Journeys and campaign templates are not API-exportable

Medium

SDC bulk message limit of 100 per request caps throughput

Medium

Custom field schema must be pre-created at destination before import

HubSpot gotchas

High

Marketing Contacts billing model is migration-critical

High

Feature tier gating is not visible until onboarding

Medium

Mandatory onboarding fees inflate year-one cost

Medium

HubSpot CSV importer cannot migrate engagements or attachments

Medium

Custom objects require Enterprise and a pre-existing schema

Selligent by Marigold gotchas		HubSpot gotchas
Severity	Issue	Severity	Issue
Medium	API rate limits are documented but not fully quantified publicly	High	Marketing Contacts billing model is migration-critical
High	Enterprise contracts are non-cancelable with no refunds mid-term	High	Feature tier gating is not visible until onboarding
High	Journeys and campaign templates are not API-exportable	Medium	Mandatory onboarding fees inflate year-one cost
Medium	SDC bulk message limit of 100 per request caps throughput	Medium	HubSpot CSV importer cannot migrate engagements or attachments
Medium	Custom field schema must be pre-created at destination before import	Medium	Custom objects require Enterprise and a pre-existing schema

Pair-specific challenges

Selligent campaigns and journeys have no HubSpot CRM equivalent and cannot migrate

Selligent stores campaigns as multi-channel program definitions and journeys as multi-step automation flows with conditional branching, channel routing, and A/B logic. HubSpot CRM has no object that stores campaign program definitions or live journey state. We export your Selligent campaign names and journey names as contact property values and provide a journey-definition export as a rebuild reference. Your team will need to recreate active campaigns as HubSpot Workflows or Marketing Hub campaigns and rebuild journey logic in HubSpot's workflow builder. This is the most significant scope gap in any Selligent-to-HubSpot migration and must be accounted for in the project timeline.
Selligent API rate limits extend export windows and require batch sequencing

Selligent's REST API enforces a batch limit of 2500 requests per 10-minute window, and the Campaign API caps at 100 records per request with a 4MB JSON body limit. For Selligent databases exceeding 200,000 profiles, these limits mean the export phase may require multiple API sessions across 24–48 hours. We manage rate-limit headers from Selligent and implement exponential back-off to avoid throttling. The total export duration is scoped before migration begins and factored into the project timeline, so there are no surprises on cutover day.
HubSpot contact property count limits vary by plan tier and may require property management

HubSpot Sales Hub and Marketing Hub Starter plans limit the number of custom contact properties. If your Selligent instance uses more than 30 custom profile fields, some may exceed HubSpot's property count ceiling on lower tiers. We audit your Selligent custom fields during the planning phase and identify which properties can be mapped natively versus which require property consolidation or a HubSpot Enterprise upgrade. This discovery step prevents the scenario where a migration runs but properties are silently dropped at import time.
Selligent behavioral event history does not map directly into HubSpot's activity timeline

Selligent records every email open, click, page view, and form submission as a discrete behavioral event tied to a contact profile. HubSpot's activity timeline tracks calls, emails, meetings, and notes as Activity objects. A direct 1:1 mapping of hundreds of event rows per contact would create hundreds of thousands of HubSpot activity records and may hit import limits. We take a pragmatic approach: key engagement metrics (total opens, total clicks, last engagement date) are written as contact properties. Full event-level history is preserved as a structured CSV attachment on the contact record for reference. Your team decides whether to backfill HubSpot activity records from the reference export.
Selligent's post-Zeta Global acquisition may affect API access and support tier availability

Marigold's enterprise products, including Selligent, were acquired by Zeta Global in November 2025. This acquisition may introduce changes to API access policies, support tier definitions, and data export tooling. We monitor Selligent API endpoint availability and will coordinate with your Selligent account team if any API access changes are detected during the migration scoping phase. Early engagement with your Selligent account manager is recommended to confirm data export permissions are active before migration begins.

Migration approach

Six steps for a successful Selligent by Marigold to HubSpot data migration

Audit Selligent data model and export plan

FlitStack AI connects to your Selligent instance via the REST API and documents every active profile field, list, segment, and campaign tag. We identify standard fields, custom profile fields, and behavioral event types. We also confirm your Selligent API credentials have sufficient read permissions and assess your current plan tier's export limits. This produces a data inventory document that becomes the field mapping specification.
Design HubSpot property schema and create custom properties

Before any data moves, FlitStack AI creates all required HubSpot custom contact and company properties to match the Selligent data model. We create custom properties for engagement metrics, campaign membership, original timestamps, and any Selligent custom fields that lack a HubSpot native equivalent. We validate property creation against your HubSpot plan's property count limit and flag any consolidation needed.
Extract Selligent profiles, companies, and behavioral data in sequence

We export Selligent contact profiles in batches respecting the API's 2500-request window and Campaign API's 100-record-per-request limit. Organization data is extracted separately and deduplicated by domain. Behavioral event history is aggregated into per-contact summary metrics. Campaign membership tags are extracted as separate datasets. Each export run is checksummed to verify completeness before the next phase begins.
Resolve owner and user mapping by email

Selligent owner or campaign manager fields are resolved by email address match against existing HubSpot users. Unmatched owners are flagged with a pre-migration report — your team either invites them to HubSpot or assigns their records to a fallback HubSpot user before the import phase runs. No contact lands in HubSpot without a resolved owner or an explicit fallback assignment.
Run sample migration with field-level diff

A representative slice of 200–500 Selligent profiles migrates to HubSpot first, including contacts from multiple segments, contacts with custom fields, and contacts with behavioral data. We generate a field-level diff report comparing source values against HubSpot values for every mapped property. You review the diff, confirm property mapping accuracy, and sign off before the full migration commits. This step surfaces any value mapping issues or property creation gaps before they affect the full dataset.
Execute full migration with delta-pickup cutover

The full Selligent dataset migrates to HubSpot in sequenced batches via the HubSpot Contacts API and CRM Imports API. A delta-pickup window of 24–48 hours after the primary migration captures any Selligent records created or updated during the cutover. An audit log records every import operation. One-click rollback is available if post-migration reconciliation identifies missing records or property mapping errors.

Platform deep dives

Context on both ends of the pair

Selligent by Marigold

Source

Strengths

Email deliverability rates consistently praised in user reviews across retail and media verticals.
Native support for GDPR, CCPA, and CAN-SPAM compliance with documented sub-processor list.
Flexible custom field and data modeling accommodates complex B2C schemas without schema locks.
Multichannel journey orchestration across email, SMS, push, and web personalization in one platform.
AI-powered audience selection and send-time optimization built into the core platform.

Weaknesses

Public API documentation lacks comprehensive rate-limit tables and bulk export endpoints.
Journey builder configurations are not exportable via API, making migrations require full manual rebuilds.
Non-refundable contract terms mean customers pay for the full order term regardless of early termination.
Platform complexity creates a steep learning curve compared to simpler email-focused tools.
Ownership transition to Zeta Global introduces uncertainty for existing Marigold/Selligent customers.

HubSpot

Destination

Strengths

Genuinely useful free CRM tier with no seat limit on contact records.
All-in-one sales engagement layer (sequences, email tracking, calling, dialer) embedded natively in the CRM, eliminating a separate integration.
Intuitive interface and fast onboarding for individual reps, per G2 and Capterra reviews.
Workflow automation triggers across contacts, deals, and tickets with a visual builder.
API coverage for all standard objects including custom objects at Enterprise tier.

Weaknesses

Pricing model is contact-based at the marketing layer — importing all records as marketing contacts can multiply the monthly bill by 4×.
Feature tier cliffs are frequent surprises: sequences, calling, advanced reporting, and quoting are all gated, often requiring plan upgrades mid-implementation.
Mandatory onboarding fees at Professional ($1,500) and Enterprise ($3,500) are not prominently disclosed on the pricing page.
API rate limits are restrictive for bulk migration — burst limits of 100-200 req/10sec and search endpoint limits of 4 req/sec require careful job queuing.
Custom objects, additional pipelines, and advanced forecasting are Enterprise-only, making cost projections difficult for growing teams.

	Selligent by Marigold Source	HubSpot Destination
Strengths	Email deliverability rates consistently praised in user reviews across retail and media verticals. Native support for GDPR, CCPA, and CAN-SPAM compliance with documented sub-processor list. Flexible custom field and data modeling accommodates complex B2C schemas without schema locks. Multichannel journey orchestration across email, SMS, push, and web personalization in one platform. AI-powered audience selection and send-time optimization built into the core platform.	Genuinely useful free CRM tier with no seat limit on contact records. All-in-one sales engagement layer (sequences, email tracking, calling, dialer) embedded natively in the CRM, eliminating a separate integration. Intuitive interface and fast onboarding for individual reps, per G2 and Capterra reviews. Workflow automation triggers across contacts, deals, and tickets with a visual builder. API coverage for all standard objects including custom objects at Enterprise tier.
Weaknesses	Public API documentation lacks comprehensive rate-limit tables and bulk export endpoints. Journey builder configurations are not exportable via API, making migrations require full manual rebuilds. Non-refundable contract terms mean customers pay for the full order term regardless of early termination. Platform complexity creates a steep learning curve compared to simpler email-focused tools. Ownership transition to Zeta Global introduces uncertainty for existing Marigold/Selligent customers.	Pricing model is contact-based at the marketing layer — importing all records as marketing contacts can multiply the monthly bill by 4×. Feature tier cliffs are frequent surprises: sequences, calling, advanced reporting, and quoting are all gated, often requiring plan upgrades mid-implementation. Mandatory onboarding fees at Professional ($1,500) and Enterprise ($3,500) are not prominently disclosed on the pricing page. API rate limits are restrictive for bulk migration — burst limits of 100-200 req/10sec and search endpoint limits of 4 req/sec require careful job queuing. Custom objects, additional pipelines, and advanced forecasting are Enterprise-only, making cost projections difficult for growing teams.

Complexity grading

How hard is this migration?

Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Selligent by Marigold and HubSpot.

Object compatibility
B
1 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
C
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
B
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
B
Selligent by Marigold: Not publicly quantified; connector documentation shows batched behavior at 2500 requests or 10-minute windows.
Data volume sensitivity
A
Selligent by Marigold exposes a bulk API — large-volume migrations stream efficiently.

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

Migrate from Selligent by Marigold to HubSpot

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

Selligent by Marigold

HubSpot

How Selligent by Marigold objects map to HubSpot

What specifically takes care here

Six steps for a successful Selligent by Marigold to HubSpot data migration

Context on both ends of the pair

How hard is this migration?

Estimate your Selligent by Marigold to HubSpot migration cost

What are you migrating?

Frequently asked questions about Selligent by Marigold to HubSpot data migrations

Can't find your answer?

Related migrations to explore

Move from Selligent by Marigold.
Land in HubSpot, intact.

Migrate from Selligent by Marigold to HubSpot

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

Selligent by Marigold

HubSpot

How Selligent by Marigold objects map to HubSpot

What specifically takes care here

Six steps for a successful Selligent by Marigold to HubSpot data migration

Context on both ends of the pair

How hard is this migration?

Estimate your Selligent by Marigold to HubSpot migration cost

Frequently asked questions about Selligent by Marigold to HubSpot data migrations

Can't find your answer?

How long does a Selligent by Marigold to HubSpot migration take?

Will my Selligent campaigns, journeys, and automation rules migrate to HubSpot?

What happens to Selligent behavioral data like opens, clicks, and engagement scores in HubSpot?

Can I migrate Selligent custom profile fields to HubSpot custom properties?

How does Selligent's organization and company data map to HubSpot?

Does the migration affect my Selligent account during cutover?

What happens to my Selligent static lists and dynamic segments?

Related migrations to explore

Move from Selligent by Marigold. Land in HubSpot, intact.

Move from Selligent by Marigold.
Land in HubSpot, intact.