The most dangerous assumption in any Yardi or MRI data migration is that clean data in your legacy system means clean data for conversion. It does not.

Legacy property management platforms, whether you are migrating from Jenark, RealPage, AppFolio, a custom-built system, or even a well-maintained Excel environment, store data in structures that do not map directly to the target platform. The work of conversion is not simply export and import. It is a transformation: understanding what exists, deciding what needs to move, remapping structures, and validating that the result is functionally correct in the new system.

Three root causes drive the majority of Yardi and MRI data migration failures:

•  Manual ETL processes that do not scale - manually uploading files one at a time is not a viable approach for portfolios with hundreds of entities, thousands of leases, and years of transaction history.

•  Failure to distinguish static from dynamic data - treating all data as equivalent and trying to convert it all at once, rather than sequencing static configuration data before live transaction data.

•  Inadequate test conversion - running a test to check whether data is imported, rather than running a test to verify whether the data behaves correctly inside the new system.

technical work begins. You need to classify every data object you intend to migrate into one of three categories. This classification drives your sequencing, your cutoff dates, and your test conversion strategy.

Static data is the configuration chart of accounts, property codes, unit types, GL entity structures, fee schedules, and system setup parameters. This data does not change during the migration period. It should be converted and validated first, because every other data object depends on it being correct.

In Yardi and MRI environments, entity structures deserve particular attention. A legacy system may store 1,200 buildings as 1,200 separate properties, whereas MRI's structure merges multiple buildings into fewer GL entities. Collapsing that structure correctly without losing data integrity is one of the most technically demanding parts of a large migration.

Dynamic Transaction Data

Dynamic data is live: resident ledgers, open AR balances, lease charges, recurring billing schedules, AP open items, and security deposit balances. This data is updated daily until go-live. Your conversion approach must account for the fact that the source system is a moving target, and transactions are posted right up until the cutover date.

The practical implication is that you cannot finalize dynamic data conversion until the final cutoff is confirmed and the legacy system is locked. Plan multiple cutoff dates and build your ETL pipeline to be re-runnable, not one-time.

Historical Reported Data

Historical data is the transaction history that must be available in the new system for reporting purposes, typically, a rolling 12–24 months of AP history, prior-period lease activity, and audit trails. This data does not need to be functionally live on day one, but it must exist in the system before your first period close.

Classifying historical data separately allows you to sequence it as a lower-urgency conversion track, running parallel to the live data migration rather than blocking it.

For any migration of more than a few hundred units, manual file handling is a risk, not an inconvenience. A migration involving 6,000+ residential units, 4,000+ commercial leases, and 500+ GL entities cannot be managed through manual exports, field-mapping in spreadsheets, or individual file uploads. The error rate is too high, and the required time is incompatible with a tight go-live window.

A scalable data conversion pipeline for Yardi or MRI typically includes:

•  A custom extraction layer that pulls data from the legacy system in a structured, repeatable format, not one-time exports, but a program that can re-run against a refreshed source database

•  A transformation layer that applies business rules, handles structural mapping (like entity consolidation), resolves data quality issues, and produces output files in the exact format required by the target platform's import utilities

•  A staging environment, a dedicated conversion database separate from the development and production environments, where transformed data can be loaded and validated before touching live systems

•  A verification database that mirrors production, allowing side-by-side comparison of key metrics: trial balance totals, unit counts, open AR ageing, and deposit balances

The database environment architecture matters as much as the transformation logic. A well-designed migration uses at a minimum four separate environments: the legacy live system, a custom staging database, the target development database, and the target production database. Each plays a distinct role in the validation chain.

Most implementation teams run one test conversion. It confirms that the data was loaded without error. It does not confirm that the data works.

A complete data migration validation requires two distinct types of conversion tests, each answering a different question.

Does the data in the new system match the data in the legacy system? This means reconciling trial balances between the two platforms, verifying unit counts and lease counts, confirming that open AR balances match by property and entity, and checking that deposit totals tie out.

This test is primarily a numbers exercise. Your finance team and your implementation team need to sign off together. No migration should proceed to production cutover without a completed Type 1 test sign-off.

Type 2: Functional Data Verification

Can the data actually be used for day-one operations? This is where many test conversions fall short. The question is not whether the deposit balance imported correctly; it is whether a leasing agent can process a deposit refund against that balance on go-live day.

Type 2 testing covers:

•  Posting a payment against a converted AR balance

•  Processing a move-out and applying a converted security deposit

•  Running a charge batch against converted recurring billing schedules

•  Generating a statement for a converted commercial tenant

•  Closing a period using converted GL opening balances

