Shopify FAQs: data, SEO and development

Passwords do not transfer as part of a customer import. Current Shopify customer accounts can use an emailed sign-in code. External identity systems are assessed separately: authentication between systems does not mean importing password hashes.

Customer accounts during migration.

We review products, customers, addresses, orders and content. Module-specific fields, saved carts or other app data may require another tool or may not be transferable. We first check a sample export and define what will be retained.

Access and transfer channels are agreed before extracting information. Use appropriate permissions and encrypted transport, avoiding databases or credentials sent by email. We also define where copies are stored and when they are no longer needed.

Changing platform does not itself demonstrate compliance. Review transferred data, providers accessing it, purposes and consent. Technical configuration must align with the business’s privacy documents and criteria.

Shopify generates its own internal identifiers. When linking to the previous system is needed, retain a mapping or source identifier in an appropriate field. A visible customer number differs from an internal ID.

Information compatible with Shopify’s model and the chosen import tool can be transferred. We review addresses and custom fields to decide between native fields, metafields or another solution. A sample is tested first.

Review available codes, balances, expiry and import-method compatibility. Importing the gift card product is insufficient: issued cards’ balances matter too. If original codes cannot be recovered, prepare another way to preserve the customer’s entitlement.

This depends on the previous loyalty platform and new app. Check export and import support for balances, tiers and history, and how customers are matched. Do not convert point balances without verifying equivalence.

Support history is not part of a standard store import. If it must be retained, we review source and destination tools, customer identifiers and export options. Sometimes keeping it in the existing CRM makes sense.

Compatible contacts can be transferred while preserving subscription state and available consent information. Importing a list does not make everyone a subscriber. We also review unsubscribes, suppressions and email-tool synchronisation.

First identify errors: duplicates, unlinked references, incorrect characters or empty fields. Agree what to clean and which source information must be recovered. Importing a faulty database does not solve its problems.

Tags can transfer where included in exports. Dynamic segments need review: old-system rules may have no equivalent in Shopify or the new app. Check which people belong to each group.

No SKU count guarantees good performance by itself. Variants per product, collections, search, apps and catalogue-update integrations also matter. We review volume and structure before choosing the import approach.

Review exported fields and move only what the project needs. Passwords, full card details and other highly sensitive information should not enter a generic CSV. Payment-method migrations require Shopify’s and the provider’s specific procedures.

Traffic and rankings can change during migration. The work involves inventorying URLs, retaining relevant content, preparing redirects and checking the new store. Monitoring helps identify errors but cannot guarantee every position is retained.

We inventory URLs and review the destination for each important page. Then we check redirects, links, content and indexing. Explaining those tasks is more useful than promising a migration without SEO losses that cannot be guaranteed.

URL changes in Google Search.

When a page path changes, prepare a redirect to its Shopify equivalent. Migration does not create it automatically: it must be defined and tested. The destination should serve the same visitor need.

Shopify uses its own paths for products, collections and other resources, so many URLs will differ. Review which can be retained and prepare changes for the rest. Do not copy the source structure without checking compatibility.

Export available fields and assign them to the corresponding resources. Review titles and descriptions for missing values, duplication or problematic truncation. If content changes too, update them consistently.

Shopify generates its sitemap automatically. Check intended public pages appear correctly and retain the redirect map from old URLs. Submitting a sitemap to Search Console is separate from guaranteeing indexing.

Shopify sitemap.

Decide based on content and usefulness. Redirect to an equivalent where one exists; if a page disappears without a replacement, do not send everything to the homepage. Review traffic, links and useful information before removal.

A pre-migration crawl identifies URLs and links. Check what remains, changes or needs redirecting, then review post-launch errors. Removing every 404 is not the objective: correctly resolving pages that should exist is what matters.

Infrastructure and implementation change, but final speed also depends on the theme, images, videos, apps and scripts. Measure representative pages and devices. Shopify does not automatically make any design fast.

Check response codes, final destinations and unnecessary chains or loops. Also verify destination content matches the old URL. Monitor errors and indexing in Search Console afterwards.

Migration can address content, navigation and technical SEO problems. Separate improvements from the work needed to preserve what already functions. This makes changes and post-publication problems easier to identify.

Review posts, images, authors, dates, categories and links. Prepare URLs and redirects with the rest of the site. Check tables, videos and other old content elements display correctly in the new article.

Platform alone does not determine rankings. Shopify can resolve infrastructure and management needs, but SEO depends on content, architecture, links and implementation. Compare against the store’s requirements.

Campaign parameters support measurement and can coexist with content URLs. Review redirects and canonicals without blindly removing necessary parameters. Old parameterised URLs should still reach appropriate destinations.

Configure appropriate behaviour for the new architecture. Do not copy old tags without checks: URLs, languages and domains may have changed. Shopify Markets participates in international-version generation.

Broken URLs, lost content or blocks can reduce visibility. That does not necessarily mean a manual penalty. Investigate and fix the actual problem using crawls and Search Console data.

There is no guaranteed timeframe. It depends on crawling, site size, URL importance and migration quality. Links, correct redirects and sitemaps help discovery; monitor changes in Search Console.

