Pipedrive vs Pipeliner CRM: Architecture, TCO & Migration

Pipedrive vs Pipeliner CRM: Architecture, TCO & Migration

Pipedrive is a deal-centric, cloud-only CRM with no custom objects and a 300,000 combined leads-and-deals cap. Pipeliner CRM — rebranded to Coevera in April 2026 — is a visual-first, account-centric CRM with custom entities, an offline-capable desktop client, and Buying Center mapping for multi-stakeholder deals. That architectural gap drives every downstream difference: pricing, automation availability, API design, data portability, and migration complexity.

One-line verdict: Choose Pipedrive if you need a low-cost, fast-to-deploy deal pipeline for a compact sales team. Choose Pipeliner if you need custom objects, offline access, or multi-stakeholder org-chart mapping and can absorb a higher per-seat cost.

Last verified: June 2026. Pricing, rate limits, and feature availability are subject to change. Primary sources: Pipedrive API documentation, Pipedrive pricing page, Pipeliner CRM pricing page. Where specific claims depend on documentation versions, the relevant endpoint or changelog reference is noted inline.

For Pipedrive's architecture compared to other platforms, see our HubSpot vs Pipedrive guide or Pipedrive vs GoHighLevel comparison. For how Pipeliner compares to Google Workspace-native CRMs, see our Pipeliner vs Copper guide.

---

Core Architecture: Deal-Centric vs. Account-Centric

Pipedrive: Deal-Centric, Cloud-Only

Pipedrive's data model orbits the Deal. Organizations contain Persons, Persons link to Deals, and Activities fan outward from Deals. Leads live in a separate Leads Inbox and convert to Deals when qualified. This conversion is enforced through the web UI only — the REST API (POST /leads and POST /deals) provides no conversion endpoint, so any automation that needs to move a Lead into an active pipeline must either use browser automation or rebuild the record from scratch via API, duplicating field mapping logic.

The core entity types are Organizations, Persons, Deals, Leads, Activities, Products, and Projects.

The key architectural constraint: Pipedrive has no custom objects. You get custom fields on standard entities, but you cannot create new entity types. If you need to track "Properties," "Vehicles," or "Contracts," you're forced to encode that data into custom fields on Deals, Organizations, or Persons — which breaks reporting and creates maintenance debt as your data model grows. This is not a UI preference; it is a schema constraint with downstream consequences for reporting, API query structure, and automation trigger scope.

Each custom field is identified by a random 40-character hex hash in the API (e.g., a1b2c3d4e5f6...), documented in Pipedrive's custom fields API reference. Every integration or migration requires a discovery step — calling GET /dealFields, GET /personFields, GET /organizationFields — to translate human-readable names to these hashes before any data operation.

Pipedrive's structural constraints, documented:

• Loose associations: A Deal links to one Person and one Organization natively. Multi-stakeholder deals require custom fields or duplicated data entries.
• Entity limits: 300,000 combined leads and deals company-wide, regardless of plan. Confirmed in Pipedrive's fair usage policy.
• Custom field limits: 30 fields on Lite, 100 on Growth, 300 on Premium, 500 on Ultimate — per entity type.
• Activity model: All interactions are generic "Activities" with a type (Call, Meeting, Task). There is no interaction-type-specific trigger in native automations; you cannot, for example, trigger a workflow exclusively on Calls without filtering by activity type in a downstream condition.
• Cloud-only: No desktop client, no offline mode beyond basic mobile caching on the iOS/Android apps.
• Option fields: Custom option and multi-option fields are capped at 1,000 options per field.
• Products per deal: Maximum 200 line items per Deal record.

Pipeliner (Coevera): Account-Centric, Offline-Capable

Pipeliner's data model is account-centric. The standard entities are Accounts, Contacts, Leads, Opportunities, Products, Quotes, and Projects. Opportunities are Pipeliner's equivalent of Pipedrive's Deals.

The differentiating architectural feature: Pipeliner supports custom entities (custom objects). You can create entirely new entity types — "Assets," "Installations," "Subscriptions" — link them to existing entities via lookup fields, and run automation, reporting, and filtering on them. This capability is available on Business tier ($85/user/month) and above. Custom entities are fully accessible via API, including as Automatizer trigger sources and action targets.