Functional failures found in Type 2 testing are often not data problems; they are mapping, configuration, or structural problems with how the data was transformed. Finding them in test is far less costly than finding them on go-live day.

One of the most underestimated challenges in a Yardi or MRI data migration is that the business does not stop while the conversion is happening. Leases are signed. Tenants move in and out. Payments are posted. Properties are acquired or disposed of.

Your conversion team is working with data that changes every business day. A migration plan that does not explicitly address this reality will produce cutover errors regardless of how well the technical conversion work was done.

For large or complex migrations, a single cutoff date is rarely sufficient. Structure your cutoffs by data type: static configuration data can be finalized early; dynamic transaction data needs a hard cutoff close to go-live; historical reported data can have a separate, later cutoff.

Communicate cutoff dates in writing to every stakeholder who touches the source system. Any transaction posted after a data cutoff will require manual reconciliation at go-live. The goal is to make that list as short as possible.

Phase Commercial and Residential Data Separately

For portfolios with significant commercial and residential components, converting both simultaneously increases risk and complexity without meaningful benefit. Phasing the conversion of residential data first, commercial data second, or vice versa, depending on portfolio weighting and operational priority, reduces the scope of each test cycle and significantly speeds up error tracing.

Account for Structural Changes During the Project

Properties are acquired and disposed of. Entities are reorganized. Lease structures change mid-project. Your ETL pipeline needs to be built to accommodate these changes without requiring a full rebuild of your mapping logic. Document every structural change as it occurs, and verify that the change is reflected in both the source extraction and the target mapping before the final cutoff.

A data migration cannot rescue bad data. The quality of your source data bounds the quality of your conversion output. Before your project kickoff, assess your readiness against these criteria:

After supporting migrations across hundreds of Yardi and MRI implementations, the failure patterns repeat. Here are the risks that most consistently turn manageable projects into delayed go-lives:

•  Classify every data object as Static, Dynamic, or Historical before any technical work begins. This single decision drives your sequencing, cutoffs, and test strategy.

•  Build a scalable ETL pipeline, not a manual file process. Any migration of more than a few hundred units requires repeatable, programmatic data extraction and transformation.

•  Run two types of test conversion: one for data accuracy (do the numbers match?) and one for functional validity (can you actually use the data on day one?).

•  Plan for scope expansion. Conversion scope grows in nearly every implementation. Build flexibility into your timeline and tooling from the start.

•  A firm go-live date with a confirmed cutoff schedule is a prerequisite, not a deliverable. Without it, you cannot plan a reliable migration.

•  Data quality in the legacy system determines data quality in the new system. Invest in source data cleanup before the conversion starts, not during it.

Assetsoft has led data migration and conversion projects for property management firms managing portfolios ranging from a few hundred units to 10,000+ across residential and commercial asset classes on both Yardi and MRI platforms.

Our implementation team brings platform-specific ETL tooling, a proven conversion sequencing methodology, and hands-on experience with the data structures used by Yardi and MRI in production. We know where conversions break, and we build our approach to prevent them.

We offer a Migration Readiness Assessment that reviews your source data, maps your entity structure, identifies cleanup requirements, and produces a realistic conversion timeline before your project starts. It is the fastest way to know whether your go-live date is achievable and what stands between you and a clean cutover.

For developers and administrators accustomed to legacy web design tools from the past 20 years, the shift to PMX X.7 introduces a significant change: a greater reliance on JavaScript-based expressions.

While this might seem daunting at first, it enables dynamic field manipulation that was previously difficult to achieve. The new Page Builder allows you to use simple JS expressions to concatenate strings (e.g., combining a Building ID and Lease ID for a clean display) or perform on-the-fly arithmetic between input fields.

Why this matters: It reduces the need for heavy backend processing for simple display logic, making your custom pages faster and more responsive for the end-user.

One of the most significant improvements in the X.7 ecosystem is how Logic Builder APIs handle data compared to traditional data requests.

In the past, building custom pages often required extensive manual coding to ensure fields complied with security roles and data limits. The new Logic Builder APIs automatically return metadata on Table and Field Security and Field Lengths.

• Efficiency Boost: Page Builder automatically consumes this metadata. If a user tries to enter seven characters into a 6-character field, the page handles validation natively without requiring you to write any additional code.
• Security: Field-level security is respected automatically, saving developers roughly 80% of the validation work typically required during customization.

The true "killer feature" of the new Page Builder is the ability to pass entire data grids as objects to the API. This moves us beyond updating single records to handling complex, bulk transactions in a single call.

In the X.7 environment, you can define complex array structures in Logic Builder that mirror your Page Builder data grids. This allows you to:

