Migrate from CINC to Salesforce Sales Cloud

Flat contact-to-property mapping creates Account-Contact hierarchy decisions

CINC stores contacts with a single primary property reference — a flat model where each contact has one owner_id and one property_id. Salesforce requires every Contact to have an AccountId, creating a hierarchy where Contacts live under Accounts. When a CINC contact has no property, there is no natural Account to attach it to. FlitStack surfaces this as a mapping decision: contacts without properties route to Lead, or your admin creates placeholder household Accounts before migration. The choice affects every downstream report, sharing rule, and automation that depends on Account-Contact relationships.

CINC deal stage pick-list values must map explicitly to Salesforce StageName

Salesforce Opportunity StageName is a pick-list scoped by RecordTypeId — the values 'Closed Won' and 'closed won' are treated as different strings and will fail validation if the exact value does not exist in the target record type's pick-list. CINC's deal stages may use different naming conventions or capitalization. FlitStack builds an explicit value map for every CINC stage name before migration runs, so no Opportunity lands with an invalid StageName. If CINC stages have no Salesforce equivalent, they require either a custom field or a decision to consolidate into existing stage values.

CINC owner_id resolution requires active Salesforce users

Salesforce OwnerId is a lookup to the User object — it cannot accept a string or an inactive user. CINC owner_id references a user by ID but may reference an inactive account or a user who has not been provisioned in Salesforce. FlitStack matches owner_id to Salesforce Users by email lookup before migration. Any owner without a Salesforce account gets flagged in the pre-migration audit. If a CINC owner has left the team, their records can be assigned to a fallback owner — but this must be decided before the migration runs, not after records start landing in Salesforce.

CINC API rate limits may extend large dataset export duration

CINC's API enforces rate limits that vary by plan tier. Large datasets — particularly activity logs with hundreds of thousands of engagement records — can take multiple days to export if pagination and backoff are not handled carefully. Salesforce's Bulk API 2.0 supports significantly higher throughput on the write side (15,000 batches per day with 10,000 records per batch), so the CINC export is typically the bottleneck. FlitStack implements exponential backoff and chunked export windows to avoid rate limit errors while maximizing export speed within CINC's constraints.

File attachments exceeding 25MB require pre-planned handling

Salesforce Files has a default 25MB per-file limit for uploads via API. CINC property or contact attachments may include files larger than this threshold — inspection reports, HOA meeting recordings, or high-resolution images are common culprits. FlitStack identifies files that exceed the Salesforce limit during the pre-migration audit. Options include chunking the file, storing a link reference to external storage, or adjusting the Salesforce org's file size limits. This decision must be made before the migration runs so files are handled consistently rather than failing mid-load.