Yardi to Dynamics 365 migration
Moving from Yardi Voyager or Yardi Breeze to Microsoft Dynamics 365 Sales means transforming property management records into a CRM structure. FlitStack AI maps Yardi tenant contacts, owner records, and vendor data into Dynamics 365 Leads, Contacts, and Accounts — preserving original create dates, contact associations, and property references so your sales team can link prospect relationships to underlying real estate assets without re-keying information.
FlitStack AI migrates contacts, accounts, leads, custom entity: realestateassets and custom entity: realestateleases from Yardi to Dynamics 365, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 2–4 weeks for under 25,000 contact records with standard property-to-account mapping.

What moves from Yardi to Dynamics 365?
Yardi and Dynamics 365 Sales operate in fundamentally different domains — Yardi is a property management platform built around units, leases, and rent rolls, while Dynamics 365 Sales is a CRM organized around leads, opportunities, and sales pipelines.
Read the full summary
The migration challenge is extracting contact-centric data from Yardi's relational model (tenants, owners, vendors, prospects) and reshaping it into Dynamics 365's Account-Contact-Lead schema. We map Yardi contact records to Dynamics 365 Contacts for existing tenant and owner relationships, and to Leads for prospects not yet converted. Property and unit references that have no native CRM equivalent become custom fields (new_PropertyReference_c, new_UnitID_c) or a custom RealEstateAsset entity, depending on your data volume. Lease terms, rent schedules, and accounting balances cannot migrate as operational Dynamics 365 records — they require a separate reporting layer or Power BI semantic model. Workflows, automations, and rent-roll configurations built in Yardi have no equivalent in Dynamics 365 and must be documented for manual rebuild. Our migration uses Yardi's Voyager 7S API for data extraction, transforms contact and property references through field-level mapping, and loads via the Dynamics 365 Web API with Dataverse table support. A delta-pickup window captures any Yardi records modified during the cutover window so Dynamics 365 reflects the final state at go-live.
Tenant Contact → Contact
Yardi tenant records (name, email, phone, lease start date) map directly to Dynamics 365 Contact fields.
How it maps
The primary AccountId is resolved by matching the tenant's property address to a corresponding owner or landlord Account in Dynamics 365. Unmatched tenants create a Contact record with no AccountId and are flagged for manual account assignment.
Property Owner → Account
Yardi owner records (company name, contact person, mailing address, ownership percentage) map to Dynamics 365 Account records.
How it maps
Owner type codes (individual, LLC, corporation) map to Account Type pick-list values via value mapping. Multiple properties owned by the same entity consolidate into a single Account with property references in a custom RealEstateAsset custom entity linked via AccountId.
Vendor → Account
Yardi vendor records map to Dynamics 365 Accounts with Account Type set to 'Vendor'.
How it maps
Vendor category codes (maintenance, landscaping, legal, utilities) map to a custom VendorCategory_c pick-list field created in Dataverse. Vendor contacts within Yardi become Account-level Contacts linked to the vendor Account.
Prospect/Inquiry → Lead
Yardi prospect records from the leasing inquiry workflow map to Dynamics 365 Leads.
How it maps
The prospect's desired unit type, bedrooms, price range, and move-in date transform into Lead fields (leadqualitycode, estimatedamount, purchasedate_c custom fields). Lead source defaults to 'Property Inquiry' with the source property referenced in new_PropertySource_c custom field.
Property → Custom Entity: RealEstateAsset
Yardi property records have no native equivalent in Dynamics 365 Sales.
How it maps
We create a custom RealEstateAsset table in Dataverse with fields for PropertyName, PropertyType, Address, UnitCount, and VacancyRate. The RealEstateAsset entity links to Account records for landlords and to Contacts for tenant assignments via a custom Lookup field.
Lease → Custom Entity: RealEstateLease
Yardi lease records map to a custom RealEstateLease Dataverse entity since Dynamics 365 Sales has no lease entity.
How it maps
Fields include LeaseStartDate, LeaseEndDate, MonthlyRent, SecurityDeposit, EscalationRate, and UnitReference_c lookup to RealEstateAsset. This custom entity links Contact (tenant) to RealEstateAsset (unit) and preserves lease terms for reporting.
- Tenant ContactContact1:1
- Property OwnerAccount1:1
- VendorAccount1:1
- Prospect/InquiryLeadtransformed
- PropertyCustom Entity: RealEstateAssettransformed
- LeaseCustom Entity: RealEstateLeasetransformed
+ 5 more in the mapping below
How Yardi and Dynamics 365 differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | Yardi | Dynamics 365 |
|---|---|---|
| Core data model | Yardi organizes around Properties, Units, Leases, and Tenants with rent-roll accounting as the central construct | Dynamics 365 Sales uses Accounts (companies), Contacts (people), Leads, and Opportunities with pipeline stage tracking |
| Contact ownership | Yardi associates contacts to Properties and Units via lease records; tenant contact is linked to a specific unit address | Dynamics 365 Contacts require an AccountId lookup to an Account; unassociated contacts route to Leads or a placeholder Account |
| Lease data handling | Leases are core Yardi entities with start/end dates, rent amounts, escalation clauses, and security deposit tracking | Dynamics 365 has no lease entity; lease terms become custom fields on Contact or a custom RealEstateLease entity in Dataverse |
| API access model | Yardi Voyager 7S API provides read access via ySQL queries; Breeze uses REST endpoints with per-user rate limits | Dynamics 365 Web API (Dataverse) supports CRUD operations with Power Platform request limits (75,000 requests per 24 hours per app) |
| Automation rebuild requirement | Yardi automations (rent reminders, lease renewal alerts, work order triggers) are property-management-specific constructs | Dynamics 365 uses Power Automate workflows and Dynamics workflow processes; automations require complete manual rebuild |
| Reporting layer | Yardi reporting centers on rent rolls, occupancy rates, and property performance dashboards | Dynamics 365 reporting uses Opportunities, pipeline analytics, and sales forecasting; property metrics require Power BI semantic model |
Yardi to Dynamics 365 field mapping
The 30 most-used fields of 43 mapped for this pair. Custom fields are added from your own schema during scoping. Download the full mapping (CSV) ↓ or open it in the field mapping template.
-
firstnameTenant ContactFirstNameContact -
lastnameTenant ContactLastNameContact -
emailTenant ContactEmailAddressContact -
phoneTenant ContactTelephone1Contact -
mobilephoneTenant ContactMobilePhoneContact
| Yardi field | Dynamics 365 field | Mapping | Note |
|---|---|---|---|
Tenant Contact.firstname | Contact.FirstName | direct | |
Tenant Contact.lastname | Contact.LastName | direct | |
Tenant Contact.email | Contact.EmailAddress | direct | |
Tenant Contact.phone | Contact.Telephone1 | direct | |
Tenant Contact.mobilephone | Contact.MobilePhone | direct | |
Tenant Contact.lease_start_date | Contact.LeaseStartDate_c | custom_field_required | Lease dates stored as custom field on Contact since Dynamics 365 has no native lease start date field. |
Tenant Contact.lease_end_date | Contact.LeaseEndDate_c | custom_field_required | Lease end date preserved as custom datetime field; used to flag renewal opportunity Cases. |
Tenant Contact.monthly_rent | Contact.MonthlyRent_c | custom_field_required | Rent amount from Yardi lease stored as custom currency field on Contact for reference reporting. |
Tenant Contact.unit_number | Contact.UnitReference_c | custom_field_required | Unit number links to RealEstateAsset custom entity via lookup relationship. |
Tenant Contact.yardi_contact_id | Contact.SourceSystemID_c | custom_field_required | Yardi internal contact ID stored for delta-run de-duplication and traceability. |
Tenant Contact.created_date | Contact.Original_Create_Date_c | custom_field_required | Original Yardi create date preserved as custom datetime since Dynamics CreatedDate is set at migration time. |
Property Owner.company_name | Account.Name | direct | |
Property Owner.contact_first_name | Account.PrimaryContactId.FirstName | transformed | Owner contact person created as primary Contact linked to Account; Account record created first. |
Property Owner.contact_last_name | Account.PrimaryContactId.LastName | transformed | Owner contact person created as primary Contact linked to Account. |
Property Owner.owner_type_code | Account.AccountTypeCode_c | value_mapping | Yardi owner type codes (Individual, LLC, Corporation, Trust) map to custom pick-list values on Account. |
Property Owner.address_line_1 | Account.Address1_Line1 | direct | |
Property Owner.city | Account.Address1_City | direct | |
Property Owner.state | Account.Address1_StateOrProvince | direct | |
Property Owner.zip_code | Account.Address1_PostalCode | direct | |
Property Owner.ownership_percentage | Account.OwnershipPercentage_c | custom_field_required | Ownership percentage stored as custom number field for multi-owner property reporting. |
Property Owner.yardi_owner_id | Account.SourceSystemID_c | custom_field_required | Yardi owner ID stored for delta-run de-duplication and lookup integrity. |
Vendor.vendor_name | Account.Name | direct | |
Vendor.vendor_category | Account.VendorCategory_c | value_mapping | Yardi vendor categories (Maintenance, Landscaping, Legal, Accounting) map to custom pick-list values. |
Vendor.phone | Account.Telephone1 | direct | |
Vendor.email | Account.EmailAddress | direct | |
Prospect.prospect_name | Lead.FullName | direct | |
Prospect.email | Lead.EmailAddress | direct | |
Prospect.phone | Lead.Telephone1 | direct | |
Prospect.desired_unit_type | Lead.DesiredUnitType_c | custom_field_required | Unit type preference (Studio, 1BR, 2BR, etc.) stored as custom pick-list field on Lead. |
Prospect.move_in_date | Lead.EstimatedCloseDate | transformed | Desired move-in date maps to estimated close date on Lead; converted to Date field. |
What to watch for in a Yardi to Dynamics 365 migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
Yardi API access requires Voyager 7S or Yardi Breeze REST authentication, not a standard OAuth flow
Yardi does not expose data via a conventional REST or Graph API with OAuth 2.0.
How we handle it
Voyager uses ySQL queries against the database, and Yardi Breeze uses a proprietary REST interface with per-user API key authentication. FlitStack AI connects to the Yardi tenant via ySQL for Voyager setups (requiring read-only database credentials) and via Breeze REST endpoints with API key for Breeze tenants. API rate limits in Yardi Breeze are per-user and throttled during business hours; we schedule bulk exports during off-peak windows to avoid hitting quotas. If the Yardi tenant lacks API access, FlitStack can use Yardi's custom report export feature with CSV extraction, but this requires Yardi admin involvement to configure the export template. The read access limitation is disclosed upfront during the discovery call.
Custom Dataverse entities for RealEstateAsset and RealEstateLease require Dynamics 365 Sales Enterprise licensing
Dynamics 365 Sales Professional caps custom table creation at 15 tables total across the environment.
How we handle it
Yardi migrations that require a RealEstateAsset custom entity plus a RealEstateLease custom entity plus supporting custom fields will exceed the Professional limit. FlitStack AI surfaces this during discovery — if the destination tenant is on Sales Professional licensing, we recommend either upgrading to Sales Enterprise (required for more than 15 custom tables) or collapsing property references into custom fields on the Account entity. The Dynamics 365 Licensing Guide confirms that Sales Enterprise ($105 per user per month) removes the custom table ceiling and enables unlimited Power Platform extensions. We do not begin migration until the licensing tier is confirmed.
Lease data has no operational equivalent in Dynamics 365 Sales — it becomes a reference record, not a working object
Yardi lease records contain rent escalation clauses, security deposit tracking, and renewal options that have no native field in Dynamics 365.
How we handle it
Migrating them as custom fields on the Contact or as a RealEstateLease custom entity preserves the data for reference but does not create working lease management functionality. Dynamics 365 Sales is not a lease management tool — if the team needs rent reminders, escalation automation, or lease renewal workflows, those require Power Automate flows built post-migration. FlitStack exports the complete lease data structure from Yardi as a JSON audit file alongside the migration run so the Dynamics admin can reference the full lease schema when building flows. We do not claim to replicate Yardi's lease management logic in Dynamics 365.
Yardi contact-to-property associations require N:1 resolution in Dynamics 365's AccountId model
Yardi allows a contact to be associated with multiple properties simultaneously (an owner with five buildings, a tenant who rents two units).
How we handle it
Dynamics 365 Contacts have a single primary AccountId lookup. We resolve the N:1 constraint by assigning the most recent lease or highest-ownership-percentage property as the primary AccountId and linking remaining property associations via the RealEstateAsset custom entity's lookup field on the Contact record. This preserves the full property association history while satisfying Dynamics 365's schema requirement. Teams should verify that the primary account assignment rule aligns with their sales process before the migration runs.
Payment history and accounting data cannot populate Dynamics 365 financial records without a separate ERP integration
Yardi payment history (rent received, late fees, security deposit transactions) is accounting data.
How we handle it
Dynamics 365 Sales does not contain a GL, accounts receivable, or payment tracking module — those belong to Dynamics 365 Finance or Dynamics 365 Business Central. We migrate payment history as records in the custom LeasePayment entity for reference and reporting purposes only. The data cannot create invoices, post to the GL, or trigger Collections Cases without a separate Business Central integration. We disclose this limitation in the migration plan and can recommend a Power Automate flow that creates a Task on the Contact when a payment record indicates a delinquency flag.
How the migration runs
Yardi API access verification and export path confirmation
FlitStack AI begins by confirming the Yardi tenant type (Voyager vs.
What this step covers
Breeze) and the available API access method. For Voyager tenants, we request read-only ySQL credentials scoped to the contact, owner, property, and lease tables. For Breeze tenants, we validate the REST API key and test connectivity against the /contacts, /owners, /properties, and /leases endpoints. If API access is unavailable, we work with the Yardi admin to configure custom report exports with CSV output. This step produces an export feasibility report documenting row counts per Yardi entity, any missing fields, and estimated API quota consumption for the migration volume.
Dynamics 365 schema provisioning — custom entities and fields
Before any data loads, FlitStack provisions the custom Dataverse entities required for property management data.
What this step covers
This includes creating the RealEstateAsset table with columns for PropertyName, PropertyType, Address, UnitCount, and VacancyRate; the RealEstateLease table with LeaseStartDate, LeaseEndDate, MonthlyRent, EscalationRate, and UnitReference_c lookup; and LeasePayment for historical payment records. Custom fields on standard entities (Account, Contact, Lead, Incident) are also created during this step. We deliver a Dynamics 365 setup manifest showing every custom field created, its data type, and the corresponding Yardi source field so the Dynamics admin can review before the migration loads data.
Owner and vendor accounts loaded first to satisfy AccountId foreign keys
Dynamics 365 requires Account records to exist before Contacts can be linked via AccountId.
What this step covers
We sequence the migration so Property Owner accounts and Vendor accounts load first, resolving the AccountId values that tenant Contacts will reference. Owner records are matched by company name and owner type code; vendor records by vendor name and category. Any duplicate Account candidates (same company name in Yardi under different owner IDs) are surfaced for manual resolution before the Contact load proceeds. Unmatched tenant Contacts that lack a valid AccountId are loaded as Leads with the Yardi contact data preserved, and flagged for account assignment post-migration.
Sample migration run with field-level diff
A representative slice of records — typically 200–500 across contacts, owners, vendors, properties, and a sample lease — is migrated first into the Dynamics 365 sandbox or production (based on the client's preference).
What this step covers
FlitStack generates a field-level diff comparing source Yardi values against the loaded Dynamics 365 values for every mapped field. The diff report highlights any null values, truncation, pick-list mismatches, or date format discrepancies. We review the diff with the client's Dynamics admin to confirm that contact-to-account linkage, custom field values, and RealEstateAsset lookups resolve correctly before committing to the full migration run.
Full migration run with delta-pickup window and audit log
The full migration extracts all confirmed Yardi entities (contacts, owners, vendors, properties, leases, work orders, documents) and loads them into Dynamics 365 following the sequenced order established in Step 3.
What this step covers
A delta-pickup window of 24–48 hours runs in parallel with the cutover, capturing any Yardi records modified or created during the final hours before go-live. Every load operation is logged in FlitStack's audit log with source record ID, destination record ID, timestamp, and operator. If reconciliation fails (record count discrepancy, referential integrity error), one-click rollback reverts the Dynamics 365 environment to its pre-migration state so the issue can be investigated and the run re-executed.
- Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
Yardi-to-Dynamics 365 Sales migration pricing reflects three primary drivers. First, contact record volume from Yardi tenants, owners, and vendors determines base extraction and load effort. Second, the number of distinct property types (residential, commercial, mixed-use) creates multiple account-segmentation rules that require separate field-mapping configurations. Third, the need to create custom Dataverse entities (RealEstateAsset, RealEstateLease) for property references that cannot map to standard Dynamics 365 fields adds schema complexity. Yardi setups with active API access and clean export paths fall in the lower range; complex multi-property portfolios requiring custom entity architecture and extensive value-mapping for owner type codes land in the upper range. Yardi Breeze tenants with limited API access may require custom report exports that add data-preparation time. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Yardi to Dynamics 365 →Why teams move from Yardi to Dynamics 365
- Yardi's property-centric reporting doesn't support sales pipeline visibility — real estate firms expanding into brokerage, development, or investment sales need a CRM that tracks leads, opportunities, and deal stages. Dynamics 365 Sales provides pipeline analytics and forecasting that Yardi's rent-roll model cannot replicate without a separate BI layer. Multiple property management teams cited this gap when evaluating Yardi alternatives on G2 review forums.
- Yardi's per-unit pricing model scales with portfolio size, making it expensive for firms that also need CRM functionality for sales teams. Dynamics 365 Sales Enterprise at $105 per user per month bundles CRM, Copilot AI, and Power Platform integration at a per-seat price that consolidates two separate tools. Organizations already paying for Microsoft 365 E3/E5 licenses often qualify for reduced Dynamics 365 attachment pricing.
- Yardi Voyager's interface is described as dated and navigation-heavy by mid-market property managers on G2 reviews. Teams evaluating the switch to Dynamics 365 Sales frequently cite the familiar Microsoft 365 interface — Outlook integration, Teams collaboration, Excel-connected reporting — as a driver to consolidate onto a platform their organization already licenses. Reddit discussions in r/PropertyManagement confirm that Yardi's steep learning curve pushes teams toward alternatives.
- Yardi Breeze lacks the API access depth that mid-market and enterprise property managers need for custom integrations. Teams managing complex data flows between Yardi and financial reporting tools report that limited export options create manual bottlenecks. Dynamics 365 Sales Web API with Dataverse supports direct query, bulk operations, and Power Platform connectors that Yardi's interface-based workflows cannot match.
- Acquired companies frequently use different property management systems, creating a data consolidation challenge. When one entity runs Yardi and the parent company runs Dynamics 365, migration of tenant and owner contact records into the corporate CRM becomes a post-acquisition integration priority. Migrating Yardi contacts to Dynamics 365 unifies the sales and property management view under a single platform.
Questions, answered
Yardi to Dynamics 365 migration questions
How long does a Yardi to Dynamics 365 Sales migration take?
Most Yardi-to-Dynamics 365 migrations complete in 2–4 weeks of clock time for under 25,000 contact records. Larger portfolios exceeding 100,000 records or setups requiring custom RealEstateAsset and RealEstateLease entity creation extend to 6–10 weeks. The longest planning step is confirming Yardi API access (Voyager ySQL vs. Breeze REST) and provisioning the Dynamics 365 custom entities before data loads begin. Yardi Breeze tenants without API access require manual report exports that add data-preparation time.
Will my Yardi rent reminders, lease renewal alerts, and work order automations migrate to Dynamics 365?
No. FlitStack AI migrates data and schema only — Yardi workflows, rent escalation rules, lease renewal alerts, and work order trigger automations do not migrate. They are property-management-specific constructs with no equivalent in Dynamics 365 Sales. Yardi automations must be rebuilt as Power Automate flows or Dynamics workflow processes on the Dynamics 365 side. We export the Yardi workflow definitions as a reference document listing each automation's trigger, conditions, and actions so your Dynamics admin has a rebuild blueprint. Lease escalation calculations and rent reminder logic require Power Apps or Power Automate custom development.
What happens to my Yardi lease data in Dynamics 365 Sales?
Yardi lease records become a custom RealEstateLease entity in Dataverse since Dynamics 365 has no native lease management module. Each lease migrates with start date, end date, monthly rent, escalation rate, and security deposit preserved as custom fields. Lease data is reference information in Dynamics 365 — it does not trigger rent reminders, generate invoices, or automate renewal workflows. If your team needs lease operations in the CRM, those require Power Automate flows built post-migration. The complete Yardi lease schema is exported as a JSON audit file alongside the migration for rebuild reference.
Can I migrate Yardi property records to Dynamics 365?
Yardi property records have no standard equivalent in Dynamics 365 Sales. We create a custom RealEstateAsset table in Dataverse to store property name, property type, address, unit count, and vacancy rate. The RealEstateAsset entity links to Account records (for landlord owners) and to Contacts (for tenant assignments) via lookup fields. This approach works for portfolios under 10,000 units per custom entity. If your Yardi setup has more than 10,000 property records, we recommend storing property references as custom fields on the Account entity instead to stay within Dataverse row limits.
How does Yardi contact-to-property association resolve in Dynamics 365 when a tenant has multiple leases?
Yardi allows a contact to lease multiple units simultaneously. Dynamics 365 Contacts have a single primary AccountId lookup. We resolve this by assigning the most recent lease's property as the primary AccountId on the Contact record and storing additional property associations as lookup links in the RealEstateAsset entity's ContactId_c field. This preserves the full association history while satisfying Dynamics 365's schema constraint. Before migration, your team specifies the assignment rule (most recent lease, highest rent, or most units) so FlitStack applies it consistently across all multi-lease contacts.
Does the migration affect my Yardi account during the cutover?
No. FlitStack AI uses read-only API access (ySQL for Voyager, REST for Breeze) during the migration — your team continues working in Yardi throughout. A 24–48 hour delta-pickup window runs after the main load completes, capturing any records modified or created in Yardi during the final hours before cutover. Documents and attachments are downloaded from Yardi and re-uploaded to SharePoint via the Dynamics 365 integration; original filenames and upload timestamps are preserved. The audit log tracks every operation so your team can reconcile record counts against the Yardi database after go-live.
What happens to my Yardi payment history and accounting data?
Yardi payment history migrates to a custom LeasePayment entity in Dataverse linked to the corresponding RealEstateLease record. Fields include payment date, amount, payment method, and late fee flag. This data supports historical reporting in Power BI but does not create Dynamics 365 invoices, post to a GL, or trigger Collections Cases. Dynamics 365 Sales does not contain accounting functionality — payment tracking and accounts receivable belong to Dynamics 365 Finance or Business Central. FlitStack can recommend a Power Automate flow that creates a Task on the Contact when a LeasePayment record shows a delinquency flag, but full accounting integration requires a separate Business Central engagement.
Why do I need Dynamics 365 Sales Enterprise instead of Professional for this migration?
Dynamics 365 Sales Professional caps custom Dataverse tables at 15 total. A Yardi migration requiring a RealEstateAsset table, a RealEstateLease table, a LeasePayment table, plus supporting custom fields on Account, Contact, Lead, and Incident will exceed that limit. Sales Enterprise removes the custom table ceiling and enables unlimited Power Platform extensions including Power Apps and Power Automate flows needed to rebuild Yardi automations. FlitStack confirms the licensing tier during discovery. If staying on Sales Professional, we collapse property references into custom fields on Account and document the trade-off in the migration plan.
Related migrations
Dynamics 365 implementation
Set up Dynamics 365 and migrate into it as one engagement.
See the service → Jobber to Dynamics 365Mapping · history · rollbackClose to Dynamics 365Mapping · history · rollbackLeadforce CRM to Dynamics 365Mapping · history · rollbackInsightly CRM to Dynamics 365Mapping · history · rollbackCivicrm to Dynamics 365Mapping · history · rollbackActiveCampaign to Dynamics 365Mapping · history · rollback Yardi to HubSpotMapping · history · rollbackYardi to SalesforceMapping · history · rollbackSources: official documentation
- Dynamics 365 environment strategy — Microsoft Learn
- Import accounts, leads, or other data — Microsoft Learn (Dynamics 365)
- Import data (all record types) — Power Platform | Microsoft Learn
- Execute Batch Operations on Dataverse — Microsoft Learn
- Service protection limits (Microsoft Dataverse)
- Entity relationship behavior — Microsoft Learn
Get a quote
Moving from Yardi to Dynamics 365?
Tell us roughly how many records and objects you have. We scope the mapping and the Dynamics 365 setup with you, then send a quote.
Get a quote