Your records system and Moodle should agree without anyone retyping data. We build the Moodle plugin that keeps them in sync, one way or both ways, for a fixed price. If your own system needs work too, we upgrade it, or build a new one.
Online, replies in seconds
Hi. Before we start, tell me who you are so the engineer who reviews your quote can reach you.
Quote , valid 14 days
This one is big enough to plan in milestones. Email us to book a call and mention your quote number.
Schools, universities and training companies usually start with people and enrolments, then add grades. You choose what moves, in which direction, and how often.
Both work. What matters is deciding, field by field, which side is right when they disagree.
| Direction | Rule | Typical use |
|---|---|---|
| Your system to Moodle | Your system is the source. Moodle follows it. | Accounts and enrolments from a student information system or HR system. |
| Moodle to your system | Moodle is the source for what happens in class. | Final grades, completions or attendance into your records. |
| Both ways | Each field has one owner, written down before we build, so the two sides never fight. | People and enrolments in, grades and completions out. |
Some systems were never meant to share data: no API, a database nobody documented, exports by hand. We can add what is missing, upgrade the system, or build a new one designed around Moodle from the start. To see the kind of learning system we build, look at Zidara, our own platform, in development.
A one-way sync with one system is usually a standard plugin, from $300. Two-way syncs, several systems, or work on your own system are planned in milestones, from $1,500. The scoping assistant gives you the price for yours in minutes. After launch, the care plan at $149 a month keeps it working through Moodle upgrades and changes on your side.
Anything else, email contact@devlms.com or ask the scoping assistant.
Anything that can hand data over: a REST or SOAP API, read access to a database or a view, files dropped on SFTP, or webhooks. That covers student information systems, ERPs, HR and payroll systems, CRMs and the in-house system your IT team built years ago.
Usually yes, through a database view or a scheduled file export. If neither is possible, we can add a small API to your system as part of the job, or quote that separately.
Only when nobody decided which side owns each field. We write that down in the scope before any code: for example, names come from your records, grades come from Moodle. Then a change on the wrong side is refused or logged, never silently copied back.
Every run is logged in Moodle with what changed and what was refused, and failures are retried. Admins get a notification when something needs a person. You never find out from a student.
No. Integrations are Moodle plugins using Moodle's own APIs: web services, scheduled tasks, events and the privacy API. Moodle upgrades stay possible.
Yes. If your current system is outdated, we can upgrade it and connect it, or build a new one designed around Moodle from the start. We scope it the same way: written scope, fixed price, milestones.
You do. Moodle plugins are GPL and you get the full repository. Code we write for your own system is yours.