Pre-mover data is a small, quiet category in Canada. A handful of providers. A handful of shapes. And not much public guidance on how to tell them apart.
This page is the guidance we wish existed when enterprise teams started calling us. It's written from our side of the table (we sell this data), but the questions below work on any vendor, including us. If a provider can't answer them clearly, that's the signal. Use it however you want.
Here's what to ask, and why each one matters.
How does the data actually reach your team?
The oldest shape in this category is the list drop. A vendor sends a flat file (CSV, Excel, sometimes SFTP). Your marketing team loads it into a campaign tool and executes. It works, and it's been working since the 1990s.
The newer shape is data integration. The provider's data lives inside whatever environment your team already operates in: Snowflake, Databricks, an API, an MCP endpoint for AI agents. Your data team joins it to your customer records the same way they join any other table.
Both work. But they attract different buyers, and the difference matters. If your team builds production pipelines, lifetime-value models, or AI-driven next-best-offer systems, a flat file is friction. If your team executes quarterly direct-mail drops, a flat file is fine.
Ask the vendor which shape they actually deliver. Some will claim both and mean one.
How fast does the signal arrive after the listing event?
A listing goes live on a Tuesday. The vendor's pipeline captures it sometime between Tuesday and six weeks from Tuesday. That gap is what you're really paying for.
Monthly refresh means the median listing you receive is about two weeks old by the time it lands. Weekly refresh cuts that to three or four days. Daily refresh is closer to 24 hours. If the vendor publishes monthly reports or "monthly factoids," that's usually a signal about their pipeline cadence, not just their marketing.
For categories where the acquisition window is already short (telecom retention, insurance quoting, mortgage competition), two extra weeks of delay is the difference between winning the customer and watching them sign somewhere else.
Does the vendor operate their own pipeline, or are you buying a snapshot?
This is the question most enterprise buyers don't think to ask, and it's the one that decides whether your data supply is stable in twelve months.
A pre-mover dataset is not a one-time acquisition. It's a living thing. Every week there are new listings, re-listings, price changes, withdrawals, and sold events. Capturing that flow continuously requires infrastructure: scrapers, address validation, matchkey systems, deduplication logic, lifecycle state tracking. None of that is easy. Much of it is years of accumulated engineering.
Some vendors have that infrastructure. Others don't. They built their dataset by acquiring a snapshot from somewhere else and have been selling slices of it ever since. A snapshot-based vendor can show you data that looks current today. What they can't do is maintain it. Every week that passes, their signal decays against the live market.
Ask the vendor to describe their pipeline. Not their data. Their pipeline. How is it built? How is it updated? Who operates it? How long has it been running? If the vendor can't describe how the data is produced, updated, and delivered week over week, what you're buying is a snapshot that will degrade under you.
Data built in the last two years on someone else's output can't evolve. Data built over a decade-plus of continuous weekly capture can.
Is the delivered data person-level or property-level?
Some Canadian pre-mover providers deliver enriched contact records (names, phone numbers, demographic profiles) joined to listings. Others deliver property-level data only, leaving the customer match to your first-party CRM.
Neither is automatically right. What's right depends on how your privacy and compliance team wants to handle the data.
Person-level delivery is faster to activate for outbound campaigns but carries more weight in a PIPEDA review and, in Quebec, under Law 25. Property-level delivery is slower to activate but easier to clear with privacy counsel. The join to your customer records happens inside your own consent framework, which your team already understands.
If your organization has a sensitive compliance posture (a regulated bank, a telecom with public-accountability obligations, a government department), the property-level shape usually survives procurement more cleanly. If your team is a direct-mail shop with existing consumer-contact infrastructure, person-level is probably how you already operate.
Can the vendor survive your procurement process?
This one isn't about the data. It's about whether the vendor as an organization can handle the operational side of an enterprise contract.
Does the vendor have a registered corporate entity you can verify? An MSA template that hasn't been written in crayon? A privacy policy and terms of service that aren't broken links? A clear answer about data lineage and subprocessor handling for your vendor-risk team? SOC 2 or equivalent if you're a regulated buyer?
These are table stakes, not differentiators. But they sort the field. Many small data vendors in Canada are solo operators running on WordPress templates with placeholder legal pages. That's not necessarily disqualifying for a small marketing test. It absolutely is disqualifying for a production contract at a bank, a telecom, or any public-sector buyer. Procurement will catch it and the deal will die.
Check the vendor's footer before you schedule the first call.
What to ask on the first call
Bring this list. Take notes. If the vendor dodges more than one, you have your answer.
- How is your data delivered? Name the channels.
- How often does the data refresh? Be specific.
- Describe your pipeline end to end. How long has it been running?
- Do you operate the capture yourself, or aggregate from another provider?
- Is the delivered data property-level or person-level?
- How do your other clients handle PIPEDA review?
- Can we test a sample against our own historical data before committing?
- What's your corporate entity? Where is it registered?
A final note on this category
Canadian pre-mover data is small enough that most buyers end up evaluating two or three vendors. The quality spread between those vendors is wider than in most data categories, because the barriers to entry are low. A WordPress site and a spreadsheet look a lot like a real business from the outside.
The five questions above exist because we've seen what goes wrong when buyers skip them. A contract signed with a vendor who can't sustain their pipeline is a contract you'll be re-signing with someone else in eighteen months. A contract signed with a vendor whose privacy posture crumbles under review is a contract that dies in procurement before it's activated. A contract signed with a vendor whose delivery architecture doesn't fit your stack is a contract that becomes operationally painful by month three.
None of this is exotic. It's the basic diligence any B2B data buyer would apply in a more mature category. This one is just young enough that the diligence hasn't become standard yet.
Ask the questions. Get specific answers. Compare them against each other. That's the whole guide.