• Loop through data: Create loops within your API to handle multiple rows.
• Batch Operations: Perform inserts, updates, and deletes within a single API transaction.
• Smart Updates: The system can distinguish between Original Value and Current Value, allowing the API to decide which records have changed intelligently and need updating, rather than unthinkingly overwriting data.

This architecture significantly reduces network traffic and database load, leading to a smoother experience for users managing high-volume data, such as rental updates or lease abstractions.

The bridge between SQL logic and Logic Builder scripts has never been shorter. The new environment supports an AI-assisted workflow in which developers can take complex SQL queries, such as joins between the Lease and Building tables and use AI tools to generate the equivalent Logic Builder script.

This AI co-pilot approach automates the creation of input parameters, data types, and variable mappings, turning a tedious manual process into one that takes seconds.

With the shift to a modern web architecture, the browser’s Developer Tools (Network Tab) becomes your best friend. Debugging in X.7 involves inspecting the JSON payloads passed between Page Builder and the API. This transparency enables rapid troubleshooting, ensuring your complex array structures are passed and received key-for-key.

This is where Assetsoft comes in. As a premier technology consulting firm for the real estate industry, we specialize in:

• MRI Software Upgrades: ensuring a smooth transition to Platform X.7.
• Customization: Building bespoke pages and reports that fit your unique business workflows.
• Integration: Connecting your customized MRI data with third-party apps.

Don't let the technical complexity of the new Page Builder slow down your operations. Let us help you build a system that works as hard as you do.

Ready to upgrade your MRI experience?

Visit us at www.assetsoft.biz to book a consultation today.

One of the most common risks in data conversion projects is scope creep. In a recent Assetsoft case study involving a migration from Jenark to MRI Software, the initial scope was limited to Residential and Commercial Management data. However, as the project progressed, the requirements expanded to include historical data, lease options, budgets, and scanned documents.

The Fix: Define your "Must-Haves" versus "Nice-to-Haves" early.

• Must-Have: Current Resident/Tenant data, recurring charges, security deposits, and open AR/AP.
• Nice-to-Have: Five years of historical transaction details (often, a trial balance as of a specific date is sufficient).

Be prepared for the reality that business doesn't stop during migration. We often see clients acquiring or disposing of properties during the conversion project. Your project plan must be flexible enough to handle these "moving targets" without derailing the entire timeline.

If you are onboarding a portfolio of 10 properties, manual entry may be sufficient. But when you are dealing with 2,600 commercial leases or 6,500 residential units, manual Extractions, Transformations, and Loading (ETL) are a recipe for disaster.

The Assetsoft Approach:

Manual uploads of one file at a time are inefficient and prone to human error. Instead, we recommend writing automated scripts or programs to extract source files and map them directly to the import format required by Yardi or MRI. Automation ensures consistency. If a mapping rule changes (e.g., how you handle "loss to lease"), you can update the script and re-run the entire dataset in minutes rather than hours.

Not all data is created equal. One of the most effective strategies we employ is classifying data into two buckets: Static and Transactional.

• Static Data: This includes property names, unit addresses, bank account details, and amenity codes. This data rarely changes.
• Transactional Data: This includes tenant ledgers, open charges, and GL balances. This data changes every day.

Best Practice: Load your Static Data early. By finalizing property lists and unit mixes weeks before your "Go-Live" date, you reduce pressure during the critical cut-off week. This allows your team to focus entirely on the dynamic, fast-moving transactional data when it matters most.

Never push converted data directly into your live production database without a safety net. A robust property onboarding strategy involves multiple database environments:

1. Dev Database: For the technical team to build and tweak extraction scripts.
2. Verification Database: Where the client reviews the raw data for accuracy.
3. Test Database: A "sandbox" environment where your operations team can practice.
4. Live Database: The final destination.

Using a Test Database is crucial not only for validating numbers but also for testing processes. For example, the trial balance might match perfectly (Data Verification). Still, if you attempt to process a move-out refund and the system fails due to a missing link to the vendor file, your data is unusable. Always test the use of the data, not just the data itself.

Every successful migration requires a "Go-Dark" or "Blackout" period, a few days when no entries are made in either the old or new system. This ensures that the data you extract is static and matches the final trial balance.

Things to Look Out For:

• Communication: Inform your Accounts Payable and Leasing teams well in advance. If they enter a new lease during the blackout, it may be lost.
• Licensing: Before you start, verify that your current Yardi or MRI license count supports the new units. You don’t want to hit a system limit during the conversion weekend!
• Cut-Offs: Plan for multiple cut-offs. For example, you might stop AP processing on Wednesday, but allow rent receipts until Friday.

There is an old saying in data science: "Garbage in, garbage out." If the legacy system has duplicate vendor records, expired lease charges that remain active, or messy "Management Lost" notes, those errors will carry over into your new ERP.