Pipeliner's Buying Center is a native many-to-many relationship layer within each Opportunity. You can link multiple Contacts to a single Opportunity and assign them role designations — including Economic Buyer, Champion, Influencer, and Detractor. These are configurable labels, not fixed categories. The practical value depends heavily on team discipline: the Buying Center works well when sales managers enforce role-tagging as part of deal review cadences, but adoption typically requires dedicated configuration time (expect 2–4 hours of admin setup per pipeline type) and ongoing enforcement. It is not self-populating. Compared to Pipedrive's single-contact linking on Deals, this is a structural difference, not just a UI feature — the relationship data is a first-class schema object accessible via API for reporting and automation.

Pipeliner ships a hybrid desktop client (Windows and Mac) that syncs your full CRM database locally using a delta-sync engine. Records include strict revision IDs and timestamps to prevent data collisions on sync. Field reps can view contacts, update deals, add notes, and log activities without internet connectivity; changes sync automatically when connectivity is restored. Known edge case: conflict resolution on simultaneous edits (one offline, one online) defaults to last-write-wins based on sync timestamp — teams with concurrent edit workflows should test this behavior before relying on it in high-volume field scenarios.

Pipeliner also supports parent-child account hierarchies and multiple Form Views per entity — neither of which Pipedrive supports natively.

---

Data Model Comparison

Dimension	Pipedrive	Pipeliner (Coevera)
Core gravity	Deal	Account / Opportunity
Standard entities	Organizations, Persons, Deals, Leads, Activities, Products, Projects	Accounts, Contacts, Leads, Opportunities, Products, Quotes, Projects
Custom objects	❌ Not supported	✅ Custom Entities (Business+)
Custom fields	✅ On standard entities (40-char hex API keys)	✅ On all entities including custom entities
Entity limits	300,000 combined leads + deals	No documented cap on accounts, contacts, leads, opportunities
Org hierarchy	Flat; one Organization per Deal	Parent-child account hierarchies
Stakeholder mapping	Basic single-contact linking	Buying Center: configurable org charts within Opportunities
Offline access	❌ Cloud-only	✅ Hybrid desktop client (delta-sync) + offline mobile
Multiple pipelines	✅ (plan-dependent)	✅
Multiple forms per entity	❌	✅ Multiple Form Views per entity
Quotes / CPQ	❌ (Smart Docs add-on only)	✅ Native Quotes entity

The custom-objects gap is the single biggest architectural difference for growing sales operations. If your sales process requires tracking entities that don't map to standard CRM objects — equipment, locations, contracts, service installations — Pipeliner handles this natively within its schema. In Pipedrive, you'd compress that data into custom fields on existing entities (creating reporting distortion) or push it into a separate system (creating sync complexity).

---

Pricing and Total Cost of Ownership

Pipedrive Pricing (2026)

Pipedrive consolidated from five tiers to four in late 2025. Current pricing per Pipedrive's pricing page:

Plan	Annual (per seat/mo)	Monthly (per seat/mo)
Lite	$14	$24
Growth	$39	$49
Premium	$59	$79
Ultimate	$79	$99

No minimum seat requirement. Add-ons are where costs escalate:

Add-on	Cost
LeadBooster	$32.50/company/month
Campaigns	Tiered by contact volume
Web Visitors	Tiered by pageview volume
Projects	Included on Premium+; add-on on Growth
Smart Docs	Add-on on Growth and below

A 10-seat Growth team using LeadBooster and Web Visitors can realistically spend $7,000–$9,000/year before middleware costs. Because Pipedrive lacks custom objects, teams that need relational data structures typically add external tools: Zapier ($600–$2,500/year depending on task volume), Make ($400–$1,200/year), or a purpose-built database layer like Airtable ($240–$1,200/year for 10 users). These costs are real and recurring, and they belong in any honest TCO model for Pipedrive above Growth tier.

Pipeliner (Coevera) Pricing (2026)

Current pricing per Pipeliner's pricing page:

Plan	Annual (per user/mo)	Automation	API Access
Starter	$65	❌ None	❌ None
Business	$85	❌ None	✅ 100,000 calls/mo
Enterprise	$115	✅ 25 processes / 10,000 runs/mo	✅ 150,000 calls/mo
Unlimited	$150	✅ 100 processes / 100,000 runs/mo	✅ 350,000 calls/mo

