# E-commerce Migration Lead Generator (`magnova/shopify-actor`) Actor

Find e-commerce sites ready to migrate to Shopify. Detects WooCommerce, Magento, BigCommerce, and OpenCart stores, analyzes their performance issues, and scores their migration readiness.

- **URL**: https://apify.com/magnova/shopify-actor.md
- **Developed by:** [Magnova](https://apify.com/magnova) (community)
- **Categories:** Lead generation, E-commerce
- **Stats:** 14 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.00501 / result

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Shopify Migration Leads Detector

An Apify Actor that identifies e-commerce websites ready for Shopify migration by analyzing their platform, performance, and pain points.

### What It Does

1. **Detects e-commerce platforms** - WooCommerce, Magento, BigCommerce, OpenCart, PrestaShop
2. **Excludes Shopify sites** - Only finds sites NOT already on Shopify
3. **Analyzes performance** - Uses Google PageSpeed Insights API (mobile-first)
4. **Identifies pain points** - Slow loading, poor mobile experience, outdated versions
5. **Scores migration readiness** - 0-100 score with Hot/Warm/Cold classification
6. **Extracts contact info** - Publicly visible emails, phones, and social links

### Lead Qualification Levels

| Score | Level | What It Means | Recommended Action |
|-------|-------|---------------|-------------------|
| **70-100** | 🔥 Hot | Multiple pain points, high intent | Reach out immediately |
| **50-69** | 🟡 Warm | Good candidate, some issues | Nurture with case studies |
| **30-49** | 🔵 Cold | Potential fit, fewer issues | Add to long-term campaign |
| **0-29** | ⚪ Low Priority | Site performing well | Low migration urgency |

### Input

```json
{
    "urls": [
        "https://example-woocommerce-store.com/",
        "https://another-magento-store.com/"
    ],
    "minPerformanceScore": 70,
    "minMobileScore": 70,
    "extractContactInfo": true,
    "includeShopify": false,
    "maxConcurrency": 5
}
```

| Field | Type | Default | Description |
|-------|------|---------|-------------|
| `urls` | array | required | E-commerce URLs to analyze |
| `minPerformanceScore` | number | 70 | Only include sites scoring BELOW this |
| `minMobileScore` | number | 70 | Only include sites with mobile BELOW this |
| `extractContactInfo` | boolean | true | Extract public contact info |
| `includeShopify` | boolean | false | Include Shopify sites in results |
| `maxConcurrency` | number | 5 | Max parallel requests |

### Output

```json
{
    "migrationReadinessScore": 54,
    "qualificationLevel": "Warm",
    "recommendation": "Good candidate. Nurture with case studies and ROI content.",
    "painPoints": [
        "Needs improvement on mobile (score 50-70)",
        "Slow page load (LCP > 4s)",
        "WordPress-based (potential security/maintenance concerns)"
    ],
    "url": "https://example-store.com/",
    "platform": "WooCommerce",
    "platformConfidence": 100,
    "performanceScore": 83,
    "mobileScore": 57,
    "coreWebVitals": {
        "lcp": 7085,
        "cls": 0.015,
        "tbt": 451
    },
    "contact": {
        "emails": ["info@example.com"],
        "phones": [],
        "social": {
            "facebook": "https://facebook.com/example",
            "instagram": "https://instagram.com/example"
        }
    }
}
```

### How Scoring Works

The migration readiness score is calculated from three factors:

| Factor | Weight | What It Measures |
|--------|--------|------------------|
| **Performance** | 45% | Mobile performance (70% of this), desktop (30%) |
| **Pain Points** | 30% | Number of identified issues (20 pts each) |
| **Platform** | 25% | Migration complexity (Magento > WooCommerce > BigCommerce) |

**Key insight:** Poor performance = higher score. Sites with slow mobile speeds are better migration leads!

### Platforms Detected

| Platform | Base Score | Why They Migrate |
|----------|------------|------------------|
| Magento | 95 | Complex, expensive to maintain |
| OpenCart | 90 | Limited features, poor support |
| PrestaShop | 85 | Seeking simpler solutions |
| WooCommerce | 80 | Outgrow WordPress, security concerns |
| BigCommerce | 55 | Less common, already SaaS |

### Legal & Ethical

This actor only collects **publicly available information**:

- ✅ HTML/CSS/JS signatures visible to any visitor
- ✅ Google PageSpeed API data (public API)
- ✅ Contact info displayed on public pages
- ❌ Does NOT access data behind logins
- ❌ Does NOT collect personal user data

### Use Cases

- **Shopify agencies** finding migration prospects
- **E-commerce consultants** qualifying leads
- **Sales teams** building targeted outreach lists
- **Market research** on platform distribution

### Support

For issues or feature requests, open a GitHub issue.

# Actor input Schema

## `urls` (type: `array`):

List of e-commerce website URLs to analyze

## `minPerformanceScore` (type: `integer`):

Only include sites with performance score BELOW this threshold (worse performance = better lead). Set to 100 to include all.

## `minMobileScore` (type: `integer`):

Only include sites with mobile score BELOW this threshold. Set to 100 to include all.

## `extractContactInfo` (type: `boolean`):

Extract publicly visible contact information (email, phone) from the website

## `includeShopify` (type: `boolean`):

Include sites already on Shopify in results (useful for comparison)

## `maxConcurrency` (type: `integer`):

Maximum number of concurrent page analyses

## Actor input object example

```json
{
  "urls": [
    "https://example-store.com/"
  ],
  "minPerformanceScore": 70,
  "minMobileScore": 70,
  "extractContactInfo": true,
  "includeShopify": false,
  "maxConcurrency": 5
}
```

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "urls": [
        "https://example-store.com/"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("magnova/shopify-actor").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "urls": ["https://example-store.com/"] }

# Run the Actor and wait for it to finish
run = client.actor("magnova/shopify-actor").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "urls": [
    "https://example-store.com/"
  ]
}' |
apify call magnova/shopify-actor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,magnova/shopify-actor"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/Z1cQUatnnh3a7MaIx/builds/bQR540F2xChdepGvd/openapi.json