We recommend performing a data health check before the extraction begins. Look for:

• Duplicate tenant records.
• Inconsistent address formats (e.g., "St." vs. "Street").
• Negative deposit balances that should have been written off.

Cleaning data in the legacy system is often easier than fixing it after import.

Onboarding new properties is a significant effort that requires coordination among the client, the software vendor, and the implementation team. As our case studies show, even projects with compressed timelines shrinking from 12 months to 4 months can be successful with the right automation and rigorous testing.

At Assetsoft, we specialize in taking the stress out of data conversion. Whether you are implementing a new instance of Yardi Voyager or scaling up your MRI Software environment, we act as your strategic technology partner to ensure your data arrives clean, accurate, and ready for business.

Ready to streamline your next property onboarding? Contact Assetsoft today to discuss your data migration strategy.

Q: What is the Rent Increase Guideline for 2026?

A: The Ontario government has set the 2026 Rent Increase Guideline at 2.1%.

This applies to rent increases taking effect between January 1, 2026, and December 31, 2026.

Q: Does this apply to all my units?

A: No. The most critical "switch" in your property management software this year is the New Build Exemption.

Units that were first occupied for residential purposes after November 15, 2018, are exempt from the 2.1% cap. For these units, you may increase the rent by any amount, provided you still give proper notice.

Q: What are the notice requirements?

A: You must provide 90 days’ written notice using the official Form N1 (for guideline increases) or Form N2 (for exempt units).

• Warning: A common error is counting "3 months" instead of "90 days." If you serve notice on February 1st for a May 1st increase, you might be short on days depending on the month lengths. The RTA is strict; being one day short voids the increase.

The Ontario market operates on specific rules that generic property management software configurations often miss.

If your system isn't distinguishing between "Pre-2018" and "Post-2018" units for rent control, or if your N4 notices are still defaulting to old timelines, you are exposing your portfolio to risk.

Assetsoft is a specialized consulting firm for the real estate industry. We are experts in Yardi Voyager and MRI Software. We don't just implement software; we configure it to align with the specific laws of the jurisdictions you operate in.

We can help you:

• Audit your Rent Roll for 2026 guideline compliance.
• Configure automated N1 and N4 notices that meet LTB standards.
• Clean up your data to ensure your LTB applications are bulletproof.
• Implement mobile apps for Fire Code documentation.

Is your portfolio ready for the 2026 rules?

Contact the Assetsoft team today to ensure your technology is working as hard as you are.

In legacy versions of MRI (e.g., X.6 and earlier), customizing a page often means writing SQL queries and expressions directly in the Web Design tool. While flexible, this approach lacked structure and security.

With Upgrade X.7, MRI has introduced an API-first architecture. Logic Builder allows developers to write APIs in a new internal language called Via. This language acts as a bridge, combining the logic of languages such as JavaScript or C# with the data retrieval capabilities of SQL.

When a user interacts with a page in Platform X, the page doesn't touch the database directly. Instead, it calls a Logic Builder API. This API handles the request, communicates with the database, and returns a structured result.

Based on the latest developer showcases, Logic Builder introduces several critical features that modernize how customizations are built:

1. Enhanced Security and Parameterization

The most significant improvement in Logic Builder is security. Legacy string literals are replaced with parameterization. In the past, developers might have hard-coded variables into SQL strings, leaving systems vulnerable to SQL injection.

Logic Builder enforces the use of parameters (e.g., @BuildingID or @LeaseID). This provides built-in table-level security and field-length validation, ensuring data is sanitized and safe before it interacts with the database.

2. Type Safety and Result Definitions

Logic Builder introduces Type Safety. The system creates a contract between the API and the page. You must explicitly define your data types: Strings, Integers, Booleans (Bit), or Dates.

Furthermore, the Result Type Definition feature requires developers to define the exact structure of the data returned from the API. This eliminates the guessing game; when Page Builder calls an API, it knows precisely what columns and data types to expect in return.

3. SQL Abstraction and the "Via" Language

For those who know SQL, the transition to Logic Builder is intuitive. The tool uses SQL Abstraction, which handles the heavy lifting of syntax details and best practices.

You can declare variables and write queries that look very similar to standard SQL (e.g., SELECT * FROM LEASE WHERE...), but they are wrapped in the Via language syntax. This enables powerful Control Flow features that were difficult in legacy tools, including loops, complex conditional execution, transaction controls, and exception handling (try/catch blocks).

Logic Builder lives within the new Application Studio interface (which, developers will be happy to note, comes in Dark Mode). The interface is organized with folder structures for modules and color-coded syntax highlighting to make coding easier.