Review response codes, important URLs, redirects, canonicals, robots, sitemap and content, as well as titles, headings and internal links. Repeat checks on the published store because previews do not reproduce every live condition.

Review options, combinations and current limits alongside theme and app compatibility. A complex-product sample helps choose variants, separate products or another structure. Counting catalogue rows alone does not validate an import.

Shopify creates its own IDs. Well-defined SKUs and business references can be retained. Where integration needs links between systems, prepare a mapping table or external identifier field.

First define variants versus distinct products. Packs may need a bundle solution; size and colour may use options. The structure must also work for stock, search and order management.

Map compatible attributes to native fields or metafields. Define type and presentation so they do not become unusable imported information. Check that module-specific fields can be exported.

Products can belong to several collections. These may be maintained manually or through conditions depending on configuration. Filters and menus are separate: importing categories does not build all navigation.

Assess usefulness, traffic and buyer alternatives. Retain an informational page, redirect to an equivalent or remove it as appropriate. Do not publish useless items merely to preserve every URL.

Identify duplicates, incomplete references and inconsistent variants before import. Agree cleaning with someone who knows the products. Do not fill characteristics or commercial relationships by assuming nonexistent data.

It depends on what “grouped” means in the source: a collection, related products, a bundle or combined variant presentation. Choose structure by purchasing behaviour and required stock deduction.

Shopify provides B2B features, and apps support other pricing rules. Review quantities, catalogues, customer type and plan first. A source price table does not always translate directly.

Use sufficiently high-resolution originals and review cropping in the new design. Shopify can serve optimised formats and sizes, but the theme must request appropriate ones. Check alternative text and missing images after import.

They can be imported if available at source. Review usage to avoid duplicates or inconsistencies. Some organise or automate; filters may also use options and metafields.

Review them with the team to decide placement. There is no need to invent a visible category or hide them in a generic collection. Buyers should find products and staff should know what remains unclassified.

Compatible tools can import historical information after reviewing customers, lines, amounts and statuses. Limits depend on source and method. Test to avoid unintended notifications, charges or inventory movements.

Invoices should be retained under business obligations. Do not assume importing orders transfers PDFs or allows identical regeneration. Agree how access to the previous archive is preserved.

Providers are configured and verified in Shopify, not copied as a theme preference. Card details do not transfer through ordinary imports. Saved methods and subscriptions have specific processes and compatibility to confirm.

It is a final update of data changed since the test import, such as orders, customers or stock. Agree the period and authoritative system at each stage. Then check duplicates and operations outside the cutoff.

Shopify distinguishes payment, fulfilment and other order data. Custom source statuses may lack direct equivalents. Decide how to preserve their meaning and how integrations use them.

A compatible subscription solution is needed, with review of contracts, customers, products and payment methods. Procedures depend on the previous platform and provider. Importing orders alone does not continue recurring charges.

Migrating subscriptions and payment methods.

Numbering and identifiers are assessed separately. Shopify has its own system; historical-import tools offer differing capabilities. Retain source references appropriately without promising identical numbering for every future order.

Review which statuses and operations the tool can import. Keeping a historical reference must not execute another refund. Compare old-system documents and amounts before accepting the history as correct.

Review relationships between customer, company, address, catalogue and payment terms. A historical order does not configure the B2B account for new purchases. Features and limits depend on plan and Shopify Markets.

Historical sales imports can be assessed if data and tools support them. Shopify POS implementation is separate: devices, catalogue, payments, locations and operations need their own review.

Connectors or custom development can be assessed, but compatibility depends on versions, modules and data access. Review required synchronisation before proposing a solution. A similarly named connector does not guarantee operational coverage.

Compare existing connectors, apps, middleware and custom development by data, frequency, errors and maintenance. Understand what each resolves and who maintains it. Do not choose solely by the number of advertised integrations.

Frequency depends on connectors, events and both systems’ limits. Delays and incidents can occur; agree detection and correction. Translate “real time” into a verifiable business expectation.

Define reliable identifiers and record-update behaviour. Before creating products, check whether they exist and their relationship with source variants. Prepare controls for sync retries too.

Assess whether to maintain, update or replace them. API versions, support and covered operations matter. An ownerless connector can turn a future update into an incident.

Price data can connect, but application depends on commercial model and plan. Market B2B catalogues and direct company assignment differ in availability. Confirm the required feature before integration development.

Review tax configuration with the business owner or advisers. Do not copy source rules assuming identical behaviour. Test representative addresses, products and customer types without treating technical work as default tax advice.

Shopify manages inventory by location. Review limits, stock assignment and fulfilment. PIM catalogue and individual warehouse stock may need different connections.

Define references, locations, reservations, orders and confirmations exchanged between systems. Review API or connector and failure cases. Both teams should understand received data and timing.

Review their triggers and fields. Platform changes can alter IDs, events and permissions. Test each important automation with sample data before reactivation.

Define who reviews errors, renews access and adapts to API or operational changes. Connector support does not always include custom modifications. Set responsibilities before commissioning.

PIM integrations can be assessed through connectors or APIs. Review field types, images, translations and product publication, plus ownership where content exists in both Shopify and the PIM.

