Choosing M-Files is the easy part. Getting it implemented properly is where most organisations stumble.
Across New Zealand, businesses are moving away from chaotic shared drives, overloaded OneDrive folders, and paper-based systems. They know they need better document management. Many have already picked M-Files as their platform of choice.
But here’s the problem: implementing M-Files isn’t like installing software on your laptop. It’s not a plug-and-play solution. Done badly, you’ll end up with a system nobody uses, metadata structures that don’t make sense, and migration headaches that drag on for months.
Done right, M-Files transforms how your team works. Documents become instantly findable. Compliance becomes automatic. Processes that used to take days happen in minutes.
At DocSmart, we’re New Zealand’s exclusive Premier Elite Reseller for M-Files and APAC Partner of the Year. We’ve implemented M-Files for councils, engineering firms, law practices, construction companies, and government agencies across the country. We’ve seen what works, and more importantly, what doesn’t.
This guide walks you through what M-Files implementation actually involves, the common mistakes to avoid, and why your choice of implementation partner matters more than the software itself.
Table of Contents
M-Files implementation isn’t just about installing software. It’s about redesigning how your organisation stores, finds, and uses information.
The process typically unfolds in five distinct phases, each requiring careful planning and expertise.
Before any software gets installed, we need to understand how your business actually works. This means interviewing stakeholders, mapping existing workflows, and identifying pain points.
For a typical NZ engineering firm, this might involve understanding how drawings get versioned, how RFIs are tracked, and how site documentation flows between field teams and the office. For a law firm, it’s about client matter management, document retention rules, and conflicts checking.
Every organisation is different. Cookie-cutter approaches fail because they ignore the nuances of how your team actually operates.
This is where metadata structures get built, document classes get defined, and workflows get mapped. It’s the most critical phase of any M-Files implementation.
Your implementation partner should be designing a system that matches how your team thinks, not forcing you to adapt to some generic template. If someone’s trying to sell you an out-of-the-box solution without understanding your specific needs, walk away.
Configuration includes setting up security permissions, defining naming conventions, creating templates, and building the rules that will automate your processes.
Bringing your documents into M-Files doesn’t always require a full migration. One of the key advantages of M-Files is its ability to connect to existing systems like SharePoint, network folders, Google Drive, and Microsoft Teams, allowing your information to stay where it is while being organised through a smarter interface.
Where migration is the best option, it becomes an opportunity to improve how your information is structured. Documents can be organised with meaningful metadata, duplicates reduced, and version history maintained, creating a more efficient and reliable system.
Whether it’s connecting, migrating, or a mix of both, DocSmart ensures this phase is handled smoothly and strategically, setting your business up for long-term success without unnecessary disruption.
Before going live, the system needs thorough testing. This isn’t just checking that buttons work. It’s about making sure workflows actually flow, permissions are correctly applied, and the system behaves the way users expect.
User acceptance testing involves getting real team members to try real tasks. If they’re confused or frustrated, you fix it now, not after launch.
Even the best-designed system fails if users don’t understand it. Training needs to be role-specific, hands-on, and ongoing.
For a construction firm, site managers need different training than estimators. For a council, planning staff have different needs than finance teams. Generic training sessions don’t cut it.
Go-live support means having experts available when questions arise, issues surface, or confusion sets in. The first few weeks determine whether adoption succeeds or fails.
Successful M-Files implementations come down to getting the foundations right. Here are the most common mistakes, and how to avoid them.
M-Files isn’t Microsoft Word. You can’t just install it and expect people to figure it out.
Implementation is a change management project, not an IT project. It requires process redesign, stakeholder buy-in, and a clear understanding of how information flows through your organisation.
Organisations that treat this as purely technical work end up with systems that technically function but practically fail.
Metadata is the backbone of M-Files. It’s what makes documents findable, workflows possible, and compliance automatic.
Some organisations rush through metadata design, throwing together a structure based on folder names. This creates chaos. Documents can’t be found. Searches return useless results. Users give up and go back to shared drives.
Good metadata design takes time. It requires understanding how your team thinks about documents, what information matters for retrieval, and how content gets used across different departments.
Your shared drives are probably full of rubbish. Old versions, duplicate files, personal folders, and documents nobody’s looked at in years.
Migrating all of this into M-Files just moves the problem. You end up with a cluttered system that’s hard to search and expensive to maintain.
Smart organisations use implementation as an opportunity to clean house. Archive what’s required for compliance, delete what’s genuinely useless, and migrate only what matters.
A two-hour training session doesn’t create confident users. It creates people who nod politely, then email documents as attachments because they don’t really understand the new system.
Effective training is ongoing, role-specific, and includes real scenarios from your organisation. It also includes quick-reference guides, video tutorials, and readily available support.
The cheapest quote often comes from providers who don’t understand what proper implementation requires. They’ll get the software installed, hand you some generic documentation, and disappear.
You’ll spend more fixing the problems than you would have spent hiring competent partners in the first place. As the saying goes, buy cheap, buy twice.
Moving from shared drives or legacy document management systems into M-Files is where theory meets reality. It’s complex, time-consuming, and absolutely critical to get right.
Let’s talk about what this actually involves, using real scenarios from New Zealand organisations we’ve worked with.
Most NZ businesses are migrating from one of three scenarios. Either they’re on traditional network drives (the classic S:\ drive setup), they’re using SharePoint in a fairly basic way, or they’ve got some legacy system that’s limping along.
Network drives are the Wild West. Folders nested ten levels deep, files named “Final_FINAL_v3_USE_THIS.docx”, and nobody quite sure who has access to what. There’s usually no version control, no audit trail, and permissions that have accumulated like barnacles over years.
SharePoint implementations often aren’t much better. They start with good intentions but devolve into sprawling site collections, broken links, and metadata fields nobody fills out. Teams end up treating it like a glorified network drives.
Legacy systems vary, but they’re usually rigid, slow, and expensive to maintain. Staff have developed elaborate workarounds. Critical information lives in personal folders because the official system is too painful to use.
There’s no magic button that cleanly moves everything into M-Files. Every migration is custom work.
The first step is analysis. We use tools to scan your existing repositories, map out what you’ve got, identify duplicates, and flag potential issues. This analysis reveals the scale of the problem and informs the cleanup strategy.
Next comes cleanup. This is where organisations make hard decisions. What gets migrated as active content? What gets archived? What gets deleted?
For most organisations, we recommend a phased approach. Active projects and current matters get migrated first, with full metadata applied. Historical information gets archived in a read-only format. Truly obsolete content gets binned.
The actual migration involves mapping old folder structures to new metadata schemes, applying document classes, and preserving version histories where they exist. It’s meticulous work.
If your current system has proper version control (rare with network drives, common with SharePoint or legacy systems), that history should be preserved during migration.
M-Files handles versioning beautifully, but getting historical versions into the system requires careful technical work. Each version needs metadata applied, relationships maintained, and audit trails preserved.
For network drives migrations where version control doesn’t exist, we often find multiple files representing different versions. These need to be identified, consolidated, and properly versioned in M-Files.
Your old folder permissions need to translate into M-Files security structures. This isn’t a direct mapping. M-Files uses metadata-based security, which is far more flexible than folder permissions but requires thoughtful design.
We often find that old permission structures are overly complex, accumulated through years of ad-hoc access grants. Implementation is an opportunity to simplify, using role-based access that makes sense for how your business actually operates.
Security should be tied to document properties, not arbitrary folder locations. A contract should be accessible based on who’s involved in that deal, not which folder someone remembered to put it in.
Change is hard. People are comfortable with shared drives, no matter how frustrating they actually are.
Clear communication throughout the migration process is essential. Users need to know what’s happening, when it’s happening, and how it affects their daily work. They need reassurance that nothing will be lost and that the new system will genuinely make their lives easier.
Involving key users early, getting their input on metadata design and workflows, builds buy-in. When users feel ownership of the new system, adoption follows naturally.
Metadata is the secret sauce that makes M-Files powerful. It’s also where most implementations succeed or fail. Think of metadata as the filing system inside your brain. When you remember a document, you don’t think about its folder path.
You think about what it is (a contract), who it involves (that Wellington client), and when it matters (current project). That’s how M-Files works. Documents are found based on properties, not locations.
Get the metadata right and finding documents becomes instant. Get it wrong and you’ve just built an expensive maze.
M-Files uses several metadata concepts that work together: document classes, properties, value lists, and relationships.
Document classes define types of content. A contract is different from an invoice, which is different from a technical drawing. Each class has specific properties that make sense for that content type.
Properties are the attributes that describe documents. Client name, project code, document status, approval date. These need to be carefully chosen based on how your organisation actually searches for and uses information.
Value lists control what can be entered in properties. Instead of free text where everyone spells client names differently, you have a controlled list. This ensures consistency and makes searching reliable.
Relationships connect documents to other objects. A contract might be related to a client, a project, and multiple correspondence items. These relationships create a web of information that mirrors how your business actually works.
The best metadata schemes are invisible. Users shouldn’t think about filling out forms. The system should capture information naturally as part of existing workflows.
This means keeping mandatory properties to a minimum. If users face a wall of required fields every time they save a document, they’ll find workarounds.
Smart metadata design uses intelligent defaults, auto-population where possible, and progressive disclosure. Users see only the fields relevant to the document type and context.
For example, when creating a new contract in M-Files, the client property might auto-populate based on which project workspace you’re in. The contract type might limit available approval workflows. The system guides users without nagging them.
Governance in M-Files means defining rules about how documents move through their lifecycle. What needs approval? Who can access what? When should something be archived?
These rules get built into the system as automated workflows. A new contract automatically routes to the legal team for review. An invoice over a certain threshold requires additional approval. A completed project document automatically changes status and security settings.
Workflow automation removes the manual coordination that eats up admin time. Instead of emailing people asking for sign-off, the system automatically presents them with pending approvals in their queue.
For compliance-heavy industries like local government, engineering, or legal, these workflows ensure that required processes always get followed. Nothing falls through the cracks because someone forgot or was on leave.
There’s a tension in metadata design between having enough structure to ensure findability and allowing enough flexibility for edge cases.
Over-structure the system and users feel constrained. They can’t handle unusual documents or new project types without calling IT. The system becomes rigid and frustrating.
Under-structure it and you’ve just recreated the shared drive problem. Documents lack consistent properties, searches return inconsistent results, and compliance is guesswork.
Good metadata design finds the middle ground. It provides clear structures for common document types while allowing flexibility where needed. It can evolve as the business changes without requiring complete redesign.
Metadata isn’t set and forget. As your business evolves, your metadata structures need to evolve too.
New project types emerge. Regulations change. Organisational structures shift. Your M-Files system needs governance processes that allow controlled evolution.
This means having clear ownership of metadata standards, regular reviews of value lists, and processes for requesting new document classes or properties. It means training new staff on metadata principles, not just button-clicking.
Organisations that treat metadata as living infrastructure keep their M-Files systems useful and relevant. Those that set it once and ignore it end up with systems that slowly decay into irrelevance.
Think of M-Files as the structured content layer and Microsoft 365 as the collaboration and communication layer. They complement each other beautifully when integrated properly.
Documents stored in M-Files can be edited directly in Microsoft 365 apps. Users work in familiar Word, Excel, or PowerPoint while M-Files handles version control, metadata, and compliance in the background.
Email attachments can be saved directly into M-Files from Outlook. This captures critical correspondence alongside related documents, creating complete context. No more hunting through email folders trying to find that important attachment.
Teams channels can be connected to M-Files vaults, allowing collaborative work in Teams while maintaining formal document management in M-Files. It’s the best of both worlds.
Many organisations worry that implementing M-Files means abandoning SharePoint. Not true. They actually work together extremely well.
SharePoint excels at internal wikis, team sites, and lightweight collaboration. M-Files excels at structured document management, version control, and compliance. Use each for what it does best.
The M-Files SharePoint connector allows seamless movement between systems. Content can be promoted from SharePoint to M-Files when it needs formal management. M-Files can also be embedded within SharePoint environments, allowing teams to access and work with information through a familiar interface while keeping documents managed and governed in M-Files.
For more detail on this integration, see our article on why M-Files and SharePoint work better together.
Microsoft Teams has become the collaboration hub for many Kiwi organisations. M-Files integration brings document management into this environment.
Teams channels can be linked to M-Files views or workspaces. Team members access documents through Teams, work collaboratively, and M-Files handles the formal version control behind the scenes.
This means teams can chat, meet, and collaborate in Teams while maintaining proper document governance through M-Files. It removes the friction that often kills document management adoption.
Here’s an uncomfortable truth: M-Files is brilliant software, but brilliant software poorly implemented is worthless.
Your implementation partner determines whether M-Files becomes a productivity engine or an expensive mistake. Price matters, but capability, experience, and ongoing support matter far more.
Good M-Files partners have deep experience across multiple industries. They’ve solved similar problems before. They know the common pitfalls and how to avoid them.
Poor partners treat every implementation the same. They use cookie-cutter approaches, generic templates, and minimal customisation. They view implementation as a transaction, not a relationship.
Good partners invest time in discovery. They ask probing questions, challenge assumptions, and design solutions specific to your organisation. Poor partners ask a few surface questions and start configuring based on generic best practices.
Good partners provide comprehensive training tailored to different user roles. Poor partners deliver generic training sessions that leave users confused.
Good partners offer ongoing support, system optimisation, and guidance as your needs evolve. Poor partners disappear after go-live, leaving you to figure out problems alone.
New Zealand has specific compliance requirements, business practices, and cultural expectations. International partners often lack this context.
Local councils need solutions that comply with the Public Records Act and Local Government Official Information and Meetings Act. They need retention schedules that reflect NZ regulations, not overseas assumptions.
NZ engineering firms work within regulatory frameworks specific to this country. Construction companies deal with building consent processes unique to our system.
Partners based in New Zealand understand these nuances. They’ve implemented systems for organisations like yours, facing the same compliance requirements and operational realities.
M-Files has a partner certification program. Partners earn tiers based on capability, implementation volume, and customer satisfaction.
Premier Partners represent the highest tier. They’ve demonstrated consistent excellence, completed extensive implementations, and maintain expert-level certifications.
When evaluating partners, look at their tier status. Ask about their implementation volume. Request references from similar organisations. Check how long they’ve been working with M-Files.
Also look at recognition within the M-Files ecosystem. Partners who win awards like APAC Partner of the Year have demonstrated excellence across multiple dimensions.
Implementation costs include far more than the initial setup fee. Factor in migration effort, training time, ongoing support, and the cost of getting it wrong.
A cheap implementation that requires extensive rework costs more than hiring capable partners from the start. Staff time spent wrestling with a poorly configured system represents huge hidden costs.
Good partners provide transparent pricing that reflects the actual work required. If a quote seems too cheap, it probably is. Either they’ve underestimated the work (meaning cost overruns later) or they’re planning to cut corners.
Ask potential partners to break down implementation costs. What’s included? What’s extra? What does ongoing support look like? How do they handle requests for changes or optimisations?
Implementation isn’t the end. It’s the beginning of a long-term relationship.
Your M-Files system will need ongoing optimisation. New workflows will be required as processes change. Additional integrations will make sense as technology evolves. Users will need refresher training and support.
Choose a partner who views this as a relationship, not a transaction. Someone who’s genuinely invested in your success, not just closing a deal.
The right partner becomes a trusted advisor. They help you leverage new M-Files capabilities as they’re released. They suggest optimisations based on how you’re actually using the system. They’re there when you need them.
We’re not just another M-Files reseller. We’re New Zealand’s exclusive Premier Elite Reseller and the 2025 APAC Partner of the Year.
That recognition didn’t happen by accident. It reflects years of successful implementations across New Zealand and the Pacific, consistently high customer satisfaction, and deep expertise in document management.
DocSmart holds exclusive Premier Elite Reseller status for M-Files in New Zealand. This means we’ve met M-Files’ highest standards for capability, implementation quality, and customer success.
Premier status requires maintaining expert-level certifications, completing a significant volume of successful implementations, and consistently high customer satisfaction scores.
It also means we have direct access to M-Files engineering teams, early access to new features, and priority support channels. When complex technical challenges arise, we have resources that other resellers simply don’t.
We’ve implemented M-Files for local councils managing public records, engineering firms handling complex project documentation, construction companies coordinating site information, law firms managing client matters, and government agencies meeting strict compliance requirements.
This breadth of experience means we’ve encountered and solved most problems before. We know what works in different contexts. We understand industry-specific compliance requirements.
When a council needs retention schedules that comply with the Public Records Act, we’ve done this across a range of organisations. When an engineering firm needs drawing management integrated with project workflows, we know exactly how to configure it.
DocSmart is based in New Zealand, but our standards are international. Our team holds global M-Files certifications and stays current with the latest platform developments.
Being local means we’re in your timezone, we understand your business environment, and we’re available when you need us. You’ll have a local team you can rely on. DocSmart provides hands-on support and guidance throughout your implementation, and we work closely with M-Files where needed to ensure everything runs smoothly.
We provide onsite implementation support when needed, face-to-face training, and the kind of responsive service you can’t get from international providers.
Our relationship doesn’t end at go-live. We provide ongoing support, regular system reviews, and optimisation services.
As M-Files releases new capabilities, we help you leverage them. As your business evolves, we help your system evolve too. We’re genuinely invested in your long-term success.
Many of our clients have been with us for years, continuously improving their M-Files implementations as their needs grow and change.
How long does M-Files implementation typically take in New Zealand?
Every M-Files implementation is different, depending on the size of your organisation, the complexity of your workflows, and how your existing systems are set up.
What’s most important is taking a structured approach from the start. This includes understanding your processes, designing the right solution, and ensuring everything is configured to support your team effectively.
With the right planning and guidance, implementations can be delivered smoothly and in a way that sets your business up for long-term success, without unnecessary disruption.
Who provides M-Files implementation services in New Zealand?
DocSmart is New Zealand’s exclusive Premier Elite Reseller for M-Files and the 2025 APAC Partner of the Year. We provide comprehensive implementation services including discovery, system design, migration, training, and ongoing support. Our team holds expert-level M-Files certifications and has extensive experience implementing M-Files across councils, engineering firms, construction companies, legal practices, and government agencies throughout New Zealand.
What is involved in migrating existing documents to M-Files?
Migration involves several stages: analysing existing content, cleaning up duplicates and obsolete files, designing metadata structures that make content findable, mapping old folder structures to new metadata schemes, and physically moving documents while applying appropriate metadata. Version histories need to be preserved where they exist. Permissions need to be translated to M-Files security structures. Most organisations use a phased approach, migrating active content first and archiving historical material separately. Proper migration takes time but is essential for long-term success.
Can M-Files integrate with our existing Microsoft 365 environment?
Yes, M-Files integrates deeply with Microsoft 365. Documents can be edited directly in Word, Excel, and PowerPoint while M-Files handles version control and metadata. The Outlook integration allows emails and attachments to be filed directly into M-Files. Teams integration brings document management into collaboration channels. M-Files also integrates with SharePoint, allowing both systems to work together based on their strengths. Azure Active Directory integration enables single sign-on and centralised user management.
What ongoing support does DocSmart provide after M-Files goes live?
We provide comprehensive ongoing support including technical assistance, user training refreshers, system optimisation, workflow adjustments as processes evolve, and help leveraging new M-Files capabilities as they’re released. We conduct regular system reviews to identify improvement opportunities and ensure the system continues meeting your needs. Our support team is local, responsive, and genuinely invested in your long-term success. We view implementation as the beginning of a relationship, not a transaction.
M-Files is powerful software, but power without proper implementation is potential without results.
The difference between M-Files that transforms your organisation and M-Files that sits unused comes down to implementation quality. It requires deep expertise, careful planning, thorough migration, smart metadata design, comprehensive training, and ongoing support.
DocSmart brings all of this to every implementation. We’re New Zealand’s exclusive Premier Elite Reseller, the 2025 APAC Partner of the Year, and we’ve successfully implemented M-Files for organisations across every major industry in this country.
We understand New Zealand compliance requirements, business practices, and the specific challenges Kiwi organisations face. We provide local expertise backed by international standards.
If you’re considering M-Files or struggling with an existing implementation that isn’t delivering, talk to us. We’ll help you get it right.
Contact DocSmart today to discuss your M-Files implementation needs. Let’s build a document management system that actually works for your organisation.
© 2026 DocSmart All Rights Reserved l Privacy Policy | Terms & Conditions | Web Design by Virtual Innovation