Perhaps the most impressive feature for teams upgrading to X.7 is the integration between Page Builder and Logic Builder.

In a recent demonstration, MRI developers showed "the easy way" to build an API. Instead of writing code from scratch, Logic Builder includes an Import feature. You can select a page you have already built in Page Builder, and Logic Builder will scan the page for data requests. It then auto-generates the API shell, including all necessary input parameters and output definitions. This drastically reduces development time and human error.

One of the biggest challenges in software upgrades is maintaining customizations without breaking the core product. Logic Builder addresses this with robust Version Management.

In Upgrade X.7, you can view the core MRI (system) version of an API alongside your custom "Client" version. If you need to add a custom field or change logic, you create a client version of the API. You can then toggle which version the system uses as the default. This ensures that your customizations are separated from the core code, making future upgrades significantly smoother.

Logic Builder is more than just a scripting tool; it is the backbone of the modern MRI Software ecosystem. By moving to an API-based architecture, Upgrade X.7 provides a more secure, maintainable, and scalable platform.

For organizations looking to get the most out of MRI Software Upgrade X.7, understanding Logic Builder is essential. It empowers your team to build sophisticated, secure, and robust business logic that delivers a seamless experience for your end users.

Are you preparing for the significant upgrade to MRI Property Management? Ensure your team is ready for the shift to Logic Builder and Platform X.

Q: What is the Rent Increase Guideline for 2026?

A: The Government of Ontario has set the Rent Increase Guideline for 2026 at 2.1%.

This applies to rent increases taking effect between January 1, 2026, and December 31, 2026.

Q: Does this apply to all my units?

A: No. The most critical data distinction in your system this year is the identification of the New Build Exemption.

Units first occupied for residential purposes after November 15, 2018, are exempt from the 2.1% cap. For these units, you may increase the rent by any amount to align with market rates, provided you serve the correct form (Form N2) with the standard 90 days' notice222.

Q: Can Yardi automate these different increases?

A: Absolutely. The standard CRRM Rent Control function allows for different increase types, but relying on manual selection is a risk.

The Problem with Generic Configurations:

Most out-of-the-box Yardi setups require users to select "Form N2" for newer units manually. This creates a significant risk: if a property manager accidentally generates a standard N1 for a new unit, you are legally bound to the 2.1% cap, potentially losing thousands in revenue.

How Assetsoft Optimizes This:

We don't leave it to chance. We configure your CRRM logic to automatically distinguish between your capped assets and your exempt "New Build" assets.

• Automated Form Selection: We ensure your system is set up to trigger Form N2 (Exempt) for eligible units and Form N1 (Guideline Cap) for older stock automatically.
• Efficiency: We configure the batch generation process so your leasing team can produce a PDF bundle and email hundreds of N1 and N2 notices with a single click, ensuring they hit the 90-day window every time.

Q: Is it true that eviction notices for non-payment are faster in 2026?

A: Yes. Under the Fighting Delays Building Faster Act (Bill 60), the timeline for non-payment of rent has tightened.

Previously, landlords often had to provide a 14-day termination notice. New provisions allow landlords to serve an N4 notice with a 7-day termination date for unpaid rent in specific scenarios.

Q: What is the "50% Rule" for hearings?

A: This is a procedural change designed to reduce delays at the Landlord and Tenant Board (LTB).

In 2026, if a tenant wishes to raise maintenance issues as a defence during a rent arrears hearing, they are generally required to pay 50% of the alleged arrears into the Board’s trust before their arguments are heard.

Q: How does this impact my Yardi configuration?

A: Speed is irrelevant if your notices are inaccurate. The LTB will issue an N4 if the arrears amount includes non-rent charges (such as NSF fees or key deposits).

How Assetsoft Optimizes This:

We utilize Yardi’s standard Termination Worksheets to ensure your N4S are bulletproof.

• Ledger Hygiene: We audit your charge codes to ensure "Rent" is strictly separated from "Other Charges." This ensures that when Voyager pulls the Form N4 balance, it retrieves only the legally enforceable rent arrears.
• Automated Triggers: Where standard functionality needs a boost, we can implement efficient triggers that alert your collections team the moment a tenant crosses a specific arrears threshold, prompting the immediate generation of the N4.

Q: Can I stop a tenant from installing a window A/C unit?

A: Generally, no. Under Bill 97 updates, tenants have the right to install air conditioning, but they have new protections regarding safety and costs. If electricity is included in the rent, you are permitted to charge a seasonal rent increase based on the actual or estimated cost of power.

Q: What are the new rules for "Renovictions" (Form N13)?

A: If you need a unit vacant for extensive renovations, you can no longer state that work is required. You must provide a report from a qualified person (engineer or architect) confirming the vacancy is necessary.

