Migrate from Lofty to Microsoft Dynamics 365 Sales

Lofty API date-range window creates export complexity that risks incomplete data sets

Lofty Open API v2.0 enforces a hard 90-day maximum between start and end dates on any single query. Teams with historical data spanning years must run multiple paginated requests segmented by date windows — a process that adds extraction passes and increases the chance that records created during export are missed. Lofty also returns entity IDs as 64-bit integers, which JavaScript silently truncates past the safe integer limit (2^53-1). FlitStack AI handles Lofty IDs as strings from extraction through to the Dynamics custom field to avoid silent data corruption. A post-migration cross-reference check validates that every record ID in Dynamics has a corresponding Lofty source record before the delta window closes.

Lofty's embedded real estate model decomposes into multiple Dynamics tables, requiring custom Dataverse tables and relationship integrity validation

Lofty stores property and transaction data as embedded fields within the Lead record. Dynamics 365 Sales has no native real estate object model — the platform uses Accounts, Contacts, Leads, and Opportunities as standard tables. Each Lofty lead with embedded property data must decompose into a Lead record plus a custom Dataverse Property__c table with a lookup relationship, and optionally a Transaction__c table linked to an Opportunity record. If Dynamics 365 Sales Professional is in use, the 15 custom table cap may be reached quickly with active real estate pipelines, requiring either a custom multi-field workaround or an upgrade to Enterprise before migration. FlitStack AI delivers a schema design document identifying every custom table needed and the relationship cardinality before data movement begins.

Lofty workflows and lead-routing sequences have no export path — every automation must be manually rebuilt in Power Automate

Lofty's automation engine governs lead routing, follow-up sequences, and task generation with no public API and no export utility. The platform stores workflow definitions in the Lofty UI only. When migrating to Dynamics 365 Sales, every Lofty workflow — whether it routes inbound leads to agents by geography, triggers follow-up tasks after a showing, or sequences nurture emails — must be rebuilt from scratch in Power Automate. FlitStack AI cannot migrate the logic; it provides a documented reference of every active Lofty workflow with its trigger conditions and actions so your Dynamics admin has a starting specification for the Power Automate rebuild. Plan the rebuild as a parallel workstream before go-live to avoid losing automation coverage.

Lofty custom field tiers create uneven migration scope — Starter-plan accounts are limited to 10 fields per type

Lofty caps Starter plan accounts at 10 custom fields per field type (text, date, number, percentage, currency, single-select, multi-select). Other plans raise this to 50 per type. When migrating to Dynamics 365 Sales, the actual number of custom fields depends on the plan the Lofty account was on at the time of export, not the current plan. Starter-plan accounts with 10 or fewer custom fields per type map cleanly into Dataverse choice or text columns. Accounts that hit the Starter cap and then upgraded may have inconsistent field coverage — some types at 10, others at 50 — requiring careful field-by-field inventory before mapping begins. FlitStack AI inventories the actual exported custom field set during the discovery phase rather than relying on plan-level documentation.

Dynamics 365 Security Roles and Field-Level Security must be reconfigured after data lands — Lofty permissions do not auto-translate

Lofty uses a simpler permission model where owner assignment primarily controls record visibility and platform-level roles govern feature access. Dynamics 365 enforces explicit Security Roles, Field-Level Security on individual fields, and record-sharing rules that operate independently of owner assignment. A Lofty record visible to a team because the owner shared it will be invisible in Dynamics until a Security Role with the appropriate Read privilege is assigned. Field-Level Security can block specific fields from appearing for users who do not hold the required privilege — a concept that has no equivalent in Lofty. FlitStack AI documents every Lofty owner and team assignment during discovery so your Dynamics admin can map those to appropriate Security Roles and sharing rules before user acceptance testing begins.