⚡ What This Guide Covers
GHL Snapshots are the single feature that separates agencies that scale from agencies that plateau. A Snapshot is a pre-built sub-account template — capturing every workflow, pipeline, funnel page, email template, calendar, custom field, and setting from one sub-account and packaging it for instant deployment into any new sub-account. Done correctly, a Snapshot turns a 2-day client onboarding process into a 2-hour one. This complete 2026 guide covers everything: what Snapshots capture and what they do not, how to build a production-quality Snapshot from scratch, how to export your Snapshot and share it with other GHL users, how to import third-party or marketplace Snapshots, how to maintain and version your Snapshots as your systems improve, and the most common mistakes that cause Snapshot deployments to fail silently after the client is already onboarded.
👉 Try GoHighLevel Free — 30 Days + Free Live BootcampMost GHL agency operators understand Snapshots conceptually — they know a Snapshot is a template. Fewer understand what a Snapshot actually captures, what it does not capture, and why a poorly built Snapshot deployed to 20 client sub-accounts creates 20 separate problems to fix individually. The distinction between a Snapshot that works and one that breaks silently after deployment comes down to understanding exactly what is and is not transferred, and building the template sub-account in a way that makes the transferred elements work without client-specific data.
This guide covers the complete Snapshot lifecycle: planning what belongs in a Snapshot, building the template sub-account, creating the Snapshot, sharing and importing it, deploying it to a new sub-account, completing the post-deployment configuration that Snapshots cannot automate, and maintaining the Snapshot as a living asset that improves with each client deployment.
What Is a GoHighLevel Snapshot?
A Snapshot is a point-in-time export of a GHL sub-account’s configuration — not its data. When you create a Snapshot, GHL packages the structural elements of that sub-account (the workflows, pipelines, funnels, templates, calendars, custom fields, and settings) into a shareable package. When you import that Snapshot into a new sub-account, those structural elements are recreated in the destination sub-account. Contacts, conversations, opportunities, notes, and any actual business data are never included in a Snapshot.
Think of a Snapshot as a blueprint — it contains the instructions for how to build the building, but not the furniture. A new sub-account that receives a Snapshot gets the complete workflow automation system, the pipeline stages, the funnel pages, and the email templates — ready to run as soon as the client-specific configuration (phone number, sending domain, Google Calendar connection) is completed.
What a Snapshot Captures — and What It Does Not
Understanding this distinction prevents the most common Snapshot disappointment: deploying a Snapshot and discovering that key elements are missing or that things that seemed to transfer did not work as expected.
All workflows — including their triggers, actions, wait steps, if/else conditions, and internal notes — are captured in the Snapshot. Workflows deploy in Draft (inactive) status — they must be individually activated after deployment. This is intentional: it prevents automations from firing on real leads before the agency has reviewed and activated them. Any workflow that references a specific calendar, pipeline, or form connects to the equivalents in the destination sub-account after deployment, provided those elements were also included in the Snapshot.
All pipelines with their stage names, stage order, and stage colours are captured. Opportunity values and probabilities configured per stage are included. Existing opportunities (actual deals) in the template sub-account are not included — only the pipeline structure.
All funnel pages and website pages — including their layout, design elements, copy, images, and embedded forms — are captured. Form elements within funnels are captured and reconnect to the destination sub-account’s equivalent forms. Custom domain assignments are not transferred (DNS settings are account-specific and must be reconfigured per sub-account). Funnel page URLs become active on the destination sub-account’s default GHL domain after deployment.
All saved email templates are captured, including their HTML structure, images, and personalisation tokens. Campaign drafts (unsent broadcast campaigns) are captured. Sent campaign history and open/click data are not captured — only the template structures.
Calendar names, durations, availability hours, buffer times, and intake form configurations are captured. What is not automatically transferred: the Google Calendar or Outlook calendar connection (must be reconnected per sub-account), the specific team member assigned to the calendar (must be reassigned after deployment), and any Zoom integration link (regenerated per account). The calendar structure deploys correctly but requires 3–4 reconnection steps after deployment to be functional.
All custom contact fields, opportunity fields, and conversation fields are captured with their field names, types (text, dropdown, date, etc.), and option values for dropdown fields. Custom field values stored in existing contacts are not captured — only the field structure itself.
All forms and surveys — including their field configurations, conditional logic, and styling — are captured. Form submission data from the template sub-account is not transferred. After deployment, forms need their post-submission redirect URLs updated to reflect the destination sub-account’s funnel page URLs rather than the template sub-account’s URLs.
The text content of SMS messages and email bodies inside workflows is captured. What may require updating after deployment: any hardcoded business name, phone number, website URL, or calendar link inside the message content that references the template sub-account rather than the destination client. This is one of the most common causes of Snapshot deployment errors — message copy that has been written with placeholder text that was never updated from the template. Build all messages with merge tags ({{business.name}}, {{contact.first_name}}) rather than hardcoded values wherever possible.
No business data transfers in a Snapshot. Contacts, conversations, notes, tasks, appointments, opportunity records, transaction history, and any user-generated content in the template sub-account are never included. Snapshots are structural templates, not data backups.
Third-party integrations — Google Calendar, Stripe, Facebook, Google Ads, Twilio/LC Phone, Mailgun, and all other connected accounts — are not included in Snapshots. Each new sub-account requires its own integration setup. This is by design: each client account connects to the client’s own Google Calendar, the client’s own Facebook Page, and so on. The Snapshot provides the framework; the agency completes the client-specific connections.
Building a Production-Quality Snapshot
The quality of your Snapshot determines the quality of every client onboarding that follows. A Snapshot built once and maintained well saves 2–4 days of setup time per client. A poorly built Snapshot creates debugging work that exceeds the time saved. These steps cover how to build a Snapshot that deploys reliably every time.
Never build your Snapshot inside a live client sub-account. Create a dedicated template sub-account specifically for Snapshot development — name it clearly so it is never confused with a real client account (e.g. “TEMPLATE — HVAC Snapshot v2.0” or “MASTER — Real Estate Snapshot”).
Why a separate template sub-account matters:
- Changes made while developing the Snapshot do not affect live client accounts
- You can test automations using your own phone number and email without affecting real leads
- The Snapshot always reflects the intended template state, not a modified client configuration
- Multiple team members can review and refine the template before it is deployed to clients
Template sub-account naming convention: Include the vertical, version number, and date in the name — “TEMPLATE — Dental v2.1 (Mar 2026).” This makes it immediately clear which template sub-account represents the current production version when you have multiple verticals and versions.
Build every workflow with client-agnostic content wherever possible — using GHL merge tags instead of hardcoded values. This is the single most important practice for Snapshot reliability.
Use merge tags for all variable content:
{{business.name}}— resolves to the sub-account’s Business Name (set in Settings → Business Profile){{contact.first_name}}— prospect’s first name from CRM{{appointment.start_time}}— booking date and time from calendar{{calendar.event_link}}— Zoom or Google Meet link for the appointment{{calendar.reschedule_link}}— self-reschedule link
For elements that cannot be merge-tagged (specific booking page URL, specific Google review link, specific ad account ID), use a clearly marked placeholder in the workflow content: “[INSERT: Client’s Google Review Link]” in bright brackets. This makes post-deployment review trivially easy — search the sub-account for “[INSERT” and replace every instance with the client-specific value.
Core workflows every production Snapshot should include:
- Speed-to-contact (new lead → immediate SMS + email + pipeline creation)
- Missed Call Text Back (missed call → immediate SMS recovery)
- Appointment confirmation + 24hr + 1hr reminders
- No-show recovery sequence (3-touch re-booking)
- Closed Won → review request (7-day delay)
- Cold lead re-engagement (30-day re-contact)
- Internal lead alert (new high-intent lead → team notification)
Configure the pipeline with stage names appropriate for the target vertical. For a dental practice Snapshot: New Patient Enquiry → Called → Appointment Booked → New Patient Visit → Treatment Accepted → Active Patient. For a real estate Snapshot: New Lead → Showing Scheduled → Offer Submitted → Under Contract → Closed. Stage names should reflect the client’s business language, not generic marketing agency language.
Custom fields to include in every vertical Snapshot:
- Lead Source (dropdown) — Facebook Ad, Google Ad, Website Form, Referral, Organic. Populates from workflow tags for lead source attribution reporting.
- Service Interest (dropdown specific to vertical) — for a dental practice: General Checkup, Cosmetic, Orthodontics, Emergency.
- Preferred Contact Method (dropdown) — SMS, Email, Phone Call.
- Date of First Contact (date) — auto-populated on contact creation for pipeline velocity tracking.
- Any vertical-specific fields (e.g. “Property Type” for real estate, “Last Service Date” for home services).
Add these custom fields to the intake forms within the Snapshot so they populate automatically when a prospect submits a form or books through the calendar — eliminating manual data entry after deployment.
Build the core funnel pages in the template sub-account. Use placeholder content — a logo placeholder image, placeholder business name, placeholder tagline — that is clearly marked for replacement after deployment. The layout, design, and structure transfer; the client-specific branding is applied post-deployment.
Minimum funnel pages for a service business Snapshot:
- Lead capture page: Headline, offer description, 3 benefit bullets, intake form. The form connects to the pipeline and triggers the speed-to-contact workflow on submission.
- Thank-you / booking page: Post-submission page that either shows the embedded GHL calendar (for free offer with immediate booking) or confirms the form submission and tells the prospect what happens next.
- Contact / homepage: Basic business information page that can be used as the client’s website if they do not have one, or as a standalone landing page.
Build the calendar in the template sub-account with your standard recommended availability configuration — the settings you apply to most clients. After Snapshot deployment, availability is adjusted to the specific client’s actual working hours. The calendar name, duration, buffer time, intake form connection, and confirmation messages transfer; the Google Calendar connection and team member assignment are configured post-deployment.
Template calendar configuration recommendations:
- Name: Use a generic but descriptive name — “New Appointment” or “Service Enquiry Call.” The client can rename it post-deployment if needed.
- Duration: Set to the most common appointment length for the vertical (30 minutes for consultations, 60 minutes for service estimates, 20 minutes for follow-up calls).
- Availability: Set to Mon–Fri, 9am–5pm as a default. Every client adjusts this to their actual hours post-deployment.
- Minimum scheduling notice: 24 hours — a conservative default that clients can reduce if they handle same-day bookings.
- Confirmation and reminder messages: Write these using merge tags so they reference the correct business name and appointment details automatically after deployment.
Before creating the Snapshot, run a complete end-to-end test of every workflow in the template sub-account using a test contact with your own phone number and email address. This is the step most Snapshot builders skip — and the one that would have caught every error before it affected a real client.
Test checklist:
- Submit the lead capture form → verify contact is created, pipeline opportunity is created, speed-to-contact SMS arrives on your phone, email arrives in your inbox
- Book a test appointment via the calendar → verify confirmation SMS and email arrive, verify appointment appears in GHL calendar, verify reminder fires at correct time
- Mark the test appointment No-Show → verify no-show recovery SMS sequence fires
- Move test opportunity to Closed Won → verify review request workflow fires at the correct delay
- Trigger the Missed Call Text Back by calling the template sub-account’s phone number and hanging up → verify text back SMS fires within 60 seconds
- Review every SMS message received — confirm no hardcoded business names or URLs from the template are present that should have been merge tags
Creating and Exporting Your Snapshot
Navigate to the Agency-level dashboard (not the sub-account level) → Snapshots → + Create Snapshot.
- Snapshot Name: Include the vertical, version, and date — “Dental Practice — Complete Setup v2.1 (Mar 2026)”
- Select the source sub-account: Choose your template sub-account from the dropdown
- Select components to include: GHL presents a checklist of what to include in the Snapshot — you can include or exclude specific workflows, funnels, calendars, and templates. For a production Snapshot, include everything unless a specific component is not ready for deployment.
- Create Snapshot: GHL processes the Snapshot creation (typically takes 30 seconds to 2 minutes depending on account complexity). The completed Snapshot appears in your Snapshots library.
GHL Snapshots can be shared with other GHL agency accounts via a shareable link. This is how Snapshot marketplaces, GHL certified partners, and agency-to-agency Snapshot transfers work.
To share a Snapshot: Agency Dashboard → Snapshots → click the three-dot menu on your Snapshot → Share. GHL generates a unique shareable URL. Anyone with a GHL agency account who visits that URL can import your Snapshot into their account.
Three sharing options:
- Public link: Anyone with the link can import. Use for publicly distributed Snapshots — marketplace listings, blog post downloads, GHL community shares.
- Restricted link: Only specific GHL accounts can import using the link. Use for premium paid Snapshots or for sharing with specific partner agencies.
- Agency-only: Only deployable within your own agency’s sub-accounts — the Snapshot is not externally shareable. Use for proprietary agency templates you do not want distributed.
Snapshot marketplaces: Several third-party GHL Snapshot marketplaces (HighLevel Marketplace, various GHL Facebook group Snapshot threads) allow agencies to list their Snapshots for purchase or free download. Selling a well-built vertical Snapshot on these marketplaces is an additional revenue stream for established GHL agencies — a dental Snapshot sold at $97–$297 one-time, purchased by 100 agencies, generates $9,700–$29,700 from a one-time build investment.
Importing a Snapshot (From Marketplace or Another Agency)
When you receive a shareable Snapshot link from another GHL user, marketplace, or partner:
- Navigate to Agency Dashboard → Snapshots → Import Snapshot
- Paste the shareable Snapshot URL into the import field
- GHL validates the link and imports the Snapshot into your agency’s Snapshot library
- The imported Snapshot is now available for deployment to any of your sub-accounts
Before deploying an imported Snapshot to a client sub-account:
- Deploy it to a blank test sub-account first to review all components
- Read through every workflow — check for hardcoded business names, phone numbers, or URLs from the original creator’s agency that will need replacement
- Review all funnel pages for placeholder content that needs updating
- Check for any integrated tools (specific Zapier webhooks, custom integrations) that will not transfer and require your own configuration
Ready to Build Your First Snapshot?
Start your 30-day free trial — full access to sub-accounts, Snapshot creation, workflow builder, and the complete GHL platform.
→ Start 30-Day Free Trial + Free BootcampDeploying a Snapshot to a New Client Sub-Account
Snapshots can be applied either during new sub-account creation or to an existing sub-account after creation.
During new sub-account creation: When creating a new sub-account (Agency Dashboard → Sub-Accounts → + Add Sub-Account), the creation wizard includes a Snapshot selection step. Choose your relevant vertical Snapshot from the dropdown. The Snapshot deploys automatically as the sub-account is created — by the time the sub-account is ready, all workflows, pipelines, funnels, and templates are already in place.
To an existing sub-account: Navigate to Agency Dashboard → Sub-Accounts → find the relevant sub-account → click the sub-account settings icon → Apply Snapshot. Select the Snapshot and confirm deployment. GHL merges the Snapshot content into the existing sub-account — existing elements are not overwritten, Snapshot elements are added alongside them.
Post-Deployment Configuration Checklist
Every Snapshot deployment requires the same post-deployment configuration steps to be completed before the sub-account goes live with real client leads. Build this checklist into your onboarding process — it represents the 10–20% of setup that Snapshots cannot automate.
| Configuration Task | Where in GHL | Information Needed from Client | Estimated Time |
|---|---|---|---|
| Update business name and contact info | Settings → Business Profile | Business name, address, phone, email, timezone | 5 min |
| Upload client logo and brand colours | Settings → Business Profile → Branding | Logo file (PNG transparent), primary hex colour | 5 min |
| Configure email sending domain | Settings → Email Services → Add Domain | DNS access to client’s domain registrar | 20–30 min |
| Provision phone number and activate A2P | Settings → Phone Numbers → Add Number | Client’s area code preference | 10 min + 1–5 day A2P approval |
| Connect Google Calendar (two-way sync) | Settings → Integrations → Google Calendar | Client’s Google account login | 10 min |
| Connect Google Business Profile | Settings → Integrations → Google My Business | Client’s Google Business Profile account | 5 min |
| Connect Facebook Page and Lead Ads | Settings → Integrations → Facebook | Client’s Facebook Business Manager access | 10 min |
| Connect Stripe for payments | Settings → Integrations → Stripe | Client’s Stripe account (or create one) | 10 min |
| Update [INSERT] placeholders in workflows | Automation → Workflows → review each | Google review link, specific booking URL, custom copy | 30–45 min |
| Activate all workflows | Automation → Workflows → toggle each to Published | None — internal review step | 15 min |
| Update funnel page branding | Sites → Funnels → edit each page | Client logo, colours, business name, photos | 30–60 min |
| Set calendar availability hours | Calendars → Calendar Settings → Availability | Client’s actual working hours and time zone | 10 min |
| Send test lead through the full system | Submit the live lead capture form | Use your own phone/email | 20 min |
Snapshot Versioning and Maintenance
Your Snapshot library is a living asset — it should improve with every client deployment. The agencies with the most operationally efficient onboarding processes are not the ones who built the best Snapshot on their first attempt. They are the ones who built a systematic improvement process: every onboarding surfaces a problem, every problem gets fixed in the template, and the next deployment is smoother than the last.
The Snapshot Improvement Loop
- During every client onboarding, note every manual fix: Every time you edit a workflow, update a funnel page element, or fix a message after deployment, record the issue in a running Snapshot improvement log. After 3 client onboardings, review the log and incorporate the fixes into the template sub-account before creating the next Snapshot version.
- Increment the version number after every update: Minor fixes (fixing a merge tag, updating a calendar duration) → increment the minor version (v1.2 → v1.3). Significant additions (new workflow, new funnel page, new calendar type) → increment the major version (v1.3 → v2.0). Keep the version history documented so you know which version each active client is running.
- Maintain a Snapshot change log: A simple Google Doc or Notion page documenting what changed in each version. “v1.3 (Mar 2026): Fixed Google review link placeholder label. Added monthly re-engagement workflow. Updated Missed Call Text Back SMS copy.” This log is valuable when clients report issues — you can immediately check which Snapshot version they are running and whether the reported issue was fixed in a later version.
- Test before promoting to production: Every time you update the template sub-account and create a new Snapshot version, deploy it to a blank test sub-account and run the end-to-end test sequence before using it for real client onboarding. A 20-minute test prevents hours of post-onboarding debugging.
8 Snapshot Mistakes That Break Deployments
- Hardcoding business-specific values in workflows: Any SMS or email message that contains the template sub-account’s name, phone number, or URL breaks silently after deployment — the client’s customers receive messages that reference the wrong business. Use {{business.name}} and other merge tags throughout, and use “[INSERT: X]” placeholders for values that cannot be merge-tagged.
- Not testing before creating the Snapshot: The Snapshot captures whatever is in the template sub-account at the moment of creation — including broken workflows, missing form connections, and incomplete funnel pages. Run the full end-to-end test before creating the Snapshot, not after discovering problems during client onboarding.
- Deploying to a partially configured sub-account: Applying a Snapshot to a sub-account that already has some configuration creates duplicate elements — two versions of the same workflow, two pipelines with the same stages. Always deploy Snapshots to blank sub-accounts at creation, or audit the destination sub-account carefully before applying a Snapshot to an existing one.
- Forgetting to activate workflows after deployment: Workflows deploy in Draft status. The most common post-deployment complaint from clients — “the automations are not running” — is caused by the agency forgetting to activate the workflows after deployment. Add “activate all workflows” as a mandatory step in your post-deployment checklist and verify each one is Published before going live.
- Not replacing [INSERT] placeholders before going live: If your Snapshot uses bracket placeholders for client-specific values and you go live without replacing them, contacts receive SMS messages that literally say “[INSERT: Client’s Google Review Link]” — a visible, embarrassing error. Make placeholder replacement a checklist step completed before any lead form is connected to live ad campaigns.
- Including test contacts and data in the template sub-account: While Snapshots do not transfer contacts, it is good practice to delete test contacts from the template sub-account before creating the Snapshot. A template sub-account cluttered with test data, test conversations, and test opportunities creates confusion when the agency reviews the sub-account post-deployment to check that the Snapshot deployed correctly.
- Using a Snapshot across completely different verticals: A Snapshot built for HVAC companies deployed to a dental practice creates immediate mismatches — the pipeline stages reference HVAC services, the funnel copy mentions “free estimates,” and the SMS templates reference jobs and technicians. Build separate Snapshots for each vertical you serve, even if the core automation logic is similar. The customisation time saved per client deployment far exceeds the additional effort of maintaining vertical-specific Snapshots.
- Never updating the Snapshot after client improvements: Every time you manually improve a client sub-account — adding a new workflow, refining an SMS sequence, building a new funnel page — that improvement should be evaluated for inclusion in the template Snapshot. Agencies that deploy from a Snapshot once and never update it are progressively falling behind their own best practices. Schedule a monthly Snapshot review: pull the most recent improvements from active client sub-accounts, apply them to the template, and release a new Snapshot version.
Building Your Agency’s Snapshot Library
As your agency grows and serves multiple verticals, you build a library of Snapshots — one per vertical, potentially multiple tiers per vertical. Managing this library effectively prevents confusion about which Snapshot to deploy and ensures every onboarding uses the current production version.
| Snapshot Type | Use Case | Naming Convention | Update Frequency |
|---|---|---|---|
| Vertical production Snapshots | Client onboarding for each industry served | [Vertical] — Production — v[X.Y] | Monthly or after significant improvements |
| Vertical template sub-accounts | Development environment for building and testing | TEMPLATE — [Vertical] — v[X.Y] | Updated before each production Snapshot release |
| Tier-based Snapshots | Different packages (Lead Gen vs Full Stack) within same vertical | [Vertical] — [Package Name] — v[X.Y] | Same as production, maintained per tier |
| SaaS Mode Snapshots | White-label SaaS plan tiers deployed to paying SaaS subscribers | SAAS — [Plan Name] — v[X.Y] | Quarterly, with new feature additions |
| Archived Snapshots | Previous versions kept for reference and rollback | [Original Name] — ARCHIVED — [Date] | Never updated — archive only |
Start Building Your Snapshot Library Today
GoHighLevel’s 30-day free trial includes full access to Snapshot creation, deployment, and sharing — plus the complete workflow builder, funnel builder, CRM, and calendar system you need to build a production-quality Snapshot. Free live onboarding bootcamp included.
→ Start 30-Day Free Trial + Free BootcampAlready a GHL user? Audit your current Snapshot against the production-quality checklist in this guide — most agencies find 3–5 improvements that would reduce onboarding time significantly.
Frequently Asked Questions
Can I update a Snapshot that has already been deployed to client sub-accounts?
Creating a new Snapshot version does not automatically update sub-accounts that were previously onboarded using an older version. Each deployed sub-account is independent — changes to the Snapshot or template sub-account after deployment do not propagate to existing client accounts. To update an existing client account with improvements from a newer Snapshot version, you can either manually apply the specific changes (adding new workflows, updating existing ones) directly in the client’s sub-account, or apply the new Snapshot to the sub-account (which adds the new elements alongside existing ones, potentially creating duplicates that need to be managed). Most agencies manually apply significant updates to existing clients rather than redeploying the full Snapshot.
How many Snapshots can I create in GoHighLevel?
GoHighLevel does not impose a limit on the number of Snapshots in your agency account. You can create as many Snapshots as your business requires — one per vertical, multiple tiers per vertical, separate Snapshots for different service packages, and archived versions of past Snapshots. The only practical limit is the organisation overhead of managing a large library, which is addressed by the naming convention and library structure covered in this guide.
Can I sell my GHL Snapshot to other agencies?
Yes — selling Snapshots to other GHL agency owners is a legitimate and growing revenue stream. You can sell Snapshots directly (share the link with paying buyers, deliver via your own checkout page), through third-party GHL Snapshot marketplaces, or through the GHL Marketplace. Pricing for well-built vertical Snapshots ranges from $47 (simple single-workflow Snapshots) to $297–$997 (comprehensive full-service vertical Snapshots with complete workflow libraries, multi-page funnels, and documentation). If you sell a Snapshot, include a post-deployment configuration guide that walks the buyer through every step they need to complete after importing — this dramatically reduces support requests and improves buyer satisfaction.
What is the difference between a Snapshot and a sub-account template?
In GHL terminology, a “Snapshot” is the specific packaged format used to transfer sub-account configurations — it is the mechanism. A “template sub-account” is the source sub-account that has been built specifically to generate the Snapshot — it is the development environment. The Snapshot is what gets shared, imported, and deployed. The template sub-account is where you build and test before creating the Snapshot. Both terms are often used interchangeably in the GHL community, but technically they refer to different things: the template is the building; the Snapshot is the blueprint.
Do Snapshots work between different GHL agency accounts?
Yes — Snapshots are designed to be shared between different GHL agency accounts. The shareable link format allows any GHL agency account holder to import a Snapshot regardless of which agency created it. This is how the GHL Snapshot marketplace functions and how GHL certified partners distribute their Snapshot libraries to client agencies. The imported Snapshot becomes a standalone asset in the receiving agency’s Snapshot library — it is not linked back to the original creator’s account and updates to the original Snapshot do not affect the imported version.