Q: How do we track these documents in Yardi?

A: Managing N13s is a high-risk activity. Losing the engineer’s report or failing to track the "Right of First Refusal" (the tenant’s right of return) can result in substantial fines.

How Assetsoft Optimizes This:

• Seasonal Charges: We use standard Recurring Charge functionality with set "Start" and "End" dates (e.g., June–Sept) to automate A/C fees, so your team doesn't have to post them every summer manually.
• Form N13 Management: We configure the Termination Worksheets in CRRM to track your N13 notices. We can also set up custom fields or attachments to link the mandatory engineer’s report directly to the tenant record, ensuring you have a digital paper trail if challenged.

Q: What is the new Carbon Monoxide (CO) rule for 2026?

A: Effective January 1, 2026, the Ontario Fire Code mandates a working Carbon Monoxide alarm on every floor of a home, including basements and non-sleeping floors—if the house has a fuel-burning appliance or attached garage.

Q: How do I prove compliance across an extensive portfolio?

A: Liability protection requires proof. A paper checklist is often insufficient in court.

How Assetsoft Optimizes This:

We leverage Yardi Inspection Mobile to make compliance automatic for your field staff.

• Forced Workflow: We can configure inspection templates that require technicians to take a time-stamped photo of the CO alarm on every floor before they can close a "Turnover" or "Annual Inspection" work order.
• Dashboarding: We build custom SQL-based dashboards on your Voyager home screen that flag any unit missing a validated CO check in the last 12 months, allowing you to be proactive rather than reactive.

Many consulting firms can install software. Assetsoft understands the ecosystem behind it.

Our team has a unique history with this technology. We were involved in the development of many of the Canadian Residential modules. We understand the CRRM (Canadian Residential Regional Module) architecture, as we helped define how it addresses Canadian-specific requirements, including N1, N4, and LTB reporting.

Our Philosophy: Standard First, Custom When Needed

We believe in using Yardi Voyager's robust, standard functionality whenever possible to ensure seamless upgrades and stability. However, the Ontario market is complex. When standard features aren't enough to meet your specific operational goals, we have the expertise to build efficient custom triggers and stored procedures that bridge the gap without "breaking" your core system.

We can help you:

• Configure CRRM to automate your 2026 N1/N2 rent increases.
• Audit your data to ensure N4s and LTB applications are valid.
• Implement Mobile Inspections for seamless Fire Code compliance.
• Streamline Reporting for clearer visibility into arrears and vacancies.

Is your Yardi environment working as hard as you are?

Contact the Assetsoft team today to ensure your technology is ready for 2026.

The primary drivers of Report Builder are accessibility and modernization. For years, users were tethered to Windows environments to design reports, checks, and statements. The goal of MRI Platform X is to free users from these constraints by moving operations entirely online.

Report Builder performs a "lift and shift" of the core concepts you know from Report Design but "webifies" them. This means you don't have to relearn how to build a report from scratch. If you’ve used Report Design for the last 25 years, Report Builder will feel remarkably familiar, yet significantly more powerful.

While the core logic remains consistent, Report Builder introduces several quality-of-life improvements that address long-standing user pain points.

1. No More Squinting: A Zoomable Interface

One of the most frequent complaints about the legacy Report Design tool was the small font size and inability to scale the view. Report Builder addresses this with a native web interface that lets you zoom in and out effortlessly. Whether you are working on a complex financial statement or a simple rent roll, you can finally see what you are doing without straining your eyes.

2. Unified Design Environment

Previously, designing different outputs required opening different tools: Report Design for reports, Check Design for checks, and Statement Design for statements. Report Builder consolidates all three into a single, unified interface. You can create and edit reports, financial statements, and check layouts from a single menu, streamlining your workflow.

3. Automatic Web Enablement

In the old workflow, building a report was a two-step process: design it in the Windows tool, then jump into Web Design to "web enable" it so other users could run it. Report Builder eliminates this friction. When you create a report now, it is automatically web-enabled by default. This saves time and removes a tedious step from the deployment process.

4. Persistent Property Dialogues

If you’ve ever lost your properties window behind your main report screen in the old tool, you know the frustration of toggling views to find it again. Report Builder features docked dialogue boxes for Fields and Properties that never get lost behind your canvas. You can toggle them on or off, but they stay accessible, improving the design ergonomics.

A significant concern with any software migration is the fear of losing legacy work. The MRI product team has ensured that Report Builder is fully compatible with existing work.