Plus provides advanced options, but specific customisation depends on the surface and current APIs. Review what buyers must see or do to choose a compatible extension. Checkout is not freely editable like a theme page.

Previous checkout design and logic do not copy as theme code. Identify needs and find supported Shopify equivalents. Some use different solutions or have plan restrictions.

The solution depends on whether data belongs to the customer, company or order and where it should be requested. Check field or extension availability on the chosen plan, plus administration and invoicing handoff.

Review B2B catalogues, discounts or other features according to the rule. Direct company catalogue assignment differs from market-based catalogues. First describe who sees each price and why.

A theme cart with specific steps or guidance can be assessed. Check variants, discounts, apps and mobile purchasing. Cart and checkout customisation are different surfaces.

Simple forms can be built in the theme; other needs require apps or services. Review storage, consent, files, integrations and spam protection. Avoid choosing solely to eliminate an app.

Check actual export and import options. Reviews must preserve origin and attribution; points need balances and customer relationships. Do not treat app-dependent information as native data.

Apps and Shopify Functions offer discount, delivery and payment rules, subject to availability and limits. Verify the rule and plan first. A cart function does not imply control over every checkout step.

Availability depends on payment provider, business country, market and configuration. Shopify Markets alone does not activate every local gateway. Check each method in the account and a test purchase.

It customises supported surfaces through extensions and supported APIs, reducing legacy-code dependency. It does not remove testing or maintenance. Apps, permissions and versions still require review.

It can provide a strong infrastructure foundation, but speed depends on construction and loading. Compare representative pages and test conditions. It is not always faster than every implementation on another platform.

Review image and video size and loading, fonts, scripts, apps and theme structure. Prioritise content visitors need on arrival, then measure again to verify changes.

Review each script’s purpose and loading time. Event pixels can use Shopify privacy and sandbox systems, but not every script automatically becomes a pixel or loses its loading cost.

Shopify manages infrastructure for large volumes, but no store should promise absolute freedom from incidents. Review theme, apps, stock and connections, which can also constrain campaigns.

Limits depend on API, plan, operation type and version. Design queues, retries and bulk operations where appropriate. Check the specific documentation rather than assuming every limit scales equally on Plus.

Apps may add images, scripts or requests affecting pages. Check resources and continuing necessity. Uninstalling an app does not guarantee every theme customisation disappears.

Shopify provides image transformations and optimised formats, but the theme must request suitable sizes and declare dimensions. Original file size and lazy loading below the first screen matter too.

Measure LCP, INP and CLS where data exists, distinguishing laboratory and real-user data. Identify problems and propose verifiable corrections. An audit cannot guarantee passing a future Google assessment.

Yes. Current documentation includes B2B features on Basic, Grow, Advanced and Plus, with differences in catalogues, company assignment, payments and market experiences. Review specific requirements and store availability before choosing a plan.

B2B features by plan.

Market catalogues group conditions; direct catalogue assignment to companies is a Plus feature. Review the number of price lists and recipients before deciding. Customer-specific pricing needs do not all resolve identically.

Assess a restricted B2B store or access-dependent presentation. Protection should not consist solely of hiding a button with CSS. Review who can see products, prices and purchase.

Shopify B2B uses companies, locations and associated customers with permissions. Import or configure relationships and check each profile’s access. Emails alone do not create the full company structure.

B2B payment terms can support later due dates according to configuration. Do not generically describe availability as Plus-exclusive. Review plan, permissions and collection handling.

Quick order lists can be prepared where theme and configuration support them. Reference search, minimum quantities and reordering matter. Test with real catalogue and customer devices.

Compare catalogue, prices, buyers, integrations and maintenance costs. Their models differ; a serious comparison does not claim either needs no maintenance. Recommendations must fit the business.

The B2B model supports company data, locations and purchase references. Review administration needs and information required during purchase. Specific invoice or ERP requirements need separate checks.

Choose by required functions and operating costs. Turnover or product count alone does not determine Plus requirements. The calculator compares subscription and fees; B2B, checkout and integrations also need functional assessment.

Official Shopify Spain pricing.

Budget apps, licensed themes, domain, payments, development, support and integrations alongside subscription. Currency, markets or other services may add costs depending on configuration. Compare the complete scenario.

Online-store hosting is part of Shopify’s service. Check plan conditions and external services used. Externally hosted video, apps or independent development may have separate costs.

A Shopify-hosted online store does not need another theme server. Domain, corporate email, middleware and external services are separate and may still cost money.

It depends on ERP version, connector, data and adaptation. Separate implementation, licences or subscriptions and maintenance. Assess specific proposals rather than publishing one universal integration rate.

Some advanced checkout customisations require Plus; other settings, apps and functions have different availability. Define the change and surface first. Not every commercial rule requires Plus.

Price depends on data, design, functions, integrations and launch preparation. We review the store to quote specific work. An example amount should not be presented as a rate for every project.

An audit reviews agreed pages and journeys and delivers a prioritised report and explanatory video. Implementation is quoted separately. Platform decisions or integration planning may fit consulting better.