Migrate from Paradym to HubSpot

Paradigm contact records map 1:1 to HubSpot contact records. All standard fields (name, email, phone, job title, address) transfer directly without transformation. The Paradigm lifecycle or status field maps to HubSpot's lifecycle_stage custom property — see field_mapping for value-level notes on pick-list translation between Paradigm status values and HubSpot lifecycle stages.

If Paradigm stores both active customers and pre-conversion leads in the same contact object using a status field, FlitStack splits records based on that status value: 'customer' or equivalent values land as HubSpot Contacts; 'lead', 'prospect', or equivalent values land as HubSpot Leads. The split rule is configurable before migration commits.

Paradigm company or account records map to HubSpot company records via direct field transfer. Company name, domain/website, industry, employee count, and annual revenue move without transformation. Parent-child company hierarchies in Paradigm map to HubSpot's parent company association using the HubSpot parent_company_id field, which requires the parent company to exist in HubSpot before child records insert.

Paradigm deal or opportunity records map to HubSpot deal records. Deal name, amount, close date, and owner transfer directly. Pipeline and stage mapping requires value-by-value correspondence — see field_mapping for stage name mapping notes. Paradigm deal associations to contacts transfer as HubSpot deal-to-contact associations.

Each Paradigm deal pipeline maps to a HubSpot deal pipeline. HubSpot allows multiple concurrent pipelines with independent stage sets. FlitStack creates the destination pipelines in HubSpot before importing deals so stage values resolve at insert time rather than requiring post-migration remediation.

Stage names map value-by-value per pipeline. Probability percentages attached to stages in Paradigm are preserved as HubSpot stage probability values. Forecast category (Open, Won, Lost) is set per stage during pipeline setup. HubSpot's Salesforce-native model uses forecast_category on Opportunities; HubSpot-native deals use stage probability for forecasting by default.

Paradigm call logs transfer as HubSpot engagement calls with original timestamp, duration, outcome, and owner attribution preserved through the HubSpot API. Call recordings stored in Paradigm are re-uploaded to HubSpot Files and linked to the engagement record where supported by Paradigm's export format, ensuring conversation context remains accessible in the destination CRM.

Paradigm email activity records transfer as HubSpot engagement emails, preserving subject line, body content, direction (sent/received), timestamp, and owner attribution. Email attachments migrate as HubSpot file attachments linked to the engagement record, maintaining complete email context within the contact timeline.

Paradigm meeting or calendar event records transfer as HubSpot meetings with original start and end timestamps, title, body, and attendee list preserved. Attendee resolution matches by email address to HubSpot contact or user records, linking meeting participants to the correct CRM records during the migration.

Paradigm notes map to HubSpot engagement notes. Rich-text formatting in note bodies is preserved where the Paradigm export format supports it. Notes without an associated contact or company are attached to the most recently linked record by default, configurable before migration.

Paradigm custom objects map 1:1 to HubSpot custom objects (available on Professional and Enterprise plans). Custom object associations that use N:N linking in Paradigm require HubSpot association-journal or junction-object setup — FlitStack surfaces these as part of the migration plan.

File attachments associated with contacts, companies, deals, or custom objects are downloaded from Paradigm's storage and re-uploaded to HubSpot Files. File size limits apply: HubSpot allows files up to the attachment size limit set by your plan (typically 10MB on Starter, higher on Enterprise).

Paradigm user and owner records are resolved by email match against HubSpot user accounts. Unmatched owners are flagged before migration — teams either invite them to HubSpot or assign records to a fallback user. Deactivated Paradigm users are optionally preserved as inactive HubSpot users to maintain historical owner attribution.

Paradigm workflows, rules, and automation triggers have no transferable equivalent in HubSpot's data model and cannot be exported in a transferable format. FlitStack migrates data and schema only — teams must rebuild all automation logic manually in HubSpot's workflow builder. As part of the migration package, FlitStack exports Paradigm workflow definitions as a structured reference document listing each rule's trigger, conditions, and actions.

Paradigm report and dashboard definitions are not exportable in a transferable format — report layouts, saved filters, chart configurations, and dashboard grids remain in Paradigm. The underlying data migrates fully to HubSpot, but report definitions require manual recreation using HubSpot's reporting tools. Teams should allocate HubSpot admin hours to rebuild critical reports before go-live.