MS Project Import for Construction Apps: The 2026 Guide for Indian Sites

If your planner builds a detailed programme in Microsoft Project but your site team still runs the day on WhatsApp, Excel and a diary, you are not alone. For most Indian builders and contractors the missing link is an MS Project import construction app — something that brings the .MPP schedule into a mobile workflow without breaking dependencies, calendars, baselines or milestones.

This guide covers what "good import" actually means in 2026, how Microsoft's licensing changes affect which file you can even export, how to clean your schedule before importing, and what to validate afterwards so the programme stays alive on site.

Why MS Project import matters on Indian construction sites#

MS Project is still the default for CPM logic, baselines and client-facing Gantt charts. The problem starts when the schedule lives on one laptop, in one office, updated once a fortnight.

On typical SMB sites in India, execution actually happens through phone calls and WhatsApp groups, labour notes in a diary, Excel sheets for RA bills and material tracking, and subcontractor schedules that never match the master programme. When the plan and the field drift apart you get the same symptoms every time: surprise delays, firefighting, and "we are 90 percent done" for six weeks straight.

The macro numbers back this up. The Ministry of Statistics and Programme Implementation (MoSPI) publishes a monthly flash report on central sector projects costing Rs 150 crore and above. In the June 2026 report, 1,847 ongoing projects across 17 central ministries carried a revised cost of about Rs 40.54 lakh crore against an original sanctioned cost of Rs 35.61 lakh crore — a cumulative cost overrun of roughly Rs 4.92 lakh crore, with cumulative expenditure at about 54.18 percent of the revised cost. The May 2026 report tracked 1,987 projects, with expenditure at 51.34 percent of revised cost and only about 41 percent of projects past 80 percent physical progress.

One important caveat for anyone quoting these reports: recent editions have stopped publishing the old "delayed versus on schedule" classification that earlier reports carried, so the frequently repeated "X projects delayed, average overrun 36 months" line is no longer something the current flash report supports. Cost overrun and physical progress are the numbers you can defend today. You can check the latest edition yourself on the MoSPI publications portal.

The same gap between plan and execution shows up on a G+12 tower in Thane as on a national highway package. It is a data-flow problem, not a planning-skill problem — which is exactly what import is meant to fix. If you are still deciding how formal your programme should be, our construction project scheduling guide for India is a better starting point than jumping straight to tooling.

The 2026 licensing reality you need to plan around#

Microsoft reorganised Project under the Planner umbrella, and several dates land in 2026. This directly affects which file your consultant can hand you.

As of mid-2026, Microsoft's India pricing page lists:

Three consequences for construction teams:

1. Only Plan 3 or a perpetual Project Standard/Professional licence gives you the desktop app that can save a real .MPP or MSPDI XML file. Planner Plan 1 is web-only. If your consultant is on Plan 1, ask what they can actually export before you promise your client a Gantt.
2. Licensing every site engineer is not realistic. At Rs 2,495 per user per month, a 20-person site team is roughly Rs 6 lakh a year before GST — for people who mostly need to read the plan and update progress, not re-baseline it. That economics is the whole reason a mobile viewer and importer exists.
3. Dates to note. Planner and Project Plan 5 moved to end of sale on 1 May 2026, and Project Online retires on 30 September 2026 — Microsoft blocked creation of new Project Web App sites from 1 April 2026, and organisations are advised to export historical data before the cut-off. Project desktop, Project Server Subscription Edition and Planner itself are not affected. Microsoft's own Project Online retirement announcement has the migration guidance.

Also worth knowing: importing an .MPP into Planner Premium is not done from the Planner UI. It runs through the Power App named "Project" (Plans, then Import), which trips up a lot of teams who go looking for an Import button that is not there. Verify current terms on the Microsoft Planner plans and pricing page before you buy anything, since these SKUs have moved twice in two years.

What an MS Project import construction app should support#

Not all imports are equal. Plenty of tools import a flat task list and call it done. For construction planning that is close to useless.

File formats: .MPP vs MSPDI XML vs Excel/CSV#

• .MPP is Microsoft's native binary format. It is not publicly documented, which is why many apps cannot read it directly and instead lean on open-source parsers — the LGPL library MPXJ, for instance, reads MPP, MSPDI XML, Primavera XER and PMXML, and Asta Powerproject files.
• MSPDI XML (Save As, then XML Format) is the documented interchange format. It preserves hierarchy, links, calendars and baselines far better than a spreadsheet, and it is also the bridge most teams use when talking to Primavera P6.
• Excel/CSV is fine for a simple activity list, but you rebuild dependencies by hand.

Two quirks from Microsoft's own export documentation that bite people: you can only export the entire project to XML (no partial export, no Export Wizard mapping), and fields containing null values are omitted from the XML to keep file size down. So an empty custom field on 200 tasks simply will not appear on the other side.

Here is what typically survives each route:

WBS structure and task hierarchy#

