Learn what you need to know before you migrate to 2.0!
Please take time to review the information outlined below carefully prior to your migration date.
Key Feature / Workflow Updates
The table below lists some of the key features that we want you to better understand before you migrate.
Check the Reach out to us... column to see if it would be worthwhile to book time with our team about your use case and workflows.
Reach out to us...
|Catalog to Price Lists||
The URL structure of your catalog (called price list in 2.0) changes from localline.ca/farmname to farmname.localline.ca.
You'll need to update your URL anywhere it is referenced, like your website and marketing materials. If a customer visits your 1.0 URL they are automatically redirected to your default 2.0 price list URL.
If your 1.0 URL is used in a QR code, you won't have to create a new QR code for your default 2.0 URL as long as the QR code is dynamic.
Multiple price lists can be public, each with its own unique URLs.
|If you have more than 1 catalog, or are unsure what kind of QR code you have.|
|Uncategorized products||Any products that were not assigned to a category in your 1.0 account are not categorized in your 2.0 account. Uncategorized products do not display on your 2.0 storefront. You can assign products to categories in bulk on 2.0.|
|Advanced Inventory||There are new ways to track inventory! You can now track and charge your products either item or weight.||If you sell variable weighted products.|
|Orders Exports||Orders page exports have more data and different column ordering. See sample files.||If you apply formulas to or create pivot tables in the exported files that support your workflow(s).|
|User roles (back office)||In 1.0 there are user roles with custom permissions. This feature is not available in 2.0 yet.||If you cannot function without limiting user permissions.|
|Users (storefront)||In 1.0, customer accounts can have multiple users on them. In 2.0, customer accounts can only have one user (for now), but they can specify other email addresses to be cc'd on automated emails about orders.||If you think your customers cannot function without multiple users in their account.|
|Square POS Integration||The Square Terminal integration is something we'll be bringing back to 2.0 soon!||If you are currently or plan on using the Square terminal in the near future.|
|Routes||This feature is not available in 2.0.||If you currently using the Routes functionality on Local Line to plan deliveries.|
We've created new ways to customize your storefront!
The embed feature from 1.0 is supported by third-party cookies, and all major web browsers are in the process of phasing third-party cookies out. As a result, this feature will gradually become unstable.
|If you want to discuss new methods to link up your website and Local Line storefront.|
|Zapier & Integrations||Coming soon to 2.0!||If you have any other software or integrations that you use together with Local Line.|
|Messages||In 2.0, we've taken an email-first method of reaching out to customers. You can send single or recurring emails to your customers directly through Local Line.||If you want to revisit how to best communicate with your customers.|
|Selling to businesses vs customers.||Company names are displayed below the user name for your customer. On the invoice, the company name is displayed next to the user name.||If the way this information is displayed is problematic for you.|
|Subscription billing||Your 1.0 subscription pricing is honoured for one year following your migration.||If you have questions about 2.0 pricing and what you will be billed in future.|
Considerations for the Food hub add-on
Reach out to us...
For the Hub 2.0 "managed vendor" use case, where the hub manages vendor products and inventory directly, the vendor does not receive a Local Line account as all workflows are done in the hub account directly. If your vendors need access to a pick or pack list you will need to manually email it to them.
The "connected vendor" use case is releasing later in 2022 and will introduce vendor accounts that link with the hub account.
|If you are not sure which use case you fit into.|
Vendor on Invoice
|In 1.0 the supplier is indicated on the customer order. This is not the case in 2.0.||If having that feature is critical to your workflow(s).|
|Vendor display info||In 2.0 you have the option to display vendor contact details on your storefront, or to only display them in your back office. By default, your 1.0 data is migrated to display vendor contact details on your storefront.||If you do not want vendor contact details displayed on your storefront.|
|Disable a Vendor||In 1.0 you could not easily disable a supplier and their products. You had to manually remove their products from your catalog and add them back. In 2.0, you can easily disable a vendor.||If you have any questions about this handy new feature.|
When you migrate all of the information on your storefront automatically gets moved to 2.0. This includes:
- Catalog and categories, along with any recurring scheduled emails
- Products and packages
- Customers and store credits they have on their accounts
- Payment methods
- Delivery and pick-up plans (with an equivalent order cut-off time)
- Historical orders for the past 30 days with a read-only status. For orders placed in 1.0, you will be redirected back to the 1.0 version to reconcile or view invoices. With the Food hub add-on, only 1.0 Customer orders are migrated, not Supplier orders. But, you retain read-only for those orders.
- Your customers see their 1.0 order history in their account.
- For Food hub add-on: SupplierVendors (enabled by default)
- For Food hub add-on: Supplier/Vendor products & packages, categories, catalogs/price lists they are assigned to, and inventory quantities. Negative inventory quantities will be migrated set to 0.
When the migration is complete you will receive an email with the next steps!
Q: When I move to Local Line 2.0, are my customers affected?
No, when you migrate to Local Line 2.0, your customers, along with any store credit they have in their account, will not be affected. Their current logins will continue to work on the new storefront! During the migration, your store will not need to be closed.
Once the migration is done, customers who try to go to your old store will automatically be redirected to your new store!
Q: Do I have to move to 2.0 or can I keep my existing account?
We're aiming to migrate all our remaining active accounts to 2.0! This will allow our team to focus on supporting one product and ensure we can build even more valuable features that all our customers can use.
All eligible customers must be migrated to 2.0 before December 15, 2022.
Q: What if I can't migrate on the date you selected?
Not a problem! Reach out to our team at firstname.lastname@example.org along with 1-2 dates that'd work better for you and we'll help reschedule your migration date. Note there are limited migration slots per day.
Q: What time of day can I expect the migration to happen?
Each migration is a little different depending on how much information we need to transfer. What this means is we aren't able to guarantee a specific time of day when the migration will happen. However, most migrations are completed between 10 am - 3 pm ET.
Q: What if my account is on the pause program?
We'll migrate your account all the same! Your paused status will be maintained in 2.0.
When you're ready to get set up for your next season, you'll just need to remember to use the new version of Local Line. New season, new look!
Q: How should I prepare for my migration date?
(1) Explore 2.0: Log into the test account we shared with you via email and complete the 2.0 checklist to see what's changed. If you need access to a test account, reach out to us anytime.
(2) Replicate workflows: Try going through the workflows you go through daily to ensure you're comfortable with how you'd accomplish the same tasks on 2.0 before your migration date. We're talking about exporting pick or pack lists, updating inventory, and fulfilling orders - you know your business best!
Don't forget to visit our Knowledge Base to learn about everything 2.0.