Migrate from MARS to HubSpot

MARS contacts map directly to HubSpot contacts. The MARS contact record brings all standard fields (name, email, phone, job title, address) plus any custom properties into HubSpot's contact object. If MARS stores a company association on the contact, that company is resolved against the MARS Company object and linked as a HubSpot company association.

MARS contacts that carry a customer or account type flag route to HubSpot contacts with lifecycle_stage set to 'customer'. We apply this mapping based on the source type value; if MARS stores multiple equivalent flags, we take the highest-priority status at migration time and set HubSpot's lifecycle_stage accordingly.

MARS leads and prospects map to HubSpot contacts with lifecycle_stage set to 'lead'. This mapping ensures all MARS prospect records remain in HubSpot as standard contact objects without being routed to HubSpot's separate Lead object, which is reserved primarily for marketing-sourced leads. The approach preserves complete contact history and allows sales teams to work with the full prospect dataset from day one in HubSpot.

MARS company records map to HubSpot companies. Company name, domain, industry, employee count, and annual revenue map to their HubSpot counterparts. MARS parent-company relationships become HubSpot's parent-company association. Each MARS company can be associated with multiple MARS contacts; in HubSpot this becomes the company-contact association graph.

MARS deal records map to HubSpot deals. Each deal brings deal name, amount, stage, close date, owner, and associated contact/company IDs. The MARS deal pipeline maps to a HubSpot pipeline — if MARS stores multiple pipelines, each one becomes a separate HubSpot pipeline with its own stage set.

MARS pipeline definitions (stage names, stage order) become HubSpot pipeline definitions. In HubSpot each pipeline is created with its stages mapped to the MARS stage names. Stage probability and forecast category are derived from HubSpot defaults unless MARS stores explicit probability values, which we map value-by-value.

MARS call, email, and meeting records map to HubSpot engagements of the same type. Original timestamps, owner email addresses, and associated contact or company IDs are preserved. If MARS logs call duration or outcome, those values land as HubSpot engagement metadata properties.

MARS notes attach to the contact or company they were logged against. We re-create them in HubSpot with the same body text, original create date, and owner. If MARS stores rich-text formatting, we convert it to HubSpot's note format or store it as a text property.

MARS custom objects map 1:1 to HubSpot custom objects. We create the HubSpot custom object type first, then populate its records with the MARS field values mapped field-by-field. Any MARS custom object associations that use N:N relationships become HubSpot custom object associations or junction records.

MARS file attachments on contacts, companies, or deals are downloaded and re-uploaded to HubSpot Files, then linked back to the parent record. File size limits follow HubSpot's 25 MB per file. Inline images in notes are extracted and re-hosted as HubSpot file attachments.

MARS owner IDs resolve by email match against HubSpot users. Unmatched owners are flagged before migration so your team can either invite them to HubSpot or reassign their records to a fallback owner. No record lands in HubSpot without a valid owner.

MARS workflows, sequences, and automation rules do not have a migration path to HubSpot. They must be rebuilt inside HubSpot's workflow engine. We export your MARS workflow definitions as a structured reference document your HubSpot admin can use as a rebuild blueprint.