A construction schedule needs a clean work breakdown: Project, then Building or Block, then Floor or Zone, then Trade, then Activity, with summary tasks for reporting and milestones for approvals, handovers and billing triggers. Your app should retain outline levels so a site engineer can collapse everything except the zone they are standing in. If your WBS is the weak link, start from a worked WBS example for a real building project rather than inheriting a consultant's 5,000-line file.

Logic, calendars, baselines#

At minimum the import should carry predecessors and successors, link types (FS, SS, FF, SF), and lag or lead with clear units. If dependencies break, the Gantt still looks fine but the dates stop behaving like a CPM schedule — which is worse than having no schedule, because it looks authoritative.

Calendars are where Indian projects quietly lose weeks. Your import needs to handle 6-day working weeks, site hours, national plus state plus project-specific holidays, and the seasonal blocks everyone plans around: monsoon from roughly June to September (excavation, external plaster, waterproofing, painting), the Diwali and Chhath labour migration window in October and November, and monsoon-period sand mining restrictions in several states. If the app silently falls back to a default 5-day calendar, your finish date can move by weeks without anyone noticing.

For control you also want baseline start/finish, actual start/finish, and a progress field. Many teams confuse percent complete with physical progress; the app should let you record "30 m of 100 m plaster done" instead of forcing an engineer to guess a percentage.

Pre-import checklist: clean the schedule first#

Spend 30 to 60 minutes on the file before importing. It saves days of confusion.

• Convert execution tasks to Auto Scheduled so dates recalculate correctly.
• Give every execution task a duration and at least one predecessor — no floating tasks.
• Keep summary tasks as summaries; never type manual dates on a summary row.
• Remove "Must Start On" and "Must Finish On" constraints unless the date is genuinely contractual.
• Standardise lag units (days versus hours) and delete stray negative lags.
• Confirm a single project calendar, or document the per-trade calendars.
• Rename tasks in language a site engineer uses, not consultant shorthand.
• If you are going the CSV route, check date format — India writes DD/MM/YYYY and many importers assume MM/DD/YYYY, which silently converts 05/09 into 9 May.
• Note the task count, milestone count, link count and project finish date before export. You will compare against these after import.

A practical Indian WBS backbone for an RCC residential tower: preliminaries, excavation and PCC, foundations, superstructure repeated per floor, blockwork and plaster, waterproofing, MEP rough-in, finishes, testing and commissioning, snagging and handover. That structure is what your weekly review and your next-seven-days plan will hang off.

Step by step: export from MS Project, import into your app#

Option A: MSPDI XML (best for preserving logic)#

1. Take a copy of the .MPP file so you can experiment safely.
2. File, then Save As, then choose XML Format (.xml) in the "Save as type" list. If you skip that step it just saves another .MPP.
3. In your construction app choose Import, then MS Project XML.
4. Map fields if prompted, and confirm the project calendar explicitly.
5. Validate before you tell anyone the import worked.

Option B: direct .MPP import#

If the app reads .MPP natively — SiteSetu does, keeping outline levels, dependencies and baseline dates intact — this is the shortest path and avoids the null-field trimming that XML export does. Still run the same validation pass.

Option C: Excel/CSV (simple activity lists only)#

Export with Task ID, Task Name, WBS or outline level, Duration, Start, Finish, Predecessors and Trade/Subcontractor as a minimum. Map columns carefully, then spot-check 10 to 15 linked activities by hand.

Post-import validation, in five minutes#

• Does the project finish date match MS Project exactly? If it is off by days, suspect the calendar.
• Do the task count and milestone count match your pre-export note?
• Pick three critical-path activities and check their predecessors survived, including lag.
• Do summary tasks roll up, or did they flatten into ordinary tasks?
• Are baseline dates present, or did only current dates come through?

Field mapping that works on most sites#

After import: turn the schedule into a site execution system#

Importing is step one. The value shows up when the same schedule drives the weekly look-ahead, daily progress updates with photos and quantities, issue logging for blocks and pending approvals, and civil-MEP-finishes coordination.

A cadence that works for SMB contractors:

• Saturday or Monday morning: review the next 7 to 14 days, lock priorities, confirm manpower and material.
• Daily, 10 minutes: the site engineer updates 5 to 15 active tasks — started, quantity done, blockers. Feed the same entries into your daily progress report format so you are not writing the DPR twice.
• Mid-week: adjust for reality — rain days, late deliveries, labour shortfall — and tag the reason code.

Two more things make the imported programme genuinely useful. First, tie approval and handover milestones to your billing cycle so RA bill preparation draws on the same progress data rather than a parallel Excel. Second, make sure updates work where the network does not — basements, podium levels and greenfield sites are exactly where the phone drops to Edge, so offline-capable capture is not a luxury.

Three Indian site scenarios#

G+12 RCC residential tower. The schedule repeats a floor cycle: shuttering, reinforcement, MEP sleeves, pour, de-shuttering, curing. After import, each floor becomes a WBS node and the engineer updates only the current floor. During monsoon, tag rain impact and watch which downstream activities move — plaster, waterproofing, facade. Keep milestones like "Slab cast, Floor 6" so client reviews stay objective.