• Shared Repository: Files saved in Report Design are accessible in Report Builder, and vice versa. They pull from the exact location in the database (MRI_RPTS and MRI_RPTP tables).
• Legacy Functions: All the familiar expressions and functions you used in Report Design (like Annual for annualizing amounts based on frequency) work the same way in the web version.
• Table Access: Just like its predecessor, Report Builder gives you direct access to every table in the PMX database, including custom tables you may have created.

The transition to the MRI Platform X Report Builder represents a significant leap forward in usability and accessibility. By moving critical reporting functions to the web, MRI provides a more flexible and modern environment that honours the deep functionality of the past while embracing the convenience of the cloud.

If you are currently licensed for Report Design, you automatically have access to Report Builder. It’s time to stop squinting at your desktop and start building in the browser.

Before a shovel hits the ground, the architect acts as the translator of the client’s vision into a language the contractor can speak.

• Existing Conditions & Field Measuring: The process often begins with field measuring to document the existing space. Accurate drawings of current conditions are the foundation for everything that follows.
• The Design Phases:
• Schematic Design: Establishing the general scope and conceptual design.
• Design Development: Expanding concepts into detailed drawings that show correct room sizes, shapes, and material specifications.
• Construction Documents: This is the critical hand-off. The architect prepares detailed working drawings and specifications that the Contractor uses to establish costs and physically build the project. These documents effectively become part of the construction contract.

The Assetsoft Edge:Transitioning from CAD to BIM (Building Information Modeling) enables architects to provide GCs with a 3D model rather than just 2D lines. Assetsoft helps firms implement BIM standards that reduce clashes before they reach the field.

Finding the right builder is an art in itself. Architectural firms often assist the Owner during the bidding phase.

• Bid Packages: Architects can prepare bidding documents, invitations to bid, and instructions to bidders.
• Contract Support: They help outline the conditions of the contract and the form of agreement between the Owner and the Contractor.

Once construction begins, the architect doesn't disappear. They enter the Construction Administration phase, serving as observers and advisors.

• Site Visits: The architect visits the site to observe progress and determine if the project is being built according to plans and specifications.
• Financial Oversight: They often review and approve the Contractor's applications for payment to ensure billing matches the work completed.
• Change Orders: When plans change (as they always do), the architect processes change orders to keep the project moving and the owner informed.

The Assetsoft Edge:Mobile project management tools allow architects to log site reports, approve payments, and issue RFI (Request for Information) responses instantly from the field. Assetsoft integrates these tools to minimize downtime for the GC.

One of the most technical services provided is Shop Drawing Review. While architects give the "big picture" design, contractors and manufacturers produce shop drawings to explain the fabrication and installation of specific items.

• Fabrication Details: These drawings cover pre-fabricated components like trusses, cabinetry, millwork, windows, and elevators.
• MEP Coordination: Critical reviews are performed for mechanical, electrical, and plumbing trades, such as ductwork and fire protection piping.
• Design Intent: The architect reviews these detailed manufacturer drawings to ensure they integrate correctly with the overall design, bridging the gap between a design concept and a manufactured reality.

Contractors cannot build without permission. Architects often shoulder the burden of expediting the preparation of the necessary applications for filing with local municipalities.

• Code Compliance: Architects verify that designs comply with building codes.
• Permit Management: They manage the flow of paperwork, securing the approvals required for the GC to operate legally.

The list of services above represents a massive amount of data, communication, and coordination. If manual processes bog down an architectural firm, the General Contractor waits, and in construction, time is money.

Assetsoft acts as a consulting partner to architectural firms, helping them adopt the technologies that streamline these exact services:

• Automated Workflow Implementation: We help automate the RFI and Submittal review process, cutting down turnaround times for Shop Drawings.
• Project Management Systems: We implement and train teams on software that keeps construction documents, change orders, and payment applications in one synchronized cloud environment.
• Data-Driven Design: We assist in setting up systems where "Existing Conditions" and "As-Built" data are captured using laser scanning and point clouds, reducing errors for the GC.

The construction industry continues to experience rapid growth, with an increasing demand for modern technology solutions. Whether you're overseeing a tenant improvement buildout, a significant renovation, or new construction, the number of variables you need to track grows quickly. Material procurement, labor scheduling, permit approvals, budget constraints, and stakeholder communications all compete for your attention simultaneously.

Without proper project management infrastructure, delays cascade, costs overrun, and communication breaks down. This is where Zoho Projects transforms how property managers approach construction and renovation work.

Construction projects are inherently sequential. You cannot paint walls before drywall is complete, and the electrical rough-in must happen before insulation. Zoho Projects' Gantt charts allow you to visualize every phase, set task dependencies, and immediately see how delays in one area ripple through your entire timeline. The baseline feature lets you compare current progress against your original schedule, keeping everyone accountable.

Budget Tracking and Cost Management

