Yes, you do need to plan for real hosting needs when you propose MLSimport sites to clients. Use PHP 7.4 or newer, with PHP 8.x strongly preferred for speed and safety. Set at least 256M of PHP memory, use solid MySQL or MariaDB, and pick hosting that can run cron jobs without tiny timeouts. This gives MLSimport enough room to import thousands of MLS(Multiple Listing Service) listings, keep syncs steady, and store large wp_posts and wp_postmeta tables without choking the server.
What are the minimum hosting requirements to run MLSimport reliably?
Pick hosting that supports modern PHP, solid memory, and stable cron so listing imports run clean.
To run MLSimport well, use PHP 7.4 or higher, with PHP 8.x as the real sweet spot. The plugin supports PHP 7.0+, but newer PHP gives faster imports and better security on client sites. Your database should be MySQL or MariaDB with no tiny caps on table size, because wp_posts and wp_postmeta grow fast during imports.
MLSimport needs enough PHP memory to run bulk imports and load big admin screens without errors. A PHP memory_limit of 256M is a good baseline, and 512M is smart for big MLS boards or busy sites. Cron support on the host also matters so the plugin can run scheduled syncs and not time out after 30 seconds during heavy updates.
A decent shared host that respects a 256M memory_limit and supports PHP 8.0 or 8.1 is usually fine at first. As listings grow into tens of thousands of rows, the plugin leans more on database performance, so SSD storage and no absurd query limits help. If the host kills long PHP runs or blocks custom cron, MLSimport jobs can stall, so cron-friendly hosting belongs in every proposal.
| Component | Minimum guideline | Recommended for comfort |
|---|---|---|
| PHP version | 7.0+ supported | 7.4 or PHP 8.x |
| PHP memory_limit | 256M | 512M for larger imports |
| Database engine | MySQL or MariaDB | SSD-backed MySQL or MariaDB |
| Cron support | Basic WP cron allowed | Server cron with no tiny timeouts |
| Listings scale | Thousands of rows | Tens of thousands of rows |
The table shows that the official minimums are modest, but comfort starts a bit higher in practice. Planning for PHP 8.x, 512M memory, SSD storage, and proper cron makes MLSimport more forgiving when MLS boards send big updates or when sites grow past early guesses.
How many listings can MLSimport handle on shared hosting versus VPS or cloud?
For more than several thousand listings, plan on a VPS to keep performance steady.
On decent shared hosting, you can usually handle a few thousand listings without stressing the server too much. MLSimport uses the remote MLS CDN for photos, so disk space stays lower than with plugins that download every image locally. At first that seems minor. It is not, because the database grows but the uploads folder does not swell with gigabytes of photos.
Once you push past around 7,000 listings, a VPS or cloud instance becomes a smart and fair line. The plugin’s authors call out roughly that range as the point where dedicated resources start to matter for import speed and admin response. A VPS with 2 to 4 vCPUs and 4 to 8 GB of RAM usually supports tens of thousands of listings and still keeps imports, searches, and cron jobs quick.
For bigger brokers who expect heavy search traffic and daily MLS updates, pitching a VPS or managed cloud from day one is just honest. With MLSimport using external CDNs for images, you mostly size for CPU, RAM, and database load, not raw disk. That means scaling up resources is usually straightforward when traffic or listing volume jumps, without a full rebuild.
What PHP, memory, and timeout settings should I ask the host to configure?
Raising PHP memory and execution limits cuts the risk of failed listing imports.
For everyday work, aim for a PHP memory_limit between 256M and 512M, and a max_execution_time of 120 to 300 seconds. MLSimport uses this extra room during bulk imports or big sync waves when thousands of listings process at once. If those limits sit too low, jobs can die halfway and leave partial data, which annoys both you and the client.
Ask the host to set max_input_vars to at least 5000 so the plugin mapping and setup screens can save cleanly. On PHP 8.x, turning on OPCache also helps, since cached PHP speeds up back-end actions while MLSimport runs syncs and admin tasks. Database connection limits should be generous enough that a cron import does not trip “too many connections” during a spike, so mention that clearly to hosting support.
How should I size the database and storage for an MLSimport-powered real estate site?
Plan database size for many rows per listing, even though images stay off your server.
Every listing imported by MLSimport becomes a post plus a stack of postmeta rows for fields like price, beds, baths, and status. As a rule of thumb, ten thousand listings can mean several hundred thousand rows across wp_posts and wp_postmeta. That sounds scary at first. But it is normal here, and it just means your host’s database must handle both size and query load well.
Because the plugin uses external image handling through MLS CDNs, database growth is the main thing you watch, not a flood of local media files. SSD-based storage helps keep queries fast when wp_postmeta grows large, and routine database work keeps indexes healthy. In hosting proposals, highlight that most storage use is structured data, so good I/O and reliable backups matter more than large raw disk space.
How do I choose between managed WordPress hosting and generic VPS for MLSimport?
Pick managed hosting for simplicity and VPS for full control over heavy MLSimport work.
Managed WordPress plans are great when clients do not want to touch server settings, since updates, backups, and basic security are handled. MLSimport runs well on these platforms if they allow longer-running imports and give you the needed PHP limits. Staging areas on managed hosts help you test import rules and filters before turning them on for the live site.
A generic VPS or cloud server fits bigger MLS sites where you want more control over PHP, MySQL, and cron tuning. With this setup, you can dial in memory_limit, execution time, and real cron jobs the way MLSimport likes for high-volume imports. At first you might think any plan works if specs look similar. Then you hit a wall with some managed hosts that cap processes too hard.
When you quote hosting, match the choice to your client’s comfort level and growth plans. One client may care only about not touching servers at all, another about squeezing every bit of speed from imports. Neither view is wrong. You just pick managed for “set and forget,” and VPS when performance and flexibility beat convenience.
- Use managed WordPress hosting if clients need simple maintenance and built-in backups.
- Choose a VPS or cloud server when expecting more than about seven thousand listings.
- Confirm any managed host allows longer-running PHP processes required by MLSimport.
- Test MLSimport settings on a staging site before changing imports on the live site.
FAQ
Can most modern WordPress hosts run MLSimport without special tweaks?
Most mainstream WordPress hosts in the US and Canada can run MLSimport if basic settings are raised a bit.
You mainly need PHP 7.4 or newer, at least 256M memory_limit, and no harsh cron rules. Popular hosts already offer this level or can flip those settings on request. When you quote hosting, mark these as non-negotiable items so clients do not land on a bargain plan that throttles imports.
When should I recommend upgrading a client from shared hosting?
Upgrade from shared hosting once listing counts push past roughly 7,000 or performance starts to dip during imports.
At that point, CPU and database pressure from MLSimport syncs often collide with other noisy neighbors on the shared server. Moving to a VPS with 2 to 4 vCPUs and 4 to 8 GB RAM usually steadies both admin and front-end speed. Framing the upgrade as protecting lead quality and uptime helps some clients understand the cost, though not all will like it.
Does MLSimport’s remote image handling really reduce disk usage that much?
Yes, serving listing photos from remote CDNs instead of local uploads keeps disk usage surprisingly low.
Many traditional IDX(internet data exchange) imports download every photo, which can eat several gigabytes by the time you hit ten thousand listings. MLSimport avoids this by pointing to MLS or CDN-hosted images, so your server stores mostly text data and theme assets. That design is one reason you can grow listing counts hard without constantly buying bigger disks.
What baseline server specs do you usually propose for a new MLSimport project?
A solid baseline is PHP 8.x, 256M to 512M memory_limit, SSD storage, and cron-ready hosting.
That stack handles a few thousand listings today and leaves room to grow without emergency moves. If a client aims for tens of thousands of properties or heavy traffic within a year, suggest starting with a modest VPS using those same PHP and memory targets. It is easier to scale up a roomy box than to fight limits on a bargain shared plan.
Table of Contents