Road or utility package. Most delay here comes from outside your control: utility shifting, permissions, traffic blocks, drawing approvals. Model these as explicit tasks with predecessors before export ("Utility shifting, Section A"), add "Drawing approval received" milestones, and after import record reason codes and evidence in the same system instead of scrolling WhatsApp for proof six months later.

Interior fit-out. Fast and parallel — ceilings, flooring, electrical, HVAC, painting, joinery. Use SS links where trades start in parallel after a zone handover, break work by zone (lobby, pantry, washrooms, workstations), and keep durations to 1 to 3 days so daily updates mean something.

Common import pitfalls#

• Broken dependencies. Compare key successor dates before and after, not just the task list.
• Calendar mismatch. A default 5-day calendar against a 6-day site is the single most common cause of a wrong finish date.
• Wrong date format. Validate the first few dates after any CSV import.
• Too much detail. A 5,000-line schedule paralyses site teams. Import it all, but expose a site-facing layer of milestones plus near-term activities — this is where a Gantt view built for site use beats a printed A0 sheet.
• Misleading percent complete. Prefer quantity-based progress for repetitive works: brickwork, plaster, tiling, painting.
• Unclear ownership. Add a responsible engineer or subcontractor field during import, not three weeks later.
• One-way import treated as sync. Most tools import a snapshot. Decide who owns the master programme and re-import on a defined cycle rather than assuming both sides update each other.

Where SiteSetu fits#

Most teams want to keep planning in MS Project — consultants and clients expect it — while making execution easy for site staff who will never have a Project licence.

SiteSetu sits in that middle layer: import the .MPP into a mobile-first WBS and task management module with location breakdown, then let site engineers update progress, attach photos and record blockers from the site itself, offline if needed. The goal is not to replace planning discipline. It is to close the gap between the programme on paper and the work on site — at a per-seat cost that makes sense for people who read the plan far more often than they re-baseline it.

Quick takeaway checklist#

• Confirm which Microsoft SKU your planner has before promising a file format.
• Export as MSPDI XML when direct .MPP import is not available.
• Preserve WBS, dependencies, calendars and baselines — that is the real schedule.
• Note task count, milestone count and finish date before export; verify after import.
• Pilot on one project, then roll out.
• Run a weekly look-ahead plus daily update rhythm so the programme stays current.

FAQs#

Can I import a .MPP file directly, or do I need to convert it?#

It depends on the app. Because .MPP is an undocumented binary format, many tools cannot read it and ask for MSPDI XML instead, while others use open-source parsers to read .MPP natively and keep outline levels, dependencies and baseline dates intact. Ask your vendor which of the two they support before you plan the rollout. If direct import is not available, use File, Save As, XML Format from Project desktop.

Which Microsoft licence do I need to produce a file I can import?#

You need the Project desktop app, which as of mid-2026 comes with Planner and Project Plan 3 (Rs 2,495 per user per month on India annual pricing, GST extra) or a perpetual Project Standard/Professional 2024 licence. Planner Plan 1 at Rs 830 per user per month is web and Teams only, so it cannot save a .MPP or MSPDI XML file. Verify current pricing on Microsoft's site before committing, since these SKUs have been reorganised twice recently.

Does Project Online retiring in September 2026 affect my schedules?#

Project Online retires on 30 September 2026, and new Project Web App sites could not be created from 1 April 2026. If your consultant hosts schedules there, ask them to export project data and reporting history before the deadline. Project desktop, Project Server Subscription Edition and Planner are unaffected, so desktop-produced .MPP and XML files continue to work normally.

Will my critical path stay the same after import?#

It should, provided dependencies and calendars come across correctly. The fastest check is to compare the project finish date and three critical-path activities against the original file. If the finish date has shifted by several days, the calendar is almost always the culprit — usually a 5-day default replacing a 6-day site week.

Should the site track percent complete or quantities?#

Quantities are more reliable for repetitive construction work: 120 sqm of plaster done out of 400 sqm is verifiable, 30 percent is a feeling. Use percent complete only where quantities are genuinely hard to measure, such as commissioning or approvals. Most disputes about "we are 90 percent done" disappear once progress is recorded in units someone can measure with a tape.

How do I handle monsoon and festival breaks in the imported schedule?#

Build them into the calendar as non-working periods before you export, rather than absorbing them later as slippage. Typical Indian additions are the June to September monsoon window for external and earthwork activities, the Diwali and Chhath labour migration period, and state-specific holidays. Then record actual weather and labour-availability impacts against tasks as they happen, so your delay claim has a documented trail instead of a WhatsApp thread.

If you already have schedules in MS Project, an MS Project import construction app is the fastest way to make that planning useful on site — without turning every site engineer into a scheduler, or buying them a licence they will use twice a month.