Can I move customer accounts and passwords to PrestaShop?
Customer records can be transferred. Whether the existing login will work is a separate question. Plan account access, history and business terms before switching stores.
AI-generated image- 1Quick answer
- 2Key takeaways
- 3Which customer data can I move to PrestaShop?
- 4Can customers keep their existing password?
- 5What changes when moving from Shopify or Shopware?
- 6Will order history and B2B terms be preserved?
- 7How do I make setting a new password straightforward?
- 8Which six cases should I test before launch?
- 9How does sjmedia plan a move to PrestaShop?
- 10Sources & further reading
- 11Cite this article
- 12Authors & technical review
Quick answer
Customer data can be moved to PrestaShop depending on the source system and import method. Existing passwords do not automatically remain usable. Assess authentication separately and plan a new password setup process where needed. Order history, addresses and B2B terms require their own mapping and acceptance checks.
The new store is planned and the products are ready. Then customer service asks a crucial question: will existing customers still be able to sign in after the move? For a retailer, this is not a minor detail. People who reorder regularly or receive agreed business terms expect their account to keep working.
At sjmedia, we therefore treat customer data, authentication and order history as separate parts of a migration. Successfully importing a name and an email address does not prove that the old password will work or that previous orders will appear in the correct account.
Key takeaways
- Plan customer data, login and order history as separate migration tasks.
- Reusing existing passwords depends on the source system and the validated implementation.
- Test accounts, business terms and password setup before cutover.
Which customer data can I move to PrestaShop?
PrestaShop documents the import of customers and addresses, among other records. This provides a basis for transferring core customer data. Which additional fields, groups and relationships can be preserved depends on the source system and the chosen migration method. Agree on that scope before the first full import.
We would start with a small set of representative accounts: a consumer, a business customer with specific terms and someone with several delivery addresses. In a protected test environment, we check how each case appears in the new store. We use synthetic data for functional tests. Any necessary comparison involving real records is planned separately and limited to the information required.
Our article on migrating PrestaShop data and modules covers the wider data scope. This article focuses specifically on customer access after the move.
Can customers keep their existing password?
That question can only be answered after assessing the source system. Passwords should not be stored as readable text, but as purpose-built cryptographic verification values. These hashes cannot simply be converted back into the original password. The new login must also support the existing method and any additional values it requires.
There are two possible routes: technically and securely validated reuse of existing credentials, or customers setting a new password. Password preservation is not a standard promise merely because both platforms have customer accounts. Even when moving between PrestaShop versions, we check the actual records and any login extensions in use.
An additional compatibility solution may be appropriate in some situations. However, it needs maintenance and must not permanently preserve an unsuitable legacy method. If reliable transfer is not possible, a clearly explained new login process is better than an apparently migrated account that fails when a customer tries to sign in.
- Review the current store
- Plan the transfer
- Check the test store
- Support the launch
What changes when moving from Shopify or Shopware?
The authentication method itself may differ. Shopify offers customer accounts that use a one-time email code. With that sign-in method, there is no customer-chosen store password to simply carry over to PrestaShop. Other account types and additional identity services need separate assessment.
Shopify also documents customer CSV imports separately from passwords and order information: importing a customer list is not a complete account migration. When moving to PrestaShop, we therefore check the export data actually available and explicitly plan access to the destination account. A statement such as “all customer data will be transferred” is not a sufficient specification.
For Shopware, we likewise assess the actual version, login setup and available export methods. Social login, business account approvals and customised accounts can require additional work. Platform names alone do not determine password compatibility. A blanket promise would be misleading.
Will order history and B2B terms be preserved?
These requirements need a separate agreement. A customer record, a billing address and a previous order are different objects. They must be correctly linked in the destination store. Old customer references should therefore be mapped to new records in a traceable way; a matching sequential number alone is not adequate proof.
Consider a hypothetical specialist retailer selling to businesses and consumers. A business customer is imported with an address but is not assigned to the appropriate customer group. The login works, yet the agreed prices do not appear. This is not a documented sjmedia client case. It illustrates why we would test account access and commercial terms separately.
Not every historical order necessarily needs to be available in the new storefront. Retailers can agree on a full transfer, a limited history or a separate route for handling enquiries. Customer service and customers need to know what is available and where. Newsletter status and existing supporting records also require separate mapping; an existing customer account does not create new marketing consent.
How do I make setting a new password straightforward?
If customers need a new password, a message beside the login should explain what has changed and how to proceed. It should not suggest that their account has disappeared. “We have updated our store. Please set a new password once to access your existing account” could be suitable wording, provided that this accurately describes the process.
The technical route should use a tested password setup or recovery function. OWASP recommends measures including time-limited, single-use tokens and controlled delivery. We do not recommend shared initial passwords or emailing existing passwords. Customer service should be able to assist without knowing a customer's password.
Which six cases should I test before launch?
Run the following checks in an isolated test environment. Capture emails there rather than sending them to real customers. Record the outcome of each case instead of only counting imported accounts.
- Existing access: A designated test customer can sign in using the agreed method.
- New password setup: The link arrives in the test mailbox, works once and is rejected afterwards.
- Account mapping: Addresses and agreed order history appear only in the correct account.
- Business customers: Approvals, customer groups and agreed terms match the specified scope.
- Duplicate records: A repeated import and similar email addresses do not trigger uncontrolled merging.
- Late changes: Accounts and address changes created between rehearsal and cutover are included.
An intentionally incorrect login and an expired link should also produce understandable feedback. A working administrator login does not replace these customer checks.
How does sjmedia plan a move to PrestaShop?
As a PrestaShop agency, we connect data migration with the purchasing workflow customers will use afterwards. We first establish which accounts, terms and history are actually required. We then define the migration route, login strategy and acceptance criteria. For individual requirements, we regard PrestaShop as an adaptable foundation; necessary extensions and their ongoing maintenance are explicitly included in the planning.
The final changes from the old store and the rollback procedure also need agreement before cutover. Our article on launching a store relaunch explains the sequence. For a store migration with sjmedia, an example account with anonymised requirements is a useful starting point: what must the customer see and be able to do after signing in for the first time? That is what acceptance testing should establish.
Sources & further reading
- PrestaShop: Customer and address import ↗accessed
- Shopify: Customer CSV imports and exports ↗accessed
- Shopify: Customer accounts ↗accessed
- OWASP: Password storage ↗accessed
- OWASP: Forgot password ↗accessed
Cite this article
Johann Nehrlich (sjmedia GmbH, Kuppenheim): Can I move customer accounts and passwords to PrestaShop?. 20 Nov 2026. https://www.sjmedia-consulting.de/en/wissen/migration/kundenkonten-passwoerter-prestashop
Author & technical review
Related to this topic.
Questions about this topic? Let’s talk about it.
I’ll listen to your situation and discuss which next steps suit your store.