The Starter plan has a 3-user minimum ($195/month floor). Monthly pricing is available on request. Additional charges apply for: API call overages, Automatizer run overages, extra storage, additional team spaces, and Field Mappings (a paid add-on on all tiers except Unlimited). Standard CSV import assistance, custom migration support, onboarding consultancy, and training are all paid services — factor this into implementation budgets.

Pipeliner includes more native functionality out of the box — the Voyager AI engine, Buying Center, and advanced visual analytics are built-in — which reduces external middleware spend. The primary hidden cost is administrative overhead: the platform's structured data model and configurable form views require a dedicated RevOps administrator. Budget 5–10 hours/month of admin time for a 20-seat deployment at steady state, more during initial configuration.

TCO Modeling at Scale

The tables below use mid-tier plans — Pipedrive Growth ($39/seat) and Pipeliner Enterprise ($115/user) — billed annually, excluding add-ons and overages:

Team size	Pipedrive Growth (annual)	Pipeliner Enterprise (annual)	Delta
10 seats	$4,680	$13,800	+$9,120
25 seats	$11,700	$34,500	+$22,800
50 seats	$23,400	$69,000	+$45,600

The break-even analysis that matters: Pipeliner's 2.5–3× list-price premium becomes rational when a Pipedrive team would otherwise spend on: (a) middleware to handle relational data Pipedrive can't store natively, (b) a developer to maintain custom integrations around the hex-hash field schema, and (c) eventual migration to a heavyweight enterprise CRM once the flat model becomes untenable. If those three costs exceed ~$18,000–$25,000/year for a 10-seat team, Pipeliner Enterprise is cheaper in practice. If they don't — because your use case is genuinely a straightforward deal pipeline — Pipedrive wins on cost and deployment speed.

The gap narrows further when you compare Pipedrive Ultimate ($79/seat) — the tier with a sandbox and enhanced security — to Pipeliner Business ($85/seat), where the plans' feature scope is more comparable. That specific comparison (10 seats, annually) is $9,480 vs. $10,200 — a $720 delta, not $9,120.

---

API Architecture and Integration Constraints

Pipedrive API

Pipedrive offers REST API v1 and v2 with OAuth 2.0 and API token authentication. Full reference at developers.pipedrive.com.

Rate limiting (token-based model, documented in Pipedrive's API changelog):

• Daily token budget: 30,000 base tokens × plan multiplier × number of seats
• Plan multipliers: 1× (Lite), 2× (Growth), 5× (Premium), 7× (Ultimate)
• Company-wide absolute maximum: 100 million tokens/day
• Burst limit: per-user rolling 2-second window; exact per-endpoint token costs documented in API response headers (X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset)

Worked example: A 10-seat Growth account has a daily budget of 600,000 tokens. A bulk sync operation pulling 10,000 Deal records (roughly 2–5 tokens per GET depending on field count) plus associated Notes and Activities can consume 80,000–150,000 tokens in a single run — sustainable for daily syncs, but a concern for real-time bidirectional integrations that also push writes.

Documented constraints:

• Custom field keys are 40-character hex hashes; must be dynamically resolved via GET /dealFields before every integration build or migration
• Leads cannot be converted to Deals via API (web app only — no conversion endpoint exists in v1 or v2 as of June 2026)
• Option/multi-option fields: 1,000 options per field maximum
• Products per deal: 200 line items maximum
• Pipedrive is permissive on data typing — it will silently coerce or drop invalid field values rather than rejecting the payload; this makes debugging data quality issues harder post-import

Pipeliner (Coevera) API

Pipeliner offers both REST API and GraphQL API. The GraphQL endpoint is a meaningful advantage for integrations that need field-specific queries: instead of fetching full entity payloads and discarding unused fields, you specify exactly which fields to return, reducing payload size and call count against monthly limits.

Rate limiting (monthly, per Pipeliner's API documentation):

Plan	Monthly API calls	API Access
Starter	0	❌ No access
Business	100,000	✅
Enterprise	150,000	✅
Unlimited	350,000	✅

Monthly ceilings create a burst risk: a migration or full resync can exhaust a month's budget in hours. Pipeliner recommends using dedicated Export endpoints for bulk extraction rather than paginated GET requests — this bypasses per-record API call counting for supported entity types. Pagination is capped at 100 records per request for standard endpoints.

Documented constraints and failure modes:

• No API access on Starter — programmatic integrations require Business tier ($85/user) minimum
• Authentication uses per-application API keys scoped to the team space; no OAuth 2.0 as of June 2026
• Pipeliner enforces strict data typing: passing a string into a numeric field, an invalid UUID for a lookup association, or a mismatched enum value causes the API to reject the entire payload with a 400 error — not just the offending field. Pipedrive silently drops bad values; Pipeliner hard-rejects. This is the most common cause of failed record imports during migrations.
• Conflict resolution on the offline desktop client uses last-write-wins based on sync timestamp; no three-way merge
• Custom entities are fully queryable and writable via both REST and GraphQL, including as Automatizer trigger sources

Integration ecosystem: Pipedrive supports 500+ native integrations (per Pipedrive's marketplace listing) vs. Pipeliner's 200+ (per Pipeliner's integration directory). Pipedrive wins on breadth and lower-friction standard connections (Slack, Google Workspace, Zoom, HubSpot bidirectional). Pipeliner wins on data-model depth — GraphQL plus custom entities plus offline sync make it more viable as an operational database, not just a pipeline tracker.

---

Automation: Workflow Builder vs. Automatizer

Pipedrive Workflow Automation

Pipedrive's automation builder is available starting on Growth ($39/seat). It supports trigger-action sequences — deal stage changes, activity completion, field updates — with outputs including email sends, activity creation, field updates, and deal creation.

Ceiling: Native automations are linear (single trigger → sequential actions). Branching logic (if/else conditions on field values) exists but is limited to one conditional branch per automation. Complex multi-step workflows with nested conditions require Make, Zapier, or direct API calls. There is no native looping or scheduled batch automation.

Practical implication: A Pipedrive Growth team running a five-stage outbound sequence with conditional re-routing typically needs Zapier or Make within 6–12 months of initial deployment. Budget for that dependency upfront.

Pipeliner Automatizer

Pipeliner's Automatizer supports multi-step processes with conditions, branching, and actions across all entity types including custom entities — a meaningful architectural advantage for teams with complex handoff logic.

The critical constraint: Automatizer is tier-gated.

Plan	Automatizer Access	Process Limit	Monthly Run Limit
Starter	❌ None	—	—
Business	❌ None	—	—
Enterprise	✅	25 processes	10,000 runs/month
Unlimited	✅	100 processes	100,000 runs/month

To get any native workflow automation in Pipeliner, you need Enterprise at $115/user/month. A 10-seat team moving from Pipedrive Growth ($39/seat) to Pipeliner Enterprise for automation parity pays $45,600 more per year. That is the actual cost of Pipeliner's automation capability relative to Pipedrive's.

---

Reporting and Security

Reporting

Pipeliner's reporting architecture is genuinely differentiated on visual analytics: drag-and-drop Kanban boards, bubble charts, compact matrix views, Navigator dashboards (a sales activity performance layer), and geolocation features (plotting accounts on a map, calculating sales routes for field reps). These are native capabilities, not integrations. For field sales teams covering geographic territories, the map view alone can justify the platform over Pipedrive.

Pipedrive's reporting covers pipeline velocity, activity completion rates, revenue forecasts (Premium+), and customizable dashboards. It is competent for standard SaaS or inside sales reporting. It does not support geographic visualization, heat maps, or multi-dimensional bubble charts natively. Power BI or Looker integrations are the standard path for teams that outgrow Pipedrive's native reporting.

Security and Compliance

Dimension	Pipedrive	Pipeliner (Coevera)
GDPR	✅	✅
SOC 2	✅	Not publicly documented
ISO 27001	Not publicly documented	✅ Certified
AI data use	Not explicitly stated	Customer data not used for AI training (stated policy)
Sandbox environment	✅ Ultimate only	Not documented
Role-based access	✅ All plans	✅ All plans
Business unit segmentation	❌	✅ Sales Units (Business+)

Pipeliner's Sales Units feature allows data segmentation by business division — different teams see different pipelines, accounts, and reports within a single instance. This is relevant for multi-division organizations that need data isolation without separate CRM instances. Pipedrive has no equivalent; multi-division organizations on Pipedrive typically use separate accounts or rely on visibility rules, neither of which provides true data segmentation.

---

Migration: Pipedrive → Pipeliner

This is the more technically straightforward direction. Pipedrive's standard entities map cleanly to Pipeliner equivalents:

Pipedrive	Pipeliner	Notes
Organizations	Accounts	1:1
Persons	Contacts	1:1
Deals	Opportunities	Field mapping required
Leads	Leads	Pipeliner integrates Leads into main workflow; qualification status may need review
Products	Products + Product Line Items	Split required
Activities	Tasks / Appointments	Type mapping required
Notes	Notes	1:1; check character limits

The structural decision point: are Pipedrive custom fields hiding missing entities? If you've encoded "Contracts," "Locations," or "Installations" as custom fields on Deals, migrating to Pipeliner is the opportunity to resolve that structural debt into proper custom entities. This decision must be made before export — it changes your field mapping, your data transformation logic, and your post-migration reporting structure.

Migration Steps

Step 1: Extract via API, not CSV. Use Pipedrive's v2 API to pull Organizations, Persons, Deals, Activities, Notes, and Products with their full field payloads. A CSV export from Pipedrive flattens relational data: Organization records are duplicated for every linked Contact, and the links between Deals, Notes, Activities, and Persons are severed. There is no reconstruction path from a flat CSV. API extraction is mandatory for zero-loss fidelity. Start with GET /organizations, GET /persons, GET /deals (paginate with limit=500&start={offset}), and fetch associated Notes and Activities per record via GET /deals/{id}/activities and GET /deals/{id}/notes.

Step 2: Resolve custom field hashes. Before any field mapping, call GET /dealFields, GET /personFields, and GET /organizationFields to build a translation dictionary: {hash: human_readable_name}. Store this as a JSON lookup table in your ETL script. Every Pipedrive payload will contain fields named by their hex hash; your transformation layer must translate these before writing to Pipeliner's typed schema.

Step 3: Handle the Buying Center gap. In Pipedrive, a Deal links to one primary Person. In Pipeliner, an Opportunity supports a Buying Center with multiple Contacts in defined roles. Your migration script must: (a) extract the primary Person and assign a default role (e.g., "Primary Contact"); (b) if you have custom fields tracking secondary contacts (a common Pipedrive workaround), parse those fields, resolve the Contact in Pipeliner's system, and establish the relational link via POST /entities/opportunitycontactroles. Any secondary contacts stored in freeform note text are unstructured and unrecoverable programmatically.

Step 4: Preserve historical timestamps and attribution. Both systems track add_time and update_time. When pushing Activities into Pipeliner, use the API's created field override to preserve original dates — otherwise five years of historical calls appear as if they happened on migration day, destroying trend reporting. For departed reps (inactive Pipedrive users), map their records to inactive Pipeliner profiles, or assign activities to a "System User" and append the original rep's name to the note body as a string.

Step 5: Meet Pipeliner's import requirements — exactly. Pipeliner's API enforces hard requirements on Opportunity creation: name, value, closing_date, pipeline_step_id, status, owner_id, and sales_unit_id are all mandatory. Pipeline step and sales unit values must exactly match configured IDs in your Pipeliner instance — a mismatch causes a 400 rejection of the entire record, not a field-level warning. Account matching uses exact name matching; duplicates cause rejection. Product line items require one row per product with exact product-name matching against your Pipeliner product catalog. For historical analytics, also migrate: Won Date, Lost Date, and Lost Reason.

Step 6: Rebuild automations manually. Pipedrive workflow automations have no export format compatible with Pipeliner's Automatizer. Each automation must be manually recreated — and Automatizer is only available on Enterprise ($115/user). If you're migrating from Pipedrive Growth, budget for the plan upgrade before your go-live date.

---

Migration: Pipeliner → Pipedrive

This direction is structurally harder because you are compressing a richer schema into a flatter one. Every decision here involves accepting data loss or encoding complexity into workarounds.

Step 1: Audit custom entities first. Before exporting anything, catalog every custom entity in Pipeliner and make an explicit decision for each: (a) flatten into custom fields on a Pipedrive standard entity, (b) push to an external system (Airtable, a database), or (c) discard. This decision changes your export logic, your field mapping, and your post-migration reporting. Making this decision during field mapping — rather than before — is the most common cause of migration rework.

Step 2: Flatten Pipeliner's hierarchy. Parent-child account hierarchies have no equivalent in Pipedrive — Organizations are flat. Buying Center org charts (Economic Buyer, Champion, Detractor role assignments) have no native Pipedrive equivalent. Your options: (a) convert role assignments to freeform notes on the Deal, (b) create a custom multi-select field on the Deal and encode contact roles as text, or (c) discard the relationship structure. Option (c) is the most common outcome. Plan for it explicitly rather than discovering it mid-migration.

Step 3: Transform Opportunities → Deals. Map Opportunity fields to Deal fields including pipeline stage equivalents. Carry over Won Date, Lost Date, and Lost Reason — Pipedrive stores these on the Deal record and they affect historical funnel analytics. Products in Pipeliner map to Pipedrive's Products + line items on Deals, but Pipedrive caps line items at 200 per Deal.

Step 4: Respect Pipedrive's hard limits. The 300,000 combined leads-and-deals cap applies regardless of plan. Custom field limits (30 on Lite, 100 on Growth, 300 on Premium, 500 on Ultimate) may constrain what you can import — model your field count before starting. Exceed the limit and Pipedrive will reject the custom field creation, blocking subsequent record imports that reference that field.

Step 5: Import via API with duplicate-merge testing. Use Pipedrive's API to preserve the Organization → Person → Deal relationship chain. Pipedrive supports duplicate detection during Person and Organization import via its matching rules — test with a 500-record representative sample before running the full migration to validate merge behavior.

---

Who Should Choose Which

Choose Pipedrive if:

• Your team is under 50 reps running a straightforward deal pipeline without non-standard entity types
• Budget is the primary constraint — functional CRM at $39/seat/month with automation included
• Your integration needs are moderate and standard (Slack, Google Workspace, Zoom) — Pipedrive's 500+ native connectors cover most cases
• Fast deployment matters — Pipedrive is adoption-ready in days, not weeks; Pipeliner's structured configuration takes 2–6 weeks for a clean setup
• You can accept the 300,000 entity cap and will not need offline desktop access

Choose Pipeliner (Coevera) if:

• You need custom entities for non-standard business objects (equipment, locations, contracts, installations)
• Field reps need offline access with full database sync and delta-conflict resolution
• Multi-stakeholder deals are the norm and your team will enforce Buying Center role-tagging as part of deal reviews
• Geographic territory visualization or heat maps are required natively (without BI tool integration)
• You can budget $115/user/month minimum for automation capability and have a dedicated RevOps administrator for ongoing configuration

Choose neither if:

• You need cross-department visibility across sales, marketing, and service under one data model — look at HubSpot or Salesforce
• You need a multi-tenant, white-label platform — look at GoHighLevel (and our Pipedrive to GoHighLevel migration guide)
• Your compliance requirements demand enterprise territory management, advanced forecasting, or CPQ — neither platform is purpose-built for that

The signal you've outgrown Pipedrive: You're encoding relational data in symptomatic ways — giant notes fields containing structured data, pseudo-IDs in custom text fields, CSVs living outside the CRM for entity types the system can't store, or Products records being repurposed as non-product objects. These are schema workarounds, not process problems. The data model is too small.

The signal Pipeliner is wrong for your team: You're on Business tier and unable to move to Enterprise, which means you have API access but no automation. You're paying $85/user/month for a manually-operated CRM with limited integration options and no workflow capability. That is the worst position in Pipeliner's pricing structure — high cost, low leverage.

---

Making the Switch Without Data Loss

Migrating between these two CRMs is a data-model translation problem, not a CSV round-trip. The custom-objects gap in Pipedrive, the automation tier-gating in Pipeliner, and the fundamentally different data gravity (deal-centric vs. account-centric) mean every migration has structural decisions that affect data integrity — and those decisions compound.

The key diagnostic question: are you translating between equivalent models, or compressing one into the other? Pipedrive to Pipeliner is typically a schema expansion — new entity types, richer relationships, more automation triggers. Pipeliner to Pipedrive is a compression exercise — and compression is where data loss, reporting drift, and user frustration start. Every relationship that can't be represented in Pipedrive's flat model is either a note, a workaround, or gone.

If you're making this move with live pipelines, historical revenue data, products, attachments, and integrations in play, the cutover design is the deliverable — not the import wizard.