Migrate from CINC to HubSpot

Direct map. CINC homeowner contacts map to HubSpot contacts. CINC records one primary contact per property — that contact is flagged as primary and receives the primary AccountId lookup in HubSpot. Additional contacts migrate as separate HubSpot contacts linked to the same company. If duplicate email addresses exist across contacts, FlitStack flags them for merge or archive prior to migration to maintain data integrity.

Direct map. CINC agent contacts map to HubSpot contacts. Email uniqueness enforced in HubSpot — duplicate emails across contacts require merge or archive before migration. Agent contacts include team members, property managers, and staff; their roles can be stored in a custom property or the jobtitle field. If an agent appears in multiple CINC accounts, FlitStack consolidates those entries into a single HubSpot contact based on the matching email address, preserving all role information.

CINC property records become HubSpot companies. Property name maps to Company Name, address maps to address fields, and the original CINC property ID is stored as a custom property for reference. CINC property type (single-family, condo, HOA) maps to a custom Industry value or custom property. Additional attributes such as year built, number of units, and HOA fees migrate as custom properties, and homeowner contacts are linked via the AccountId lookup.

Direct map. CINC deals map to HubSpot deals. Deal name, amount, and close date migrate directly, and the CINC deal ID is stored as a custom property. Pipeline stage maps to HubSpot deal stage via value mapping, and the deal owner is resolved by matching the CINC owner email to a HubSpot user ID. Any additional deal-specific custom fields migrate as custom properties on the HubSpot deal record.

CINC pipeline (sales pipeline) maps to a HubSpot deal pipeline. Each CINC pipeline becomes a separate HubSpot pipeline, and teams with multiple CINC pipelines must have corresponding HubSpot pipelines pre-created. The stage names within each pipeline are mapped via value mapping to HubSpot deal stages, and stage probabilities are set according to HubSpot defaults or your specifications. Any pipeline-level custom properties are transferred as custom properties on the pipeline record.

Stage names are mapped value-by-value between CINC stages (New Lead, Showing Scheduled, Under Contract, Closed Won, etc.) and HubSpot deal stages. Stage probabilities are reapplied from HubSpot defaults or your specified values. Any custom properties attached to a stage migrate as custom properties on the HubSpot deal stage. The mapping is reviewed with your team before migration to ensure accuracy.

CINC work orders (maintenance requests, architectural requests) have no HubSpot standard equivalent. They migrate as a HubSpot custom object with fields for work order number, type, status, priority, assigned vendor, and property link. Junction object needed if N:N with properties.

CINC violation records have no HubSpot standard equivalent. They migrate as a HubSpot custom object with fields for violation type, status, date opened, fine amount, resolution date, and property link. Violation history preserved as activity records on the custom object.

CINC accounting module data (rent rolls, charges, payments, owner ledgers) has no HubSpot equivalent. Key financial fields migrate as custom properties on the company record (for property-level financials) or deal record (for transaction-level financials). Full accounting history stored as custom fields for reference.

CINC Owner field resolves to HubSpot users by email match. Unmatched owners flagged before migration — teams either create HubSpot users first or assign records to a fallback owner. Active CINC users who are not yet HubSpot users delay migration until user provisioning completes.

CINC file attachments (documents, images, correspondence) are re‑uploaded to HubSpot Files and linked to the appropriate object record using file URLs. Original file names and metadata (e.g., created date, author) are preserved where possible. HubSpot's file size limits apply, and any inline images embedded in notes are extracted, downloaded, and rehosted as HubSpot file assets. After migration, you can view or download the files directly from the linked record.