Construction budgets are notoriously difficult to control. Zoho Projects enables you to set project budgets, choose billing methods based on staff hours or project milestones, and track spending in real time. Built-in alerts notify you when costs approach or exceed predetermined thresholds, enabling proactive decisions rather than discovering overruns after the fact.

Resource and Materials Management

Managing equipment, machinery, and construction materials requires careful tracking. Zoho Projects lets you add building resources, categorize them appropriately, and ensure supplies are available when needed. The digital inventory system reduces human error and prevents costly delays when critical materials are unavailable at job sites.

Document Management and Compliance

Construction projects generate extensive documentation, including permits, blueprints, contracts, inspection reports, change orders, and safety records. Zoho Projects provides centralized cloud storage accessible to all stakeholders. Version control ensures everyone works from the latest information, while role-based access controls keep sensitive documents secure.

Property management organizations worldwide have transformed their operations using Zoho's ecosystem. Prime Property Care, a London-based HMO management company, doubled its property portfolio without adding staff by building unified workflows on Zoho Creator. Their administrative time for room marketing and tenant onboarding dropped by 80 percent.

Similarly, PropertyAngel in Bangalore automated its entire backend operations using Zoho Creator, saving an estimated $500,000 compared to building custom solutions from scratch. These implementations demonstrate how the Zoho ecosystem scales from simple project tracking to comprehensive business automation.

For construction-specific implementations, organizations have integrated Zoho Books with Zoho Projects to track construction finances alongside project milestones. This integration provides real-time insights into project progress and financial performance, enabling better decision-making throughout the construction lifecycle.

Construction projects involve diverse stakeholders: project managers, contractors, subcontractors, architects, inspectors, and property owners. Zoho Projects reduces the communication burden on managers by enabling direct communication with the workforce. Quick announcements, site photo sharing, RFI submissions, and feedback happen instantly through the platform.

The issue management features help teams catch defects earlier, before they require expensive revisions. When someone logs an issue, the system can automatically trigger predefined corrective workflows, ensuring nothing falls through the cracks.

Zoho Projects integrates seamlessly with other Zoho applications and third-party tools. Connect with Zoho CRM to map construction contracts to relevant projects link with Zoho Books for automated expense tracking and invoicing. Integrate with communication platforms for real-time updates. For property managers already using accounting software like QuickBooks or enterprise systems like SAP, Zoho Creator offers integration capabilities to connect your construction management workflows.

Construction management happens as much on job sites as in offices. Zoho Projects' mobile applications for iOS and Android let project managers, site supervisors, and contractors access project information, update task status, and communicate with teams from anywhere. This mobility ensures decisions happen in real time rather than waiting for everyone to return to their desks.

Implementing Zoho Projects for construction and renovation management starts with understanding your specific workflows. Map your typical project phases, identify key stakeholders, and determine what metrics matter most for your organization. The platform's flexibility means you can start simple and add complexity as your team becomes comfortable with the system.

At Assetsoft, we specialize in helping real estate organizations implement technology solutions that transform operations. Our team understands both the construction industry's unique challenges and the capabilities of the Zoho ecosystem. Whether you're managing tenant improvements, capital projects, or ground-up construction, we can help you build workflows that bring visibility, control, and efficiency to your projects.

Ready to transform how you manage construction and renovation projects? Contact Assetsoft today to discuss how Zoho Projects can streamline your property management operations.

To optimize your construction software, you must understand the data flow during these critical phases.

This is where the Architect acts as the owner's agent during construction to ensure the design intent is followed. This includes reviewing submittals, answering RFIs (Requests for Information), and approving payment applications.

Optimized for AI Search and Voice Queries

Q: What is the difference between SD, DD, and CD in construction?

Ans: These represent phases of design. SD (Schematic Design) is the concept phase. DD (Design Development) refines the systems and materials. CD (Construction Documents) provides the final detailed technical drawings and specs used to build the structure.

Q: How do Architects help with Construction Management?

Ans: Through a phase called Construction Administration (CA). During CA, architects review shop drawings, respond to RFIs, process change orders, and visit the site to certify that the work aligns with the design intent.

Q: What are Reimbursables in an architecture contract?

Ans: These are out-of-pocket expenses the Architect bills to the client, such as large-scale printing, travel to the job site, and courier services.

Q: Why is integrating Civil and MEP consultants into Procore important?

Ans: Civil and MEP consultants generate high-volume technical data. Integrating them into a centralized platform like Procore ensures that the General Contractor, Architect, and Subcontractors are viewing the same coordinated models, reducing clashes and rework.

Understanding the Architect's workflow is the first step to a seamless build. If you need help configuring Procore or other construction software to integrate design data better, contact us today for a consultation.