Migrate from Marketing 360 to HubSpot

Marketing 360 contact records map directly to HubSpot contacts. The Marketing 360 contact ID is preserved as a custom HubSpot property (source_contact_id) for traceability. Standard fields (firstName, lastName, email, phone) transfer to HubSpot properties of the same name. Custom field IDs from the Marketing 360 customFields array are resolved to named HubSpot properties before writing.

Marketing 360 stores extended contact data in a customFields array with integer IDs and string values. FlitStack resolves each ID against the Marketing 360 custom field definitions discovered during the API audit, then maps the values to named HubSpot custom properties on the contact. Any custom field without a matching HubSpot property is created as a new HubSpot property before migration runs. ID-to-name mapping is documented in the migration manifest.

Marketing 360 contacts can carry multiple tags (id + tag name). These migrate to HubSpot as a comma-separated contact property (original_tags) for reference, and FlitStack can optionally create HubSpot contact lists for each unique tag so lists can drive HubSpot workflows post-migration. Tags that map to HubSpot's contact property names are written directly.

Marketing 360's additionalInfo field is a free-text field on the contact record. It migrates to a custom long-text property (m360_additional_info) on the HubSpot contact. If the field contains structured sub-fields, FlitStack parses and surfaces them as individual properties or as a note attachment.

Marketing 360 company records map directly to HubSpot companies. The company name, domain, and address fields transfer to HubSpot's Company object properties. Company records in Marketing 360 that are linked to contacts are linked via HubSpot's native contact-company association after both objects land.

Marketing 360 tasks whose type indicates a sales deal (e.g., type.name = 'Sales', 'Opportunity', 'Project') are candidates for HubSpot deals. The task name becomes the deal name; the task's additionalInfo is parsed for deal amount and close date if present. If Marketing 360 task statuses are structured as stage proxies, FlitStack maps them to HubSpot deal stages. Multiple task types may map to a single HubSpot pipeline — FlitStack surfaces this in the mapping plan.

Marketing 360 tasks with service-oriented types (e.g., type.name = 'Support', 'Service Request') migrate as HubSpot tickets. The task subject and additionalInfo become the ticket name and description. Task statuses map to HubSpot ticket pipeline stages. Assignees on the task resolve to HubSpot ticket owners by email match.

Marketing 360 tasks carry assignees with username, fullName, and email. FlitStack resolves each assignee email against HubSpot user records. Matched assignees become HubSpot deal or ticket owners. Unmatched assignees are flagged in the pre-migration report so the team can either invite the user to HubSpot or assign to a fallback owner.

Marketing 360 task types are not the same as HubSpot deal pipelines — they are a flat list of labels. FlitStack audits all task type values during discovery, then maps each type+status combination to the appropriate HubSpot deal stage or ticket pipeline stage. If multiple Marketing 360 types map to one HubSpot stage, this is documented as a collapse in the mapping plan.

Marketing 360's sourceByType field on contacts indicates the acquisition channel. This has no native HubSpot equivalent — it is preserved as a custom contact property (original_source_type) so attribution data is not lost even though HubSpot tracks source through its native contact source property and UTMs.

Marketing 360 stores payment processing data that is tied to its billing model (2.9% + $0.30 per transaction, card-present 2.6% + $0.10). This transaction data lives in the Payments module, not the CRM. FlitStack migrates contact and company records — payment history is preserved as a custom text property referencing the original Marketing 360 payment record ID for audit purposes but is not rebuilt as native HubSpot line items.

Marketing 360 uses organizationid to scope contacts to a sub-account or franchise unit. HubSpot does not have a native multi-org concept at the contact level — this value is preserved as a custom contact property (m360_organization_id) so reporting can filter by the original Marketing 